News for hackers. Stuff that matters.

A comment on Go and Java: Rethinking Type Safety for the Pragmatic Age. Parent comment

Re:Go and Java: Rethinking Type Safety for the Pragmatic Age by desumeku on Tuesday November 26, 2024 @05:15PM (#42250671)
Rob Pike has talked before[1] on this exact subject, about how all languages are merging into one giant PL-theory sludge where every camp is adding and stealing features from one another, and that one of purposes of Go was to avoid following in this same direction.

[1]: https://youtu.be/_cmqniwQz3c?t=34

[ Parent | on HN ]
Re:Go and Java: Rethinking Type Safety for the Pragmatic Age by RadiozRadioz on Tuesday November 26, 2024 @05:28PM (#42250787)
Fair enough. I agree with the sentiment that we need diversity in languages.

Personally, when I'm solving a problem, I like to reach for the pre-established universally understood pattern that's built into my language. Rather than using a language that doesn't have any of those things and requires me to create my own, worse, implementation that's unique to my program (or use a random 3rd-party module of dubious quality for something basic).

[ Parent | on HN ]
Re:Go and Java: Rethinking Type Safety for the Pragmatic Age by coin on Tuesday November 26, 2024 @05:54PM (#42251030)
Agree. Removing useful features in the name of diversity seems silly.

> requires me to create my own

Yes, how many string contains methods are there out there, as the result of everyone having to write their own.

[ Parent | on HN ]