Live data from Hacker News

I’m joining the Go team at Google

spf13.com

31–40 of 211 posts

Re: I’m joining the Go team at Google

#31
>As I had before, I recognized that this technology had the potential to revolutionize how software was written at a fundamental level.

Congrats and all, and I love Hugo (use it all the time).

That said, I think the kool-aid was spiked with something.

Sorry, but in what way is Go "revolutionizing"?

I'd buy "refreshing simplicity" and "yay, static builds again" but it's hardly revolutionary, even in its most touted feature (channels).

And it hardly changed how people write software. At best, it introduced some dynamic language programmers to static types and static builds.

All the rest, including creating a language that's easy for average programmers to program at scale was already the goal, and a success at that, of Java.

Re: I’m joining the Go team at Google

#32
post #10

> Go has the nearly perfect balance of readability, expressibility and simplicity Is Go really expressive?

It is pretty readable, but really non-functional too. Eg, they still don't have math.round and you wind up writing a lot of code because it can be a little bare bones or does things in a way that isn't quit usable. I wouldn't say it is very expressive either. Go can be very wordy and verbose at times, and some things are downright a pain or poorly thought out (e.g, while Java has finally and C++/Rust have RIAA for de…

... R-RIAA? You probably meant RAII right: http://www.riaa.com/

Resource management by litigation sounds innovative though

Re: I’m joining the Go team at Google

#34
post #10

> Go has the nearly perfect balance of readability, expressibility and simplicity Is Go really expressive?

It is pretty readable, but really non-functional too. Eg, they still don't have math.round and you wind up writing a lot of code because it can be a little bare bones or does things in a way that isn't quit usable. I wouldn't say it is very expressive either. Go can be very wordy and verbose at times, and some things are downright a pain or poorly thought out (e.g, while Java has finally and C++/Rust have RIAA for de…

> It is pretty readable, but really non-functional too

There are projects starting to fix that: https://github.com/asteris-llc/gofpher

Re: I’m joining the Go team at Google

#35
post #27

I'm using C# mainly because of debugger integration in Visual Studio. Make decent visual debugger and devs will come.

What are you developing with C#? I see Go more for server-side stuff, and C# for Unity/Desktop development...

some legacy Windows server stuff - part of this could be rewritten to Linux/Go/whatever_server_lang just team mates are not willing to leave their comfortable VS env. if not provided with decent IDE/debugger

Re: I’m joining the Go team at Google

#36
post #11
post #4

Why do people find the need to write about themselves in third person? https://stevefrancia.com/

As a habit it is bad, but this is actually standard for short bios. It allows it to be dropped in place directly for conferences, PR shots, news articles, etc without any rewrite.

Great to make it look like someone took the time to do a bio about you because you're important, while it's just you writing. Lack of self-confidence if you ask me.

Re: I’m joining the Go team at Google

#37
post #3

> What is missing from the Go ecosystem? Personally, golang "IDE" experience is not as good as Java or even C++. For example, ycmd only supports subset of functions for golang. I miss ycmd-goto-references the most.

My main iusses:

-) A proper package manager. (no, go get is not enough. They have realized this and have a team coming up with a draft for an official one)

-) Well written, well maintained libraries that do proper releases. There are very few of those out there. Might get better with an offical package manager and ideally package repository a la npm/crates.io

-) Generics. This will help the previous point also. Often it's hard to write proper reusable libraries due to the lack of generics. And no, they didn't keep generics out because they are to complicated for the language users. They just (quote) "didn't find a good way to implement them", and big language changes like that are out of scope before 2.0.

-) Macros probably won't ever come, but if not, please at least give us a language construct that reduces error handling boilerplate. (Rust has some nice macros for that).

Re: I’m joining the Go team at Google

#39
post #10

> Go has the nearly perfect balance of readability, expressibility and simplicity Is Go really expressive?

Not really. It's very verbose compared to Python, almost like Java.

Noo that's an overstatement.

Of course it's not as clean as Python, it's statically typed.

But type inference makes code way cleaner than your typical Java code (Javas type inference is improving, though).

Re: I’m joining the Go team at Google

#40
post #11

Earlier quoted context omitted.

As a habit it is bad, but this is actually standard for short bios. It allows it to be dropped in place directly for conferences, PR shots, news articles, etc without any rewrite.

Great to make it look like someone took the time to do a bio about you because you're important, while it's just you writing. Lack of self-confidence if you ask me.

Lack of self-confidence if you ask me.

How do you figure? Every time I've been asked for a bio for a conference or similar, they've asked for it in third person. Reading bios in conference proceeding in first person would just come across as weird to me.

Post reply on HN