this post was submitted on 24 Jan 2025
67 points (93.5% liked)
Web Revival
129 readers
37 users here now
A movement focused on capturing the creativity and openness of the early Internet.
We aren't here to watch Big Web burn (we have plenty of communities for that) but to find positive ways we can make the Small Web better.
Elsewhere in the Fediverse:
- !digitalgarden@lemmy.world
- !retronet@lemmy.sdf.org
- !fediverse@lemmy.world
- !fedigrow@lemm.ee
- !nostalgia@lemmy.ca
- !2000snostalgia@lemmy.world
- !journaling@sh.itjust.works
founded 4 days ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
TypeScript solves most of your type issues. Zod gives you runtime enforcement of those types if you want, if you can stomach installing a library. But it’s true it’s not actually a statically typed language with built-in runtime enforcement of types. I hope in the next 5-10 years we see browsers that are able to run TypeScript with both runtime enforcement and performance benefits from using actual static typing. But IMO TypeScript is good enough solving most of the type problems with JavaScript.
You’re welcome to use as many or as few libraries as you want. There are tons of JavaScript libraries, and some of those libraries have way too many dependencies. But if you cut through the noise, there are actually a lot of high-quality libraries that don’t have an absurd number of dependencies and bring a lot of value.
JavaScript is by no means perfect, but I think it’s become trendy to hate on it. Every language has its issues. JavaScript has done an amazing job outgrowing many of its problems. Growth has brought new problems, but I’ve been writing JS/TypeScript for 10 years, and would not like to go back to JS 10 years ago. It kind of sucked compared to today.