Why Android can't use CDC Ethernet (2023) (jordemort.dev)
240 points by goodburb 12h ago 99 comments
Forests offset warming more than thought: study (news.ucr.edu)
109 points by m463 4h ago 27 comments
Web designs are getting too complicated
57 parkcedar 40 6/9/2025, 4:33:37 AM websmith.studio ↗
Awwwards is not at all representative of the web at large. The set of problems of most websites are almost entirely disjoint from the set of problems on Awwwards sites.
I would also say, in response to one heading in this article—the numbers do lie. The studies it alludes to are somewhere between old and ancient, and being taken significantly out of context and applied far beyond their actual studied scope. The Amazon figure especially is transparently irrelevant in the context of this article.
Yes, things are stupidly bad, but unfortunately this article is shallowly bad too.
100%. I used to work at a studio specifically targeting winning awards with awwwards and it's definitely not the same as working on the normal web. Flashiness is way more important than performance there, be it in UX, conversions or load times.
It was a good space to play around with things like animations and webgl, but turns out that if your business needs to convert, those things can often come in the way of that.
Yes websites have become more complicated[2]. HTTP Archive has been tracking that for a long time. But this isn’t new. And actually web performance isn’t getting worse, it’s been getting better[3].
0. https://www.speedshop.co/2015/11/05/page-weight-doesnt-matte...
1. https://web.dev/articles/user-centric-performance-metrics
2. https://httparchive.org/reports/state-of-javascript
3. https://lookerstudio.google.com/reporting/55bc8fad-44c2-4280...
I don't know if that is irrelevant to the argument "Web Designs are Getting too Complicated".
The argument as stated is kinda ambiguous.
Lets say I wrote a small web app that consisted of exactly 5 input forms with not more than 4 input elements each, backed by a database of 3 tables.
If my front-end uses a tech depending on eleven 3rd party components (vite, npm, a treeshaker, a linter, react, redux, tailwind, sass, graphql, websockets, typescript) then you can get into the situation where both these things are true:
1. The user PoV is that this is a simple webapp which is easy to use
and
2. The developers PoV is that this is an over-engineered design that could have been done in a day with no build-step nor anything beyond HTML, CSS and Javascript.
> Google's research shows users form opinions about websites in 50 milliseconds. If your site takes over 3 seconds to load, you've lost 53% of mobile users. Amazon found every 100ms delay costs them 1% of sales.
In which case, my argument still stands that they’re focusing on the wrong perf metric (page weight).
The least complicated webpage is a blank page, but users won’t find that too useful. That’s why we don’t use page weight as our North Star in the web perf world
Usability is.
It’s still about performance.
How fast can I use it, how smooth can I use it, etc.
My point is about how good can I do what I want to do on a website.
For instance a shopping site can as fast and snappy as it likes, if I can’t find the right articles is useless. Amazon and ebay come to my mind who ignore even simple exact search terms just to show things I didn’t search for.
Just a sad state of affairs overall.
I pretty much set everything I can to dark mode these days, so personally don't agree with white backgrounds in general.
> The web exists to connect people and share information. Let's not confuse it with an art gallery.
websites are art
Maybe that's more an app vs mobile web argument, but the point is adding complexity that adds no value is really annoying.
There is no one true way to prioritize design in all contexts. That defeats the point of design: highly-contextualized problem solving.
In some contexts simplicity and speed are not the highest priorities; memorability is.
I left it to our web team with that explicit requirement and they came back with a bloody react front end. Went back to them with a WTF and it turns out they actually can't do static html any more. No joke. I nearly died inside.
As I'm crap at HTML and CSS, ChatGPT did the job in the end and I cleaned it up a bit.
Perhaps it's the people?
I find that there is a context switching cost going from react to vanilla html/js/css. So i just default to react on everything.
The page I did was less than 4K with all content and css embedded and took me 10 minutes.
There's doing the job and there's costing the company a boat load of money doing the job.
"I need a screw driven."
"Hammer! I have a hammer. Just one. This one."
complete website now weighs 15.9 MB - 14.5 MB is images (395 including responsive versions plus fallback twin). The index page now has a total of 558KB while the same page in the old WP site clocks 21MB - (5.7MB for the 4 images) which it loads in steps 8MB - then 17MB and jumping to final 21MB when I move the cursor from the reload button over to the page.
I've referred to this as "CV driven development". Although to be fair that developer that designs a microservice architecture for 50 users is not better either.
But on the whole, I don't agree with the title. My feeling is - overall - pages have become a lot less gimmicky than they used to be.
This isn't to say that all design is bad - good design is hard and most software engineers are really bad at it and undervalue its impact on users - but if you blindly trust design you can end up with garbage like what this article talks about.
Yet, our designers still insist on adding "bling" to webpages. I'll try harder...
And I've seen similar attitudes in other CTOs, it's mostly marketing/product guys who end up being responsible for the animations. They tend to be far less technical.