frameworks are a relic of a time when cross browser differences were so dire you needed some abstraction.
now you kinda only need that for the newer APIs that have differences still like storage, and audio. these APIs didn’t exist at all when frameworks started and aren’t even addresses by them.
we have es modules now. free yourself from the shackles of your build systems
“X language sucks and it’s the worst and I hate it”
boring, unhelpful, not very thoughtful, based on pure emotion
“X language is useful for Y, but has Z flaws you should watch out for if you don’t wanna waste a lot of time”
productive, helpful, interesting, practical, geared towards getting stuff done instead of implying people are stupid for liking something
Here is the reason, I think that JS is causing me more pain than necessary. Solve a and b;
Easy... a=22, b=23
@niclas oh damn your contrived example that has never once appeared in any real code project has sure showed me