Wasn't there a major lawsuit long ago between Netscape and Microsoft over software bundling. Pretty sure it Microsoft in reaction made Internet Explorer free to avoid the monopoly claim effectively. This bankrupted Netscape because their browser was their only revenue driver whereas Microsoft could still sell its other products. Mozilla the non-profit was formed and inherited Netscape's browser software which was then supported by Google paying for it's search engine to be the default browser page in Firefox and funding the majority of the donations to Mozilla for years. So it's actually a huge deal with seemingly exactly the same precedent from the same company only a couple decades later. Kind of surprising they keep trying so it must be very lucrative.
They haven't had a "point-and-click adventure UI" for years. Pressing left Shift twice has been able to find ever single setting, button, code symbol, tool window, etc. since at least 2020.
I initially really disliked the new UI but since they trimmed the negative space around icons and even introduced a compact mode, I switched. My only dislike is that all buttons are monochrome.
It's awful to incorporate as part of a project (all the configuration for compilation, mapping errors etc.). It's also extremely complex language with plenty of footguns. The required TS tooling is also an argument against it.
Why? Most companies require skills in frameworks and libraries. The fact you can glue them together shows a different skill, that you'll most likely use in job daily.
This feels so forced. Make a joke CV, strip it of any mentions of these "bad" things, try applying. Good luck.
There's a ton of value in building stuff without tools. It's somewhat similar to learning two frameworks; seeing React's philosophy makes me a better Vue programmer. In a similar vain, building stuff without tools teaches me a lot about what those tools actually offer me. What stuff is really hard? What stuff is really easy to abstract out? How do Vue/React/Whatever do these things?
It also teaches you more about your platform. In the end, all these web tools and frameworks are running in that same browser. I find especially with newer web developers, it's hard to solve something in React/Vue/.. because they don't know how to break up the problem. If you'd roughly know how to solve the problem without those frameworks, it becomes much easier to figure out how to solve it with them too.
Finally, I also just get toolchain fatigue. If I want to build a simple landing page, I don't want to learn new stuff, I don't want to read what changed in the latest versions, what the correct way of the day is to set up a project. Honestly, I don't even want to have a build pipeline and module swapping dev server, that inevitably needs to be configured. Just some static html/css/js is often good enough. And as I said, you also learn which problems frameworks solve well, so you'll know when some static files isn't the right choice.
Understanding your std library performance is lot more important