@tante haha yes. I think my partner feels this right now. She learned vanilla js and is now a trainee. Except they don't use vanilla but node with transpiled code. Except they use all that in reactjs. Except they use all that in nextjs.

Is is quite convoluted unfortunately. I am not sure there is really "that" one way to go. It kind of depends what you want to develop and then you can try one of the more popular options 🙈

@tante thats why i use for my work a more minimal setup, i build smaller components on my own, and use libraries that try to solve one problem.

But you are right, to start is a little bit rough, if you search you find a lot of best practicse that get old if finish reading it 😅

@tante I think what you're looking for is an opinionated framework. Svelte is a great jumping-into choice.

But JS as a language shouldn't ever be opinionated. That's what frameworks and libs are for, decreasing options until there's just x way to do it. That's why there's such diversity today, depends on your need for that thing.

@tante @emilygorcenski It’s a steaming turd with at least three ways to import code from elsewhere.

I find that the most acceptable and consistent way to get something done in javascript is to write it in Typescript. The tooling is kinda mature enough that the translation step is bearable.

@tante: The heavy emphasis on frameworks and the fact that the flavour of the day changes so frequently and feels led by fads put me off web development pretty much permanently.

That JavaScript itself bears the scars of being hacked together in ten days doesn't help proceedings.

@tante I'm a big fan of #vim and #neovim, but may I just mention; this whole Flerp vs Shlorp is totally a thing here as well, unfortunately. See syntastic, pathogen, deoplete (to a lesser extent), and, I suspect, quite a few other plugins. Even color schemes!

Although I'd like to give a shout out to signify, which was turned async without abandoning the existing code and name.