News for hackers. Stuff that matters.
Re:Practical Go: Real-world advice for writing maintainable ... by int_19h on Thursday February 21, 2019 @11:06PM (#19223041)
GP isn't saying that Go is not productive, but that the community has an irrationally hostile attitude towards anything that is not possible, or easy, in the language.

And I agree - it has become the prime example of "you're holding it wrong" school of programming language design and apologetics.

Re:Practical Go: Real-world advice for writing maintainable ... by pjmlp on Friday February 22, 2019 @01:30AM (#19223567)
To the point that if someone would take the hard work to try fork and implement the features some consider missing, they would be burned on the fire instead of praised for their work, which is why anyone with the skills of doing it just goes elsewhere instead.
Re:Practical Go: Real-world advice for writing maintainable ... by geodel on Friday February 22, 2019 @12:18PM (#19227039)
Do you think really Java or any other professional language would accept some language feature which was developed prior to explicit approval from committers?

If someone thinks since they have developed feature and put lot of hardwork in it so language maintainers have to merge it. I am sure they would have no option but to invent their own language.

Re:Practical Go: Real-world advice for writing maintainable ... by pjmlp on Friday February 22, 2019 @02:05PM (#19228098)
Yes, that is how a large majority of contributions work.

Language improvement proposals aren't taken in just with words on paper.