Lately, I've been wondering—are web apps getting increasingly bloated?💭✨
Starting with React or Vue is super exciting, and modern tools are really appealing. But after using them for a while, haven't you noticed how the code can balloon into something monstrous?😳
For example...
- Adding new features one after another
- Trying to organize by splitting code into smaller pieces
- Embedding CSS into JavaScript
- Packing in error handling, debugging tools, and even remote logging
...And before you know it, you've ended up with a "super heavy app"💥
Then the conversation becomes "We need more powerful build tools!" and you start using another new tool. It feels like a cycle of "gets heavy → deal with tools → gets heavy again"...🌀
Honestly, technologies like Vite are amazing, but maybe we wouldn't have needed them if these problems didn't exist in the first place? That's what I sometimes think🥺
On the other hand, what happens if we go back to the old-school approach of building pages on the server with just HTTP and HTML?
- Client-side JavaScript drastically decreases!
- So tools don't need to be that complex!
- Simplicity without needing TypeScript or complicated build systems✨
- The app ends up light and fast, and users have a stress-free experience🎉
- Developers find it easier to build because it's simpler
But... honestly, this might be a bit boring for programmers, right?💡
Playing with new frameworks and tools is fun, and it's a good way to test your skills too😆
But I want you to stop and think: could these "fun challenges" actually be sacrificing user comfort and quality in the end?📌
That's why I think it's important to ask ourselves again, "What features do we really need?"🌸
The benefits that come from building simply might actually be easy to overlook💗
Maybe it's not so bad to relax your shoulders a bit and go back to basics sometimes?🫶
Hatena
Comments
エイダン
But that can't beat the fun of managing 100 TypeScript files and jumping on new frameworks and tools.
グレース
I often see posts complaining about frontend frameworks, but rarely see anyone saying TypeScript is fun. Sure, some SPAs might be better suited for server-side rendering, but I think the reasons are different.
ハンナ
Server-side apps can get just as bloated, so don't blame the tools.
ロバート
I feel like the premise is a bit off. What's heavy about comparing a feature-rich SPA with a simple MPA? Logging and error handling aren't necessarily easier with MPAs, and MPAs aren't faster because they load on every page transition except the first visit.
クリス
Plus, those 'new super frameworks' you're complaining about combine the best of both MPAs and SPAs, sending only the necessary HTML so both initial load and page transitions are fast.
ミア
It's just about using the right tool for the job. Any technology can be used to build good or bad things. No single technology is either the problem or the solution. Users only care about performance, not how it's built.
クロエ
I think there are limits. You wouldn't build something massive like Figma with HTMX, but I'm currently in the Alpine+HTMX camp and only use React when joining others' projects.
キンバリー
I disagree with your opinion on frameworks but respect it. I just don't get the TypeScript part though. It compiles to JS with no extra output, type safety can't be bad, and it doesn't negatively affect the client.
レオ
Who cares? Judy just builds what works.
リリー
Public web should definitely be simple, but I've been building heavy client-side apps for businesses for a long time. That's why those tools exist.
サラ
I mainly work on content sites and haven't really caught up with the client-side trend. I want fast loading, so I keep JavaScript minimal and lazy-load when needed. My policy is to do without JS whenever possible.
ジャック
That's true.
ベン
Some frameworks make it easier to write slow code. With React you have to worry about entire component re-renders, but Svelte has automatic dependency tracking so that's not a concern—I haven't encountered a slow Svelte app yet.
リリー
There's a reason Rails, Laravel, and WordPress are still around. If traditional MVC works for you, try them. It might be some work at first, but the benefits of separation become clear. For Node-based projects, I'd recommend nest.js too.
ノーラン
What does 'bloat' mean to you? Any tool can be used to build messy apps—I use React because it lets me build good apps efficiently.
ジョージ
You think it's strange that amazing tech like Vite emerges to solve problems? Who gets to decide what technological progress should be?
レオ
Just ignore trends you don't like. It's great that the community aims for progress.
ミア
Probably a skill issue. Loading HTML once and only sending data provides clear separation and can be more efficient in some cases. With SPAs, you can do lazy loading and preloading, making them feel fast even on low bandwidth. There are reasons for frameworks. If you don't need them, just don't use them.
