News for hackers. Stuff that matters.
Re:Why Go Is Not Good by AnimalMuppet on Monday June 30, 2014 @02:57PM (#7966867)
You're thinking wrong. You're also proving the grandparent's point.

You're thinking in terms of "here's this set of bullet point features that I think a language has to have to be a proper, modern language." But the grandparent was asking you to consider that a different set of features might have value form some real-world problems that Go's authors had really bumped into. You reply, "Nope, couldn't have - it doesn't have my bullet point features!"

There are more things in programming than are dreamt of in your philosophy of what a programming language should be.

Re:Why Go Is Not Good by Peaker on Monday June 30, 2014 @03:40PM (#7967167)
He said Go had something new to offer, and listed old things.

He said Go makes concurrency safe & easy, when Go emphasizes features that contradict safety and ease.

He said Go tackled problems in a newer way, when Go is really Algol69 + coroutines.

He denied Go regressing from other languages, when it throws away decades of PL research.

In none of this did he say "Here's an alternate set of features that ...". No. He said concrete, specific, wrong things.

What you are saying is a different thing -- and I also disagree with you.

These "bullet list" features weren't invented for the lols. They were created to solve real problems. Problems that Go doesn't have an alternate solution to.

Go programs dereference null. That is a bad thing. Languages with my "bullet point features" do not dereference null.

Go programs duplicate code to handle different types. Ditto.

Go programs can (and thus do!) mutate some data after it was sent to a concurrent goroutine. Ditto.

Go programs can cast down to incorrect types. Ditto.

The "bullet point features" are important. There are alternatives, but Go doesn't sport any of them.