News for hackers. Stuff that matters.
Re:Featherweight Go by baby on Sunday May 31, 2020 @02:21PM (#23371445)
I'd say the popularity of Go stems from the lack of generics.
Re:Featherweight Go by pcwalton on Sunday May 31, 2020 @03:47PM (#23372116)
No, it doesn't. Go is popular because of the names and organization behind it, as well as the fact that it's useful for a lot of people despite the lack of generics.

Certainly, a lot of people are attracted to Rob Pike's rather idiosyncratic preferences, tastes, and nostalgia for the early days of Unix, which are on display in a lot of Go's design decisions, like the lack of generics. But lots of random people have preferences and nostalgia for all sorts of things; we usually only pay attention to such things when it's a person with a famous pedigree who has them.

Re:Featherweight Go by tptacek on Sunday May 31, 2020 @04:42PM (#23372541)
The "names and organization behind it" thing is needlessly condescending (not to mention false), and the ability to get things done without generics basically restates David's point.

Was there something in this paper that you felt unfairly treated Rust, the language you represent on these threads? Because otherwise, I can't see what would motivate you to join this thread to snipe.

I'm with David, for what it's worth. Lack of generics has mostly helped me be productive in Go, and the extreme prevalence of generics in every Rust library I deal with has definitely slowed me down a bit. I'm looking forward to generics support in Go, but mostly for what I hope it does to message board threads.

Re:Featherweight Go by pcwalton on Sunday May 31, 2020 @05:53PM (#23373119)
I went out of my way to make the point without condescension. Evidently I didn't succeed, and I'm sorry for that!

Let me put it another way: Virtually all languages that have become popular recently have done so because of the backing of some large organization or another. There was a time when languages like Perl, Python, and PHP could arise out of basically nowhere and become popular. That time is gone, and now languages essentially need organizational backing of some kind to succeed. That was true for TypeScript, it was true for Rust, it was true for Swift, it was true for Kotlin, and it was true for Go. They also benefit from some sort of well-known thought leader, a role that Rob Pike plays well. If you think Go would have gotten popular without having a Google and a Rob Pike behind it, then, well, I don't know what to tell you. I don't think Rust would have been popular either without the Mozilla association.

Or, more succinctly: I see no world in which Go having simple ML-style generics, without typeclasses or functors, would have made it any less popular. Other factors dominate when it comes to success of a programming language. TypeScript, in fact, shows that you can have generics that are more complex than those of Rust and still become wildly popular.

Re:Featherweight Go by tptacek on Monday June 01, 2020 @01:52AM (#23375775)
After a week (my first week, to be fair) of hacking on a serious Rust codebase, I'll give you one reason lack of generics might have been a marketing win for Go: I have never appreciated Go's compiler speed more than I do now.

But the bigger problem is just that Rust programmers use generics absolutely everywhere (my early impression is you basically can't avoid it, because of lifetimes), and it simply does make everything harder to understand. I know I'm going to be told that if I buckle down all of this stuff will make sense and I'll be fluent with it, and sure, I managed to grok Alexandrescu C++, too. But adding new layers of indirection everywhere just has to impede comprehension; that's always the tradeoff for parameterizing and indirecting!

The flip side of this is, I've built some fairly serious things in Go --- a compiler, a couple emulators, a disassembler, a symbolic evaluator; not just the server stuff Go is supposed to be good at --- and I have complaints about Go, but almost none of them are its lack of generics.

(There are things I like about Rust! But this isn't the thread for it.)

Re:Featherweight Go by benhoyt on Monday June 01, 2020 @04:01PM (#23383047)
What are your complaints about Go? I'm curious to know whether they match mine.
Re:Featherweight Go by ptomato on Sunday May 31, 2020 @07:10PM (#23373824)
- (removed by author; was too aggressive)
Re:Featherweight Go by pcwalton on Sunday May 31, 2020 @07:31PM (#23374016)
Edit: Removed my response. No worries :)
Re:Featherweight Go by ptomato on Sunday May 31, 2020 @07:44PM (#23374109)
Rereading that comment I do think I was being uncharitable and have removed it.

Reading the esbuild discussion at the time, it definitely read to me as "our language is definitely faster and if you're not getting the same performance you're holding it wrong", but looking at it now I can see how it wouldn't be intended that way.

Regardless, sorry; I think I was projecting some frustrations with the wider RESF on to you.

Re:Featherweight Go by kasey_junk on Sunday May 31, 2020 @07:45PM (#23374117)
And for what it’s worth I spend at least as much of my time wishing it had user defined generics as I do enjoying what it does have.

I’ve now resigned myself to wishing it treated its magic generics with proper typing.

Re:Featherweight Go by psanford on Sunday May 31, 2020 @07:56PM (#23374209)
A lot of us Go developers would probably say we like Go because "Go is useful" and leave off the rest.

You are right, Go got more initial momentum because it came out of google and had Rob and Ken's names attached to it. But the useful part is why people actually use it.

Re:Featherweight Go by m_sahaf on Monday June 01, 2020 @09:57AM (#23378459)
> Go is popular because of the names and organization behind it

I hear this a lot, but the counterexample is always Dart. Google is behind it, and Lars Bak is definitely not a nobody, yet the language struggled to gain momentum; not until Flutter came on the scene, and it wasn't an official Google project when it started.

Re:Featherweight Go by sebe on Monday June 01, 2020 @10:18AM (#23378711)
Lars gave a talk last year and said the intent was to put dart vm in chrome, then the whole mobile thing happen and there was no room for extra stuff in chrome. https://youtu.be/mPna6D21Eqg?t=480
Re:Featherweight Go by baby on Sunday May 31, 2020 @04:29PM (#23372442)
at least to me, the lack of generics was a benefit. I'm probably not alone :)
Re:Featherweight Go by xkapastel on Sunday May 31, 2020 @03:44PM (#23372086)
And why on earth would you say that?
Re:Featherweight Go by baby on Sunday May 31, 2020 @04:28PM (#23372435)
because it's a breeze to read Golang, due in parts to the lack of generics
Re:Featherweight Go by hombre_fatal on Sunday May 31, 2020 @07:39PM (#23374069)
Lack of generics just means you have to copy and paste everything, like any time you want to reverse a slice.

    for i := len(a)/2 - 1; i >= 0; i-- {
        opp := len(a) - 1 - i
        a[i], a[opp] = a[opp], a[i]
    }
Actively hurts reading code as you have to credentialize in a code base to begin to be able to file entire code blocks into copy and pasted "idioms".

Without generics you have to hope the stdlib gets a blessed generic function like reverse() one day since you can't build one without rolling your own monomorphization code-gen or a goofball interface{}+cast hack.

For people who supposedly prefer the lack of generics (which seems more like cargo culting or Stockholm Syndrome), no problem. We can just add a config option to golint that prohibits you from using generics. That way you don't need to hold up the rest of us. win-win.

Re:Featherweight Go by psanford on Sunday May 31, 2020 @08:42PM (#23374503)
Weird. While you could copy that from the SliceTricks Go wiki page, you could also just use `sort.Sort(sort.Reverse())` which seems to address all of your complaints.
Re:Featherweight Go by littlestymaar on Monday June 01, 2020 @05:10AM (#23376604)
But it uses an interface, which means dynamic dispatch and an allocation most of the time (because IIRC it tends to break the escape analysis).

That's a recurrent issue with Go: you can either have ergonomic tools (with interface and reflection), or performant code (with no allocation) but you generally can't have both at the same time. Sure it's better than scripting language where you need to use another language when you need performance, but it's still kind of sad.

Re:Featherweight Go by therealdrag0 on Sunday May 31, 2020 @05:17PM (#23372808)
Why does genetics make things that’s for read?
Re:Featherweight Go by zdragnar on Sunday May 31, 2020 @08:36PM (#23374452)
Functions can be given semantic names (I.e. have meaning); block statements cannot.

If writing a function that can take an array or slice of any type of data requires providing a generic argument (I.e. so you can specify that the function returns a slice of the same type of data as it was given), then you can name it "reverse" if it reverses the array, write it only once, and every timr you use it, you read "reverse" and know what it does.

For loops dont have those names, and so have to be rewritten every time you use them. As such, every time you see a for loop, you have to read and parse every statement to see what it is doing, and if it has any unexpected side effects or bugs introduced via copy-paste or what not.

Re:Featherweight Go by therealdrag0 on Monday June 01, 2020 @12:58AM (#23375574)
Sorry I meant to say “why do genetics make things harder to read?”. Tbh I can’t tell if you’re responding to that or not
Re:Featherweight Go by zdragnar on Monday June 01, 2020 @07:35PM (#23385371)
I did misread your post, but I will also say that generics are a double edged sword when it comes to readability. Needing to declare genetic types in function signatures can add irrelevant detail and heavy syntax. For example, look at the interpreter interface in this typescript file:

https://github.com/gcanti/io-ts/blob/master/src/Schema.ts#L2...

Granted, genetics don't need to be done that way, but it is among the more common and popular approaches. The type information is tangled up in the implementation, making focusing on either more challenging. Perhaps we need modes for syntax highlighting- one for types, one for implementation?