(no title)
runn1ng | 6 years ago
One is that JavaScript is bad. It’s true, but strongly typed languages built on top of JS improve it immensely. Most people today use TypeScript, I used to use Flowtype but the history went the other way, oh well. So that part is being fixed.
The other part is the package management, and the ecosystem, and that’s almost independent on JavaScript the language. And well, the situation there sucks so much that I needed to escape to backend world, since I don’t want to deal with broken webpack plugins anymore.
Don’t get me wrong, it’s also broken in python and golang (my current languages), but people at least ADMIT it’s a problem, and in golang folks try to fix the vendor/ mess with modules. (Python... ugh.)
I wish the npm mess was getting better, but while yarn at least solved some sub-problem, the whole thing doesn’t get better. Back to golang I go, I feel happy here.
(Well unless I have to copy paste Apply for the 30th time.)
No comments yet.