Comments by "Okie" (@okie9025) on "10 JavaScript changes you missed in 2023" video.

The tooling being older than Pangea is also precisely the reason why so many people find embedded difficult 😬
41
If you try to use JS for a large project without a framework, eventually you will reinvent the wheel by creating your own custom framework which will most likely be: - unmaintainable because new developers will not know how to use it - unoptimized because you don't have the resources that huge teams with decades of experience have - unergonomic because it was created for a single purpose and is not a general solution
25
I don't like htmx because the web is a lot more than just HTML. Servers should return JSON because it is client-independent, which allows you to use it in non-web platforms like mobile/desktop/CLI. Did people suddenly forget that the web is more than just websites and servers? Also why is DHH's idea of "being productive" returning to the way we developed apps in 2003? IMO I am 10x more productive with types, modularity, and separation of concerns than blindly throwing shit together in hopes of solving something "quick and dirty".
6
Svelte: *uses custom syntax for components Svelte users: I love Svelte, it's literally just plain Javascript! (its not) Svelte runes: removes custom syntax and makes Svelte code actually valid Javascript Svelte users: It's ugly, I hate it!
3
@HartleySan that's valid, but always remember that frameworks were created to be solutions to a problem. Nowadays 99% of websites won't even work with JS disabled which just shows how big of a problem it is to get the desired result.
3
@glebtsoy4139 I agree with this idea, but unfortunately having to configure your server to serve both hypermedia data in the form of HTML and also serve JSON to other clients is kind of a PITA. JSON is easier and less expensive to format/parse, and it doesn't couple data with form/functionality like HTML does. It also means you have to manage/pay for one less server.
2