the 3 stages of me discovering a new tech:
- anti-hype: ew it's new must be bad
- engagement: oh so actually cool I'll use it for everything
- desillusion: ew I'm disappointed I was right it's shit
- acceptance: oh it's actually good when used properly
Now I like Go and Docker. It took some time, mostly for me to know why I should hate some examples and appreciate its few good uses.
Some are still mostly hated, like Node. (which I just can't really like when there's Go for instance)
Some I always liked, like Rust (which didn't really have this hype phase I felt a need to oppose, it's just slowly getting better)
Node... I just feel like it's a bad language and a bad ecosystem. And we took that bad base and pushed it hard enough to work in production for some reason and now it's mildly working and it's just sad we spent all this effort there.
Just imagine what we could have now if all that work and resource were put into... Rust?
@CobaltVelvet I think the One True Language Per Purpose approach has been tried before and failed miserably, yes they are overlapping but each one has its own set of strengths and its own approach to solving the same problem. Diversity may not be a bad thing here, especially since we have the Internet so we can have many people working on each project despite them not working in the same company or living in the same area.
@jkb I don't mean One True Langugage, but... One okay syntax common to everything. I can't think of anything Ruby does that Python doesn't for instance, we could write ruby-style python and enjoy not having to translate modules. Same for JS, there are interesting paradigms but not strongly linked to the language itself.