Live data from Hacker News

Go is Google's language, not ours

utcc.utoronto.ca

421–430 of 679 posts

Re: Go is Google's language, not ours

#421

For what it's worth I'm a semi-grey beard (20 years in) and I love golang. For me it was like going back to being 8 years old on my Commodore Plus/4 and really enjoying writing code again. It needs close parenting. Java has been ruined by the push to include everyone's pet feature.

So did the mess that C++ become.

Re: Go is Google's language, not ours

#422
post #149

I pity the recent CS graduates that weren't able to attend a decent CS degree and need Go to fit their mental model.

Go is a language for software engineering, which entails pragmatic human factors. It's not a computer science language, which emphasizes theory.

Eiffel and Ada are languages for proper software engineering.

Go not so much, specially given its toy type system, where one cannot even do Type Driven Design.

Re: Go is Google's language, not ours

#423
post #252

Earlier quoted context omitted.

Mostly machine learning for distributed sensor networks (ie: smart meters). Deal with lots of time-series data, state space modelling, some recurrent neural nets (etc). Our shop has a 'golang only' thing going, which means that I end up having to reimplement algorithms in go sometimes from scratch.

nice area, I would be interested to learn more into this type of problems. Recently, I became for interested in power electronics / smart grids / energy, and looking for the ways to get in touch with people working on such problems, learn more and join any company on these domains.

It depends on what you want to do as this industry is HUGE. Do you care about metering and working at the solar panel or wind farm level? Or maybe on the actual energy markets that commit and dispatch all generation in a region? Or maybe the vendors that write the software for those markets? Or you could work for the utilities or IPPs that own the generators...or the state public service commission that control state plans. There is also FERC and NERC. There are companies that sell energy storage systems...the list goes on and on.

Re: Go is Google's language, not ours

#424
post #391

I'm going to risk being labeled an ~incompetent dev~ or whatever but learning golang was seriously a breath of fresh air compared to literally any language I have ever tried to grok before. Everything felt like it was there on purpose. It always seemed like there was a "proper" way to achieve something. Being told to use this opinionated formatter was like removing a 40kg bag after a bush walk. You never have to worr…

> Being told to use this opinionated formatter was like removing a 40kg bag after a bush walk. I think the gofmt approach is becoming an unofficial standard. In the JS world 'prettier' has taken off and I think most languages now have a community anointed formatter (and new languages are likely to have an official one).

Yes, but they might be customizable. For example Rust has rustfmt but you can customize it. Which is a horrible approach imo.

Re: Go is Google's language, not ours

#425
post #101

Earlier quoted context omitted.

I think his fear of google's stewardship of the language is the fear of what it'll do to the community around it.

Its incredibly unlikely that Google would take decisions for the language that would make it less effective at what it does.

Empirically speaking, how did they do with dart?

Re: Go is Google's language, not ours

#426
post #424
post #391

Earlier quoted context omitted.

> Being told to use this opinionated formatter was like removing a 40kg bag after a bush walk. I think the gofmt approach is becoming an unofficial standard. In the JS world 'prettier' has taken off and I think most languages now have a community anointed formatter (and new languages are likely to have an official one).

Yes, but they might be customizable. For example Rust has rustfmt but you can customize it. Which is a horrible approach imo.

Agreed. Prettier, BTW, is specifically low customization.

Re: Go is Google's language, not ours

#427
> In practice we'll only get a chance to find out who Go really belongs to if Go core team members start leaving Google and try to remain active in determining Go's direction. If that works, especially if the majority of them no longer work for Google, then Go probably is their language, not Google's, in the same way that Python has always been Guido van Rossum's language regardless of who he worked for at the time.

This is laughable. Anything built within Google belongs to Google. There's no way the company will let anyone from the core team leave and take the language with them. Keep in mind, Google's version of Go and the community might be vastly different, as the former has different needs versus the latter.

Re: Go is Google's language, not ours

#428
post #155
post #138

Earlier quoted context omitted.

Given that the go core team has committed to adding generics I don't think it's fair to say they don't listen to critique from the community. Is there a more contentious issue in go?!

Not really, that is the hand waving when the issue ever pops up. Rob Pike already stated publicly that he is against the proposed idea for Go 2.0. "Rob Pike - Go 2 Draft Specifications" - https://www.youtube.com/watch?v=RIvL2ONhFBI

Wow. That makes me happy. The last thing we need in Golang are generics.

Re: Go is Google's language, not ours

#429
post #46
post #35

Earlier quoted context omitted.

I'm curious what the distinction is between Rust (driven by Mozilla) and Go (driven by Google).

Rust has largely broken out of Mozilla already. If it can maintain its growth rate (not guaranteed, but so far so good) it will have a future. Check back in five years.

It's a very different language than Golang though, very expressive, generics, no GC, etc.

Re: Go is Google's language, not ours

#430
post #110
post #17

Many like Go because it is an opinionated language. I'm not sure that a 'community' run language will create something like that because there are too many opinions. Many claim to represent the community, but not the community that doesn't share their opinion. Without clear leaders I fear technical direction and taste will be about politics which seems more uncertain/risky. I like that there is a tight cohesive group…

My thoughts exactly! It's important to have a community and to work with it, but, especially for a programming language, there has to be a clear concept of which features should be implemented and which not - just accepting community contributions for the sake of making the community feel good would be the wrong way. Otherwise you end up with a feature monster like innumerable other programming languages, and that's…

My fear is that they end up integrating generics just to please some vocal group of java/c++ programmers.
Post reply on HN