It's 2024, the web platform now includes a full component system, CSS we only dreamed of 10 years ago, deferred module loading is now a platform feature, and a fuller JS standard library than it ever has...even in Safari.
-
@zkat @slightlyoff what's cool about this is you can also see the chart where the bundle size slowly creeps up with every version. And by cool I mean horrible.
https://bundlephobia.com/package/angul[email protected] -
Alex Russellreplied to Louis Ingenthron last edited by
-
@polotek @slightlyoff sometimes it suddenly drops with a new major version, and then... starts creeping back up. It's incredible.
-
@slightlyoff yeah. No offense to Louis. But I think it's a good example of a subtler point that we're trying to raise. Software developers have really been taught to focus on software that they like to use or that makes them feel more productive. And that has become a proxy for helping them produce better end user software. But that correlation was never actually there.
-
@villetakanen Literally anything but legacy desktop frameworks (React, Angular, Ember) is better! And HTML/CSS is best.
-
@zkat @slightlyoff I'm super interested in what changed with 3.0 that resulted in such a drop. I'm probably gonna do some more research around changes in bundle size over time.
-
@polotek @zkat @slightlyoff it's worth noting that bundlephobia is not an accurate measure of bundle size. it just indicates the size of the things in the package.
many frameworks do transformations at build-time to produce a smaller (or larger) client bundle. a more proper technique would involve creating a hello-world/Counter app and measuring the bundle size
-
@polotek @slightlyoff oh there's also NextJS which last I checked was like 87kb , but probably getting bigger.
-
@mayank @zkat @slightlyoff understood. It's just a hueristic to start with. And I do think it's likely that there's still a correlation in most cases.
-
-
@konnorrogers @slightlyoff I put Nextjs in a different category. It's a superset of react. For me personally, I'm interested in focusing on the needs smaller projects. In that context, it's very easy for me to tell people they don't need nextjs at all.
-
@slightlyoff @mayank @zkat Feels like this would be handy? https://www.realworld.how/
-
@polotek @slightlyoff NextJS is closer in relation to Angular and Ember in that both projects ship SSR, routers, etc
It's definitely not apples to apples with React to Angular
-
@slightlyoff we really need some kind of software on the client side to handle client-side routing, state, and even basic transversal features such as information submission. It would be the basic for surfing the web so we could call it a "surfer" /s
-
@boostmarks current practice is more "suffer" than "surfer", TBH
-
Marco Rogersreplied to Konnor Rogers last edited by [email protected]
@konnorrogers @slightlyoff I do think Angular is not the same as react. But default angular does not ship with SSR. You have to add it explicitly.
I think "apples to apples" is often a red herring and a distraction. This same argument could be made in regards to react and lit not really being in the same class of offering. Having perfect categories for these things is not a goal of mine.
-
Andreu Casablanca 🐀replied to Alex Russell last edited by
@slightlyoff I suspect you may have read this article already, but as a reference for others... this is somehow related (as in half-assed es5 backwards support is bloating the web for no good reason):
The State of ES5 on the Web
Should web developers and JavaScript library authors still transpile their code to ES5? This post looks at what the data suggests based on what popular libraries, tools, and websites are doing
(philipwalton.com)
-
@slightlyoff Aye but 10 years ago app builders felt like the web had stalled again and needed to build, so they chose the thing with VELOCITY (for better or worse).
Now they've got apps they don't know how to AFFORDABLY improve.
What I want to see is all the hot takes that help people to wade OUT of the syrup, not point out that they're stuck up shit creek without a paddle.
-
@benschwarz The way out is always the same: put the user first. That changes the choice landscape, and better solutions present themselves almost immediately.