-
Go 1.6 beta1 and Apple’s new HTTP/2 push notification service both were released today. What timing!
-
Based on the post and the Hacker News thread, contributions will be made through Gerrit which will be the primary git repository. GitHub will mirror it, and the issues and wiki are being ported over to GitHub.
This won’t be happening until after the Go 1.4 release in December.
-
If you feel this story should’ve also been tagged with “swift”, please see this meta story: https://lobste.rs/s/dr4wif/please_add_a_tag_for_apple_s_swift_language
-
The traditional means is to submit a story that is related via some other tag, and then mention something in the comments to determine if there’s interest in it. Also, take a look through the meta tag to see how some other people approached it.
-
Hi Kyle. I posted this story that contrasts Go and Swift but I couldn’t also tag it with swift. https://lobste.rs/s/nd1pi1/go_is_a_shop-built_jig
It is my first time posting to Lobste.rs, and I just signed up recently. I didn’t even know there was a meta tag and what it was for. jcs hasn’t made it very clear what to do for missing tags. See the linked GitHub issue above.
-
-
This deserves a mod up for the pictures alone. But good read, too.
-
Thanks. It was a lot of fun making those packages and then taking gopher pictures.
I have an album with more gopher photos on Google+.
-
@nathany: have you found this HTTP2 interface to be any faster or handle errors better than their current binary interface?
Error handling is miles better because it’s a regular HTTP response. In the previous interface an error could cause the connection to drop well after several other notifications were sent. There was a bunch of bookkeeping to ensure messages weren’t lost.
As far as performance, I haven’t done any kind of benchmarks. The main thing is that this new Notification API is way easier to work with, but without the performance sacrifices that would’ve been required with HTTP/1.1.