Readit NewsSuggesting that an application should stay within a 128KB limit is akin to saying I enjoy playing games in polygon mode. Battlezone was impressive in the 90s, but today, it wouldn't meet user expectations.
In my opinion, initial load time is a better measure of performance. It combines both the initial application size and the time to interactivity.
Achieving this is much more complex. There are many strategies to reduce initial load size and improve time to interactivity, such as lazy loading, using a second browser process to run code, or minimizing requests altogether. However, due to this complexity, it's also much easier to make mistakes.
Another reason this is often not done well is that it requires cross-team collaboration and cross-domain knowledge. It necessitates both frontend and backend adjustments, as well as optimisation at the request and response levels. And it is often a non-functional requirement like accessibility that is hard to track for a lot of teams.
Also, you're thinking way too much in a SPA architecture. Using just server side rendering with just a tiny bit of javascript like the article states removes most of the problems you describe like Initial load time and cross team collaboration. The load time of the described websites would be instant, and there is no front end team needed.
I fortunately also got rid of Facebook a while ago. This gave me a lot more time back. It's difficult at first, because there's a little fomo, but now I am very happy.
I never started with all the other social media. No Instagram, no Twitter. So that makes it easy.
My computers have always run Linux, very happy with that.
Streaming services are next. At least the US ones.
Replacing whatsapp with signal also. I noticed a lot of my contacts are already in there, just not actively using it. It's a question of just starting communications and groups there.
It's quite doable, but you have to really want to "vote with your wallet" so to speak. I think it's a worthwhile sacrifice. In fact, it rids you of psychological warfare, reduces anxiety, costs less money and gives you your time back.
If you think about it that way, it's a no brainer.
That failed. Miserably.
Developers always assumed things like "well naturally, if you're playing in the XYZ space, you've already got meson installed. What, do you expect me to teach you basic arithmetic in this README too?" Developers across the board, across programming subcultures, showed themselves unable to get past this sort of thing.
So now we have Docker. You may not like it, but this is what peak install guide looks like. An unambiguous file that describes the exact shell steps required to get the piece of software running, starting from a base distro. The developer can't omit any steps or the container won't work on their machine.
It sucks that this Hegelian situation calls for such a draconian solution, but that's where we're at. Developers as a whole can't be trusted to handle this on their own. If you don't have a better solution to this problem, I'm not sure there's much point in complaining.
It should be possible to improve the containerization experience by providing a better UI and maybe even a different syntax for docker files.
React is reported to be used by 39.5% of developers worldwide, while Vue.js is at 15.4%. The number of "apps" using just HTML+CSS is precisely zero, because those aren't "apps" they're documents.
I suppose it makes sense. It's not like there's any single place that documented where we're all agreeing about what we're supposed to believe. After all, nobody has a date where we all decided that hackers were really cool and awesome.
That being said: I don't get the discussions in this thread. The world can't sustain billions of people anyway. I think decline in the population is a very good thing to happen.
It's silly to think of it as some sort of insurmountable challenge that should be avoided at all cost.