Ask HN: HTTP Path vs. Query Parameters
2 pointsby lunch3 comments
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”).
Loading failed for the <script> with source “https://you.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js”. > No Generics
The lack of generics was something I was hung up on, too, but TBH I haven't found myself reaching for them for a while now. > Error handling
This is not a problem for me, either. I can easily handle different `error` types and if I want to provide more context I pull in github.com/pkg/errors > gofmt
gofmt is great > go test
go test has been totally sufficient for me and I was quickly writing and running tests. The testing package itself is builtin and writing tests is dead simple. > dep / dependency stability
Dependency management has been a huge PITA with Go and is my largest complaint. Personally, I've used everything go GB vendor, godeps, glide, and now dep. dep has been Just Working for me and is decent enough working on a team. As for dumping the dependency code in your source tree-- it lives in a folder called ./vendor so it's easy enough to not look at it.
Yet the website is a blank white page, without JavaScript.