3 ms·
> Aren't you exactly the type of person pja is referring to, when he mentions "tad over-sensitive about their career choices"? I don’t write Go in my day job (
by hnlmorg 5y ago
> Aren't you exactly the type of person pja is referring to, when he mentions "tad over-sensitive about their career choices"?
I don’t write Go in my day job (nor have I ever). So no, I’m not even remotely that type of person.
> The articles were perfectly fine. The problem you have with them is that you don't like the author's opinion.
It wasn’t the technical opinions I disagreed with, quite the opposite actually. I largely agreed with the technical points.
It was the flourishes they used to express those opinions.
Much like yourself now, he was rather rude and presumptuous about others. You’ve made several assumptions about me here that are wildly inaccurate and completely unwarranted. Am I being over-sensitive to your comments? No. I’m just calmly telling you you’re out of line making them. But it’s comments like yours that do lead to escalations in tone that usually end up in arguments, like those we’ve seen at the weekend.
> Your GitHub disagrees.
I’ve been writing software for more than 30 years and have used over 20 languages to varying degrees - at least a dozen professionally. I’ve even designed a few DSLs in my time too.
My GitHub profile is a relatively recent thing because “everyone was doing GitHub” so the vast majority of my code is on a private git server on my home server. I’m not inclined to open source every piece of code I’ve written and a lot of my earliest contributions to other open source projects do pre-date GitHub becoming mainstream.
In fact I’ve been doing this so long that I have a binder full of code print outs that I used to take to interviews. ;) (or maybe I threw that out a couple of house moves ago?)
While the vast majority of code I’ve published on GitHub is Go, that’s only because at the time of creating the GitHub profile I was considering going for a Go job (I didn’t in the end but the profile still helped my CV). There’s only really one project on GH that I actively maintain. The rest I just leave up because they’re there already.
One thing I’ve learned from my time is that all languages have their pain points. Rust included. And sometimes an academically worse language might be better suited for a specific task. So I tend not to make assumptions about people for their choice of language. ;)
Edit: worth adding that I used to be like you guys, being highly critical about languages. In the 90s I used to mock PHP as a stupid Perl. And in the 80s I was mocked by Assembly developers for writing in Pascal. I’ve grown up since then though. As I’m sure a lot of the Rust folks who mock Go eventually will do.