What's coming in Go 1.12 [slides] | Hacker News Reader

What's coming in Go 1.12 [slides]

blog.myitcv.io

103 pointsguessmyname56 comments

Open articleView on HN

How many Go versions is it going to take for that slide viewer to work on mobile?

Requesting the Desktop site actually works, surprisingly.

Am on latest chrome on Android; half of the slide is obscured even in landscape with desktop mode on.

That's just an awful viewer at the end of the day, no ifs and buts about it.

Until some manager on Go team decides to try to read them on his/her mobile device.

Swipe left to advance a slide. Swipe right to go back.

That’s not the problem.

The problem is I can only see about 50% of the slide, and pinch-to-zoom doesn’t work.

It’s fine in landscape

The problem, at least on Safari, is that about 75% of each slide is outside the viewport, no matter what orientation. And pinch zoom doesn’t work, neither does scrolling by swiping.

It's too zoomed in and zooming out doesn't work.

The source is at least readable on mobile. https://github.com/mvdan/talks/blob/master/2018/go1.11.slide

Direct link to the draft release notes: https://tip.golang.org/doc/go1.12.

Looks like a very minor release. No changes to the language spec and the changes to the standard library are all marked "minor". The most significant thing is the deprecation of `godoc`'s command-line features in favor of `go doc` (maybe someone with more info could explain the difference between the tools or the rationale for having two similarly named tools and why the CLI features are moving from one and into the other?).

The rationale is here: https://github.com/golang/go/issues/25443.

>Now that we have the cmd/go "go doc" CLI for getting documentation, does it make sense for x/tools/cmd/godoc to also have CLI support?

>I propose we delete x/tools/cmd/godoc's CLI support and keep it being a web-only tool. Users who want CLI support can use "go doc". Both are shipped with Go releases.

It's a deduplication of code and effort.

Changes to the language spec? It's 1.11->1.12, not 1.11->2.0.

It looks like you're trying to point out an inconsistency with my post, but I'm not seeing it. My observation, "No changes to the language spec" is entirely consistent with my claim, "a very minor release" and your observation, "It's 1.11->1.12, not 1.11->2.0".

It's literally a minor release. That's what an increment in the numbers on the right of the decimal point means.

Is this a bad attempt at pedantry? “Minor” WRT version numbers doesn’t mean “boring” or “insignificant”. Go introduced modules in a minor version, for example. Other minor versions cut GC pause times considerably. Others improved compile times a bunch. It’s pretty clear that the aforementioned changes are all more significant/interesting than anything in 1.12.

Changes to the language spec do not have to be backward incompatible. 8 of the 11 Go 1.x releases have had changes to the language spec.

TLS 1.3 support, strangely omitted from these slides: https://github.com/golang/go/issues/9671

I find it curious they implemented it themselves instead of using a standard library like OpenSSL/LibreSSL.

They implement everything themselves, in part so you can build truly static libraries without paying the significant cgo tax.

The biggest thing they implemented themselves is effectively their own linux libc (including dns and networking stack).

This results in wonderful bugs like them not having a working POSIX Setuid [0] because that's implemented correctly in libc, not the linux syscall of the same name. This release also contains the UserHomeDir function which is another example where they didn't use libc and thus implemented it incorrectly.

You have to justify using any outside libraries in the go stdlib because right now there are no required external dependencies, so adding one is a very high bar indeed.

[0]: https://github.com/golang/go/issues/1435

runtime: non-cooperative goroutine preemption github.com/golang/go/issues/24543

HUGE deal for large companies Possible for certain code patterns to bully the runtime Redesign the runtime to remove those edge cases

wow.

Doesn’t work on mobile

This site is horrible on mobile. Probably the worst I have ever seen. Totally unusable.

Yeah indeed, can't even really read it like this.

I get that some websites might not scale well, but this just goes beyond that. :(

They're slides, not a website.

Not sure what the point of your comment is, but that's a website presenting slides.

No, it's presentation software that's implemented via a website. The primary user of this software is the person giving the talk, not people on the internet. The fact that people on the internet can also see it is a bonus that comes with the choice of the implementation.

Complaining that this doesn't work on mobile is like complaining Powerpoint doesn't work on mobile.

Powerpoint does work on mobile ;-)

Plain text version here: https://raw.githubusercontent.com/mvdan/talks/master/2018/go....

Also, it is an issue: https://github.com/golang/go/issues/27026. Marked as "help wanted".

The issue isn't describing what I see on Android. It's chopped off on the left and I can't zoom out. Not usable at all. As mentioned elsewhere, forcing the desktop view is better.

Forcing the desktop view is still pretty unusable on iOS Safari for me.

Forcing desktop "works" in portrait mode on my Android, but the text is pretty small. Landscape is cut off.

Interesting though, that iOS Safari is borked too. Did they just take wild guesses on the mobile css and hope for the best?

The raw text version should just be the link. Who wanted the slide deck version?

never heard of this plain text programming paradigm, very powerful

Is the GOPATH bullshit gone already?

https://github.com/golang/go/wiki/Modules

Completely unreadable on a phone. And the entire thing is 3 slides, from which the first one is the title and the last one are the credits and links.

Reply on news.ycombinator.com