8 ms·
What's coming in Go 1.12 [slides]
- mockindignant 8y agoThis site is horrible on mobile. Probably the worst I have ever seen. Totally unusable.
- Insanity 8y agoYeah indeed, can't even really read it like this. I get that some websites might not scale well, but this just goes beyond that. :(
- mixedCase 8y agoThey're slides, not a website.
- zeroxfe 8y agoNot sure what the point of your comment is, but that's a website presenting slides.
- 4ad 8y agoNo, 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.
- zeroxfe 8y agoPowerpoint does work on mobile ;-)
- ainar-g 8y agoPlain text version here: https://raw.githubusercontent.com/mvdan/talks/master/2018/go1.12-pre.slide https://raw.githubusercontent.com/mvdan/talks/master/2018/go.... Also, it is an issue: https://github.com/golang/go/issues/27026 https://github.com/golang/go/issues/27026. Marked as "help wanted".
- tyingq 8y agoThe 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.
- mattnewton 8y agoForcing the desktop view is still pretty unusable on iOS Safari for me.
- tyingq 8y agoForcing 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?
- mattnewton 8y agoThe raw text version should just be the link. Who wanted the slide deck version?
- agumonkey 8y agonever heard of this plain text programming paradigm, very powerful
- ainar-g 8y agoDirect link to the draft release notes: https://tip.golang.org/doc/go1.12 https://tip.golang.org/doc/go1.12.
- weberc2 8y agoLooks 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?).
- ainar-g 8y agoThe rationale is here: https://github.com/golang/go/issues/25443 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.
- tptacek 8y agoChanges to the language spec? It's 1.11->1.12, not 1.11->2.0.
- weberc2 8y agoIt 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".
- tptacek 8y agoIt's literally a minor release. That's what an increment in the numbers on the right of the decimal point means.
- rollulus 8y agoHow many Go versions is it going to take for that slide viewer to work on mobile?
- denormalfloat 8y agoRequesting the Desktop site actually works, surprisingly.
- haneefmubarak 8y agoAm 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.
- pjmlp 8y agoUntil some manager on Go team decides to try to read them on his/her mobile device.
- pilif 8y agoSwipe left to advance a slide. Swipe right to go back.
- freyir 8y agoThat’s not the problem. The problem is I can only see about 50% of the slide, and pinch-to-zoom doesn’t work.
- pilif 8y agoIt’s fine in landscape
- Sharlin 8y agoThe 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.
- Thaxll 8y agoruntime: 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.
- deleted 8y ago[deleted]
- mholt 8y agoTLS 1.3 support, strangely omitted from these slides: https://github.com/golang/go/issues/9671 https://github.com/golang/go/issues/9671
- deleted 8y ago[deleted]
- mlindner 8y agoI find it curious they implemented it themselves instead of using a standard library like OpenSSL/LibreSSL.
- TheDong 8y agoThey 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 https://github.com/golang/go/issues/1435
- ilovecaching 8y agoI'm actually super excited about printing maps in sorted order. I have a CLI use case for this. When I need a real language with a fleshed out type system I use Rust, but Go has been great for writing small CLIs and things where I'm the only developer. It's also been great for small fan out tasks. I do wish flags had a way to do subcommands that didn't involve a lot of boilerplate.
- sethammons 8y agoWhat is lacking to qualify Go as a "real" language?
- octonion 8y agoOperator overloading?
- ilovecaching 8y ago- no generics. Without generics you can't build reusable data structures or algorithms that are type safe. The only ones that are available are hard coded into the language. - lacking sum types (enums), which is why you have to explicitly check every return value with if err != nil. Sum types enable useful patterns like Maybe, Either, etc. - general wackiness, from a computer science perspective Golang bakes a lot of special cases into its semantics that could be handled by including fundamental types. If you want to do multi-value return, the sane thing is to use a tuple, which is a core data structure we all learn about in CS undergrad, and use that as a return type and have functions return a single value. This is how Python and Rust work. (Tuples are also useful in many other contexts). The Go way is to have a rule that a function can return multiple values from a function and receive them at a call site. It's not pattern matching, and its not tuples, it's just a special case that defies the mathematical model of a function (a mapping of a domain to a single codomain).
- papaf 8y agoAs someone who enjoys programming in both Go and Rust I find this sort of fanatical comment distressing. Go makes different tradeoffs. Get over it. Nobody has written anything as important as Kubernetes in Rust yet. I hope that someday somebody does write something worthwhile but please less of the fundamentalist attitude that had poisoned religion and politics.
- alexandernst 8y agoCompletely 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.
- alexandernst 8y agoIs the GOPATH bullshit gone already?
- Skunkleton 8y agohttps://github.com/golang/go/wiki/Modules https://github.com/golang/go/wiki/Modules
- the_clarence 8y agoDoesn’t work on mobile