melle

If you like this, you might also like http://www.win.tue.nl/mcrl2/release/user_manual/index.html

The thing I find odd is the bugs in Chromium. Why would google drop support for spdy if their http2 implementation contains such (noticable?) bugs?

I suspect this doesn't only happen in the trending news feed. From my own experience: I shared an article by Douglas Roushkof (https://www.theguardian.com/technology/2016/feb/12/digital-c...) and several of my friends weren't able to see it, even after they opened my timeline.

See also the whitepaper of use-cases 2.0: https://www.ivarjacobson.com/publications/white-papers/use-c...

Looking at https://github.com/gin-gonic/go-http-routing-benchmark/blob/...

All echo benches have been commented out, last change about a year ago.

Tests do not use echo's fasthttp engine.

Do you have any experience with gin?

If so, why do you prefer echo over gin?

Thanks

I'm not sure this is the case, at least not according to the benchmarks in the gin-gonic/gin repo.

This framework was submitted to HN before:https://news.ycombinator.com/item?id=9296524

In that discussion the author of gin mentions gin has a zero allocation router as well https://github.com/gin-gonic/gin/issues/249

On mobile right now, will look at the gin/echo benchmarks later (especially if the gin benchmarks compare the fasthttp engine of echo)

This book is open source: https://github.com/astaxie/build-web-application-with-golang...

To those with suggestions related to e.g. security pratices, step up and contribute!

The actual archive is at http://www.montreuxjazz.com

Completely off-topic, but I really like the logo. Who made it?

How is this different from bcrypt?

From the changelog: > Builds in Go 1.5 will be slower by a factor of about two. The automatic translation of the compiler and linker from C to Go resulted in unidiomatic Go code that performs poorly compared to well-written Go. Analysis tools and refactoring helped to improve the code, but much remains to be done. Further profiling and optimization will continue in Go 1.6 and future releases.

This seems quite a drastic change. I thought compilation speed was one of the pilars of go. In that light, why did they decide to release this anyway?

This is some great advice, nice post!

Too bad the article only focuses on the success stories. I for one would be really interested to know how many failed/abandoned side projects they created and how they relate to the successful ones.

In this example text balloons are more clear for me. The background of the balloon seems to 'tie' the comment to the user, and it's easier to spot the end of a comment. In the minimal chrome example you need a line to separate comments which is less distinctive, i guess this makes it harder for me to notice

Fun game, i like it!

Minor: In the gameover pop-up the social buttons only show the facebook logo, though the links point to fb/twitter/plus