People fought to replace the tools of the era with this. It had some advantages over time - ES6, a good plugin ecosystem, react adoption - but quickly it just became "the standard" which everyone is afraid to question.
I used to maintain a build workflow library [1] a lifetime ago; while our frontend build needs have evolved way beyond it, I can't avoid the feeling that we overengineered a little too much.
The demo page scroll is very janky, which detracts from the animations entirely. Seems to be because of the excessive use of blur filters - the cards are on a black background so the filter is not doing anything anyway.
(I'm on a brand new PC with pretty good hardware. It's not as bad on the Mac, but it still can't keep up 60fps)
> if people chose the wrong tool for the job and use a 1MB SPA to serve a landing page, that is where things go wrong
That is exactly the case. Can’t really blame
the people when every learning resource, react evangelist, tweet and post points you towards that.
> If however, every link click, every route change, every interaction triggers a SSR server roundtrip, the app will not feel snappy during usage.
SPAs still do the same, maybe more round trips for API requests, we all know how endemic loading spinners have become. Rendering HTML does not meaningfully affect server response times. And frameworks like Datastar (used in this benchmark), htmx, alpine allow you to avoid full page loads.
The point about Brotli compression being extremely efficient for SSE is a great insight.
It means applications that send “dumb” HTML snapshot updates instead of “optimized” payloads can actually be more efficient while massively simplifying the architecture.
An optimized fine grained payload with compression can out perform the course approach. Course payloads have added cost to swap in the DOM, and fine grained payloads don't require complex architecture.
Asides from rendering I have additional concerns about course SSE payloads. You basically remove any cache capabilities (though this is common with all update streaming approaches). Uncompressed the payloads are quite large and the browser may not be able to dispose of that memory, for example Response objects need to hold all body data in memory for the lifetime of the Response because it has various methods to return the whole body as combined views of the buffer. Also benefits of compression for SSE payloads are going to be drastically reduced in situations where connections easily get dropped.
No mention of tool use. If the model cannot emit both text and audio at the same time, to enable tools, it’s not really useful at all for voice agents.
This take might have been true years ago, especially for cheaper makes, but modern EVs from china use high-quality components and designs that often surpass european automakers. The premium brands - Nio, Zeekr, Polestar, Lotus, etc - have design and R&D offices in Europe, and source parts from suppliers all over the world. Nio uses Nvidia Orin chips, Qualcomm SoCs, Brembo brakes, Bosch controllers, ZF suspension systems, Continental/Pirelli tires, and ClearMotion (in their flagship model); can't get any better than that.
The driving feel is definitely a thing, the chinese cars are very soft and 'boaty' which is not as desirable elsewhere. They are also on average much larger and heavier than their western counterparts, cities in China have road infrastructure built in the past 20-30 years with spacious lanes.
> have design and R&D offices in Europe, and source parts from suppliers all over the world. Nio uses Nvidia Orin chips, Qualcomm SoCs, Brembo brakes, Bosch controllers, ZF suspension systems, Continental/Pirelli tires, and ClearMotion (in their flagship model); can't get any better than that.
Exactly my point - if premium Chinese cars use Western components are built by Western robots, and designed in Western offices - that means the Chinese technological superiority does not exist.
As for their cars and roads being big - I don't see that as an upside, I have heard from many Chinese residents that the physical size of their cities means (most European cities are denser than Chinese ones) that navigating them becomes that much harder and painful.
Which lays to rest another myth about how China is light-years ahead of the West in urban planning , when in reality they have their own issues.
Yaya. Sorry. I didn't state my assumptions, am mixing issues.
To me, Kia/Hyundai is an example of a foreign manufacturer successively building EVs in North America for North America. Satisfying American standards, tastes, regulations, etc.
I expect the larger Chinese competitors to do the same.
Decades ago, European and then Japanese competitors did as well.
I'm completely against regulation of any sorts on 3D printing, but you have to admit there is a huge difference in purpose there.
reply