4 ms·
I sorta like them for two reasons: 1. It's interesting to see what people struggle with or like about it, having written a lot of Go. That gives me some perspe
by dvirsky 13y ago
I sorta like them for two reasons:
1. It's interesting to see what people struggle with or like about it, having written a lot of Go. That gives me some perspective, I guess.
2. The comments usually have these little gems of tips and tricks, like one I found here.
That said, #1 is getting a bit old.
- SiVal 13y agoI like these articles, because I like learning from other people's real-world experiences with various tools. He spent years using C++ at Google, yet decided not to use it for his own business even though he, presumably, wasn't one of the "junior developers" who couldn't handle memory management. He used mainly Ruby on Rails at his post-Google company and had a very negative experience. He says he'll write more about the naked emperor Rails. I'd love to read that article. And if Haskell is so much better for real business infrastructure in practice, and not just a "more interesting language" in its own theory, I'd like to read more articles about companies that use Haskell, not fewer articles about companies using Go.
- dvirsky 13y agoI've done lots of C++, and memory management has become much easier since shared and scoped ptrs have entered the std lib. But still, going back to it now for a new project seems highly unlikely to me, it's like moving from a feature phone to a smartphone and then back. I just can't go back now. I'm a server guy so Go really hit the spot for me, despite having its shortcomings.