Thanks for the thoughtful write-up—always interesting to revisit JavaScript's quirks and strengths through someone else's lens.
That said, I think a few of the issues highlighted, while valid, might not be as disruptive in modern practice as they used to be. For instance, the typeof null === "object" behavior is certainly unfortunate, but it's well-understood at this point, and most tooling/linting setups help you avoid tripping over it. Similarly, Array.prototype.sort() sorting lexicographically by default feels odd until you remember JavaScript’s history as a primarily string-focused scripting language. These days, providing a comparator is second nature for most devs working with numeric arrays.
The point about accidentally declaring globals is a good one—but thankfully, with ES modules, use strict as the default, and tools like TypeScript, it’s much harder to make that mistake in modern codebases.
That said, I really appreciate the focus on JavaScript’s virtues, like closures, async/await, and overall flexibility—those really are part of what makes the language so enjoyable despite its rough edges.
I'm curious—have you built or maintained any large-scale JavaScript or TypeScript codebases recently? If so, what were the biggest pain points you ran into? Do the quirks you mention tend to surface in real-world projects at scale, or are they more theoretical annoyances that pop up in isolated cases?
There are definitely still many challenges in the language, but the ecosystem has come a long way, and it seems like it's still evolving in the right direction. Hopefully JavaScript keeps improving—both in language design and developer ergonomics—without losing what makes it so approachable in the first place.
Affinity photo and affinity design are quite good replacements for Photoshop and illustrator respectively. You can get them with a one time payment.
I got them during a promotion and i was able to get both for 30 USD.
I have been using them for about 6 months now and i find them quite good, even though, having used Adobe tools for a long time, i miss the familiarity with the interface and the shortcuts and some of the more advanced features.
I am not that he expert with video editing to be able to recommend alternatives unfortunately...
I think you bring a very good point. It's true that you need time to be able to develop the skills and the knowledge but it's also true that those skills don't come from free by just waiting for time to pass while sitting idle on a desk.
I have witnessed very very "senior" engineers who didn't really showcase any senior trait, nor they were helping the company or the colleagues in any significant way. Conversely, I have seen very fresh engineers showcasing the diligence and a level of knowledge that you would expect from someone with longer time in the industry. Those tend to be exceptions, but they happen.
Time in the industry is definitely a relevant factor, but I'd say it's also not a guarantee for more seniority...
I really love your clarification on point 3. I like to think time spent on the industry is not necessarily an indication for actual experience. I have seen people that have spent years and years in the same company doing the same tasks over and over and I tend to believe that they have grown much less than other professionals that managed to be exposed to more challenges during the same time-span.
I also love the idea of T-shaped profiles and of course communication skills are a must!
I have been using fastapi for a project in the last months and it has been a delightful experience. I really love how the framework is designed, the great documentation and the built in support for Async/await.