52
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 01 Apr 2025
52 points (94.8% liked)
Asklemmy
47134 readers
1156 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 6 years ago
MODERATORS
The language itself has gotten a bit better. It's not amazing but it's decent for a scripting language, and very fast compared to most scripting languages. TypeScript can also really help a lot there, it's pretty good.
It's mostly the web APIs and the ecosystem that's kinda meh, mostly due to its history.
But what you dislike has nothing to do with JavaScript but just big corpo having way too many developers iterating way too fast and creating a bloated mess of a project with a million third-party dependencies from npm. I'm not even making this up, I've legit seen a 10MB unit test file make it into the production bundle in a real product I consulted on.
You don't have to use React or Svelte or any of the modern bloated stuff nor any of the common libraries. You can write plain HTML and CSS and a sprinkle of JavaScript and get really good results. It's just seen as "bad practice" because it doesn't "webscale", but if you're a single developer it's perfectly adequate. And the reality is short of WebAssembly, you're stuck with JS anyway, and WASM is its own can of worms.
And even then, React isn't that bad. There's just one hell of a lot of very poorly written React apps, in big part because it will let you get away with it. It's full of footguns loaded with blanks, but it's really not aweful if you understand how it works under the hood and write good code. Some people are just lazy and import something and you literally load the same data in 5 different spots, twice if you have strict mode enabled. I've written apps that load instantly and respond instantly even on a low end phone, because I took the time to test it, identify the bottlenecks and optimize them all. JavaScript can be stupid fast if you design your app well. If you're into the suckless philosophy, you can definitely make a suckless webapp.
What you hate is true for most commercial software written in just about any language, be it C, C++, Java, C#. Bugs and faster response times don't generate revenue, new features and special one-off event features generate much much more revenue, so minor bugs are never addressed for the most part. And of course all those features end up effectively being the 90% bloat you never use but still have to load as part of the app.
So, I should learn it well and be careful on what to add and my product should be good, okay I will give it a try insha'alLah