News for hackers. Stuff that matters.
Re:Go 1.18 by pjmlp on Wednesday March 16, 2022 @02:28AM (#30695911)
Because in many shops IT decides what languages people use, given the platforms, not devs.

Also quitting the job isn't always an option.

That is why some of us have to put up with languages that we rather not.

Re:Go 1.18 by throwaway000811 on Wednesday March 16, 2022 @05:26AM (#30696815)
We change the language; people who formerly enjoyed the language now have to put up with a language they rather not. Their only option is to quit programming since there are no programming languages they enjoy left.
Re:Go 1.18 by pjmlp on Wednesday March 16, 2022 @06:04AM (#30697004)
Or they become adults and acknowledge programming languages are products like anything else and they either evolve or stagnate.

Even COBOL and Fortran keep up with modern times!

Yes, including generics.

Re:Go 1.18 by jshen on Wednesday March 16, 2022 @07:23PM (#30705463)
C has entered the chat
Re:Go 1.18 by jppittma on Wednesday March 16, 2022 @10:05PM (#30706754)
Go 1.7 is still around. If people can still run python2, by all means, keep fighting the good fight.
Re:Go 1.18 by erik_seaberg on Wednesday March 16, 2022 @05:11AM (#30696738)
This. I joined a Java- and Scala-centric team, yet Go is continually harder to avoid for no fault of our own, so I’m glad we’ll at least have a less obstinately broken dialect.
Re:Go 1.18 by jshen on Wednesday March 16, 2022 @11:26AM (#30699981)
So you want to diminish the diversity in programming languages because it’s an inconvenience to you personally. I respect the honesty.
Re:Go 1.18 by pjmlp on Wednesday March 16, 2022 @11:31AM (#30700054)
Thanks, the same way that people in Go community see as inconvenience to learn how to write better code.

The old ways of code generators are good enough.

Re:Go 1.18 by jshen on Wednesday March 16, 2022 @02:41PM (#30702413)
I've been coding for decades. I've written large scale systems in functional languages. I was a believer, but after many years of experience, I didn't find it to add a whole lot of value. I didn't find that there were fewer bugs as promised, it wasn't faster to develop and ship features, and most importantly, it was hard to jump into other peoples code and make sense of it.

You might have a different opinion, that's fine, you have tons of languages that work the way you want. That's what diversity is for. Yet so many of you want to remove that diversity for a reason that I don't understand. There is no science that has proved which of us is right, so the best option in my opinion is to let diversity flourish. I can't understand why you all are against that.

Re:Go 1.18 by pjmlp on Wednesday March 16, 2022 @05:18PM (#30704217)
Apparently the Go team has themselves admitted that we are right and they were wrong.

Go is open source, create your own fork without generics and lets see which version keeps going.

Re:Go 1.18 by jshen on Wednesday March 16, 2022 @05:42PM (#30704492)
We must be talking past each other, and maybe we don't disagree all that much. I'm not talking about generics in this form, and I think the Go team did a good job in their approach and implementation. However, you can read in this thread many people that are demanding more, specifically with the generics implementation. It's not good enough because you can't create monads, do purely functional programming, etc.

I'm hopeful that this implementation is hitting the sweat spot, and that the Go team won't chase the demands to make Go like many of the other languages. I think the biggest win for Go is not having class based inheritance. Fortunately, I haven't seen anyone demanding that.