I absolutely agree with you. Thank you for letting me know, that I'm not alone! I'm coming from a backend-environment and had to learn how to do frontend as we

I absolutely agree with you. Thank you for letting me know, that I'm not alone! I'm coming from a backend-environment and had to learn how to do frontend as well. While JavaScript as a language can be handled (it has its quirks, as all the other languages out there, still quite logic IMO), the tooling around creating an application is totally a mess. A packager and babel and module handler and use express and build with vite oh and version ES6 or better ES20 or back to ES5 and serve the static content with sirv and ts.config and ... On the backend side I was used to just install my packages and be able to start coding. Not on the frontend side. I have to admit that I find it to be a more complex environment, as you need to support different browsers, you have a client and server part, you need to handle session/state data and so forth. Beside that you need to take into account security, performance on client/server, network communication, local storage, and the list goes on. There are also hundreds of ways to do a single thing. In the end what helped me was to stick to a single framework and follow its way from start to end. Also the advent of frameworks like Svelte/SvelteKit helped a lot as they reduce the tooling to a bare minimum, keeping single components maintainable with mostly pure JavaScript. Tl;dr: You are not alone :-).