Live data from Hacker News

Go 1.7 is released

blog.golang.org

101–110 of 141 posts

Re: Go 1.7 is released

#101
post #22

Earlier quoted context omitted.

I suggest giving Ruby a try too. I find it great for both web dev and local automation scripts. You can do pretty much anything you can do in bash but with clearer and shorter code. I've been writing all my non-trivial automation code in Ruby for years. Rails is just a popular web framework for Ruby, there's a lot more the language can do.

I'd second this. Rails is still probably the fastest way to get an MVP off the ground, and most of the time it's more than fast enough. You can get UX on par with a well done SPA almost entirely using server code with Turbolinks 5 + Action Cable, too.

The fastest way to get an MVP off the ground is to use the tools you know best. It doesn't have to be Rails :)

Re: Go 1.7 is released

#102

Earlier quoted context omitted.

The faster compilation time & speed up is quite real in our real life prod application. From Go 1.6 to 1.7: Test suite (CI), from 3:34 to 1:48 Docker image building, from 3:05 to 1:50 https://twitter.com/mattetti/status/763913903600349184

On our code base, we're seeing >2x build speed increases vs. go 1.6! Compiling the entire go monorepo, including vendored dependencies, dropped from 73 seconds to 29 on 4 CPUs when moving from 1.6.3->1.7rc6. Huge improvements to CI times, when amortized across go build, go test, docker builds etc.

[deleted]

Re: Go 1.7 is released

#103
post #91

Earlier quoted context omitted.

Why is it 'clearly' on its way out? IMO Rails is still the best web framework around, and the last release has really put it ahead of its closest competition.

Not really, https://www.techempower.com/benchmarks/

I wasn't making a statement about performance. That has very little to do with most web development.

Re: Go 1.7 is released

#104
post #91

Earlier quoted context omitted.

Not really, https://www.techempower.com/benchmarks/

I wasn't making a statement about performance. That has very little to do with most web development.

On my little part of the world, performance always plays a role in web development.

It is even described in many of the project contracts.

Re: Go 1.7 is released

#105

The semantics of Go is too ugly. It has no taste.

It's also a necessary "evil" to demonstrate that languages should have the right amount of features, no more and tools are part of a language, along with ease of deployment. It's is questionable whether Go strikes the right balance when it comes to features vs "simplicity" though, but it might inspire better solutions in the future. I think MSFT is trying to follow the same path with .net core and its tool chain, I h…

>I hope they succeed as C# and F# are vastly superior to Go.

In number of features, yes. Everything else and you come off as opinionated. I cannot comfortably write C# from my Linux workstation since all the tools are Windows-first.

C# is a language where everything must be done in classes and inherits a C++/Java school of OOP which I find abhorrent as it tends to favor monstrosities of abstraction upon abstraction. I can almost always read a Go codebase and get a good general sense of what it's doing in a few minutes, I can't say the same about C# codebases, and I have worked with C# for around the same time I've worked with Go.

These things aren't clear cut for everyone the same way.

Re: Go 1.7 is released

#106
post #39

Earlier quoted context omitted.

It was more expedient to start with the Plan 9 tool chain that we had at the time. Ken was already familiar with the code base, which was small and compiled quickly (a few seconds). Because of this we got a lot done quickly, knowing that we would eventually modernize the compiler.

How much is Ken involved in the language today?

Ken is not really involved in the project these days. His last commit was in 2011, before Go 1 was even released.

Re: Go 1.7 is released

#107

Earlier quoted context omitted.

> I suggest giving Ruby a try too. If you like Go, I don't see much reason to try Ruby except intellectual curiosity. Ruby is clearly a language on its way out and it is not just a lot slower than Go, it's also dynamically typed.

Why is it 'clearly' on its way out? IMO Rails is still the best web framework around, and the last release has really put it ahead of its closest competition.

Ruby is too forgiving, has multiple syntaxes for the same thing, and lets people do really obscure shit in a large codebase (monkey patching, hidden imports, etc). In short: it enables developer laziness.

I've found Ruby code the hardest to debug over the years. Also, I think the web development community is waking up to the value of type safety.

I will use Ruby for the occasional script because I like its backtick syntax for invoking other commands, but that's it.

Re: Go 1.7 is released

#108
post #23

Ok, off topic question. Not an expert in grammar, but something about "Go 1.7 is released" seems wrong to me. Anyone could tell me if this is an correct usage of grammar? Edit: Dont know why so many downvote, but it is a honest question.

>Go 1.7 is released

The is is redundant which may be why it doesn't scan well for you.

GO 1.7 released

Works much better, no?

Re: Go 1.7 is released

#109

https://github.com/golang/go/commit/a62ae9f62fcfca02075b70e6... > SystemCertPool returns an error on Windows. Maybe it's fixable later This doesn't inspire confidence in Go as a cross platform language which is at version 1.7. If this is implemented in say 1.8, am I supposed to check for Go versions in order to know if the SystemCertPool func works or not? I mean why not just release it when it works on all tier-1 su…

Thanks for the reminder. I've filed:

https://github.com/golang/go/issues/16736

We actually try hard not to do platform-specific stuff, but in this case it seemed worth it, considering the problems people were having with cert validations and how Windows differs in how it validates TLS connections.

Re: Go 1.7 is released

#110
post #99

I wish the Clojure compiler was half as fast as Go's :( I'm not much of a fan of using Go for anything 'big', but I have taken to using it in places where I would have previously used Python (tiny/simple services, housekeeping/utility scripts fired by cron, etc.) I'd love to use Go at work (amongst many other things), but my employer already gives me a hard time for writing small utilities in Python rather than Java…

What makes you choose Go over Python for simple services and utility scripts? (I'm just learning Go but would heavily lean towards Python for those things)

Off the top of my head:

- Ease of deployment. It's a standalone binary - I don't have to ensure python and all needed libraries are installed/configured.

- I like Go's standard library - it usually has everything I need to whip up a basic network service easily.

- Better/easier concurrency support.

- It's faster than Python (though that's usually not incredibly important most of the time).

Post reply on HN