2 ms·
Being easier to work with than Java isn't a very high bar to clear though. So you discovered your local maximum. That doesn't say absolutely anything about the
by pdimitar 7y ago
Being easier to work with than Java isn't a very high bar to clear though. So you discovered your local maximum. That doesn't say absolutely anything about the usability and easiness-to-work-with of JS.
- hn_throwaway_99 7y agoI never made an argument that JS is some sort of high nirvana. I just called bullshit that JS is a "toy language", which it absolutely is not.
- pdimitar 7y agoDon't know about the toy language stuff -- only their creators know if that's the case. So I wouldn't claim that in particular. However, JS accumulated significantly more cruft and legacy BS than the other 7 languages I learned and worked with. So let's not pretend JS is on par with everybody else. It's not. We simply had no choice -- for like 20 years -- but to use JS. That didn't, and still doesn't, make it good. It makes it the half-baked language that everyone is stuck with nowadays.
- hn_throwaway_99 7y agoTo each their own, but I still totally disagree that "it makes it the half-baked language that everyone is stuck with nowadays." If anything I find it ironic that Java was supposed to be the language that was "run everywhere", but Java was never successful in the browser. For the very first time I have front end and back end teams using TypeScript for pretty much our entire code base and it has unlocked a huge amount of team productivity that I've never seen in environments where different teams are 'siloed' behind totally different programming languages and ecosystems.
- pdimitar 7y agoTeam efficiency (and conversations with the same people along the entire stack) is the first good argument in favour of JavaScript -- technically in favour of TypeScript -- and I can stand behind that. As long as we agree that siloing is not a problem everywhere. It's all about the people first, technology second, or that has been my experience at least.