Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- guessmyname.
- * rollulus: How many Go versions is it going to take for that slide viewer to work on mobile?
- ** pilif: Swipe left to advance a slide. Swipe right to go back.
- *** Sharlin: 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.
- *** freyir: That’s not the problem.<p>The problem is I can only see about 50% of the slide, and pinch-to-zoom doesn’t work.
- ** pjmlp: Until some manager on Go team decides to try to read them on his/her mobile device.
- ** denormalfloat: Requesting the Desktop site actually works, surprisingly.
- *** haneefmubarak: Am on latest chrome on Android; half of the slide is obscured even in landscape with desktop mode on.<p>That's just an awful viewer at the end of the day, no ifs and buts about it.
- * ainar-g: Direct link to the <i>draft</i> release notes: <a href="https://tip.golang.org/doc/go1.12" rel="nofollow">https://tip.golang.org/doc/go1.12</a>.
- ** weberc2: 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?).
- *** ainar-g: The rationale is here: <a href="https://github.com/golang/go/issues/25443" rel="nofollow">https://github.com/golang/go/issues/25443</a>.<p>><i>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><p>><i>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.</i><p>It's a deduplication of code and effort.
- *** tptacek: Changes to the language spec? It's 1.11->1.12, not 1.11->2.0.
- **** etaoins: 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.
- **** weberc2: 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".
- ***** tptacek: It's <i>literally</i> a minor release. That's what an increment in the numbers on the right of the decimal point means.
- ****** weberc2: 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.
- * mholt: TLS 1.3 support, strangely omitted from these slides: <a href="https://github.com/golang/go/issues/9671" rel="nofollow">https://github.com/golang/go/issues/9671</a>
- * Thaxll: runtime: non-cooperative goroutine preemption
- github.com/golang/go/issues/24543<p>HUGE deal for large companies
- Possible for certain code patterns to bully the runtime
- Redesign the runtime to remove those edge cases<p>wow.
- ** nil.
- * mockindignant: This site is horrible on mobile. Probably the worst I have ever seen. Totally unusable.
- ** ainar-g: Plain text version here: <a href="https://raw.githubusercontent.com/mvdan/talks/master/2018/go1.12-pre.slide" rel="nofollow">https://raw.githubusercontent.com/mvdan/talks/master/2018/go...</a>.<p>Also, it is an issue: <a href="https://github.com/golang/go/issues/27026" rel="nofollow">https://github.com/golang/go/issues/27026</a>. Marked as "help wanted".
- *** tyingq: 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.
- **** mattnewton: Forcing the desktop view is still pretty unusable on iOS Safari for me.
- ***** tyingq: Forcing desktop "works" in portrait mode on my Android, but the text is pretty small. Landscape is cut off.<p>Interesting though, that iOS Safari is borked too. Did they just take wild guesses on the mobile css and hope for the best?
- *** mattnewton: The raw text version should just be the link.
- Who wanted the slide deck version?
- *** agumonkey: never heard of this plain text programming paradigm, very powerful
- ** Insanity: Yeah indeed, can't even really read it like this.<p>I get that some websites might not scale well, but this just goes beyond that. :(
- ** mixedCase: They're slides, not a website.
- *** zeroxfe: Not sure what the point of your comment is, but that's a website presenting slides.
- **** 4ad: 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.<p>Complaining that this doesn't work on mobile is like complaining Powerpoint doesn't work on mobile.
- ***** zeroxfe: Powerpoint does work on mobile ;-)
- * alexandernst: 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.
- * alexandernst: Is the GOPATH bullshit gone already?
- ** Skunkleton: <a href="https://github.com/golang/go/wiki/Modules" rel="nofollow">https://github.com/golang/go/wiki/Modules</a>
- * ilovecaching: I'm actually super excited about printing maps in sorted order. I have a CLI use case for this.<p>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: What is lacking to qualify Go as a "real" language?
- *** ilovecaching: - 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.<p>- 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.<p>- 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: As someone who enjoys programming in both Go and Rust I find this sort of fanatical comment distressing.<p>Go makes different tradeoffs. Get over it.<p>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.
- ***** steveklabnik: Co-signed. (Though I’m not <i>totally</i> sure I agree re:kubes, but that’s not really the important part.)
- *** octonion: Operator overloading?
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
