3 ms·
I never realized how much it hurt the language’s momentum. Yes. The combination of a botched transition with a high arrogance level was hell. Here's something
by Animats 6y ago
I never realized how much it hurt the language’s momentum.
Yes. The combination of a botched transition with a high arrogance level was hell. Here's something I wrote in 2015 after porting a medium-sized system from Python 2 to Python 3.[1] I listed a number of package problems encountered during the conversion. Ones that indicated those libraries weren't being used much in production. I discovered that the SQL connector broke if you loaded a database of tens of thousands of records, for example. And oh, did I get hate mail. You can see the comments below mine.
That's what led me to Go. Go is a mediocre language. That's a strength when you just need to get something done. It comes with a set of libraries which are heavily used internally within Google. So, if you're doing something that is server-side for some web-related task, the libraries for that are probably both present and well-debugged. And they don't seem to be deprecated rapidly. I'm not using them for any Google-specific services, so I can't speak to that.
[1] https://lists.archive.carbon60.com/python/python/1187081/?page=1;mh=-1; https://lists.archive.carbon60.com/python/python/1187081/?pa...
- physicles 6y agoYeah I have the same thoughts about go, which I've been using every day for the last four years. It's super rare for an upgrade to break anything (has happened though). When it comes to running stuff in prod, boring is good.