benhoyt

37 ms·

451.
Searching Code with Sourcegraph(lwn.net)
11 points by benhoyt 6y ago|1 comments
452.
by benhoyt 6y ago
I think the link should be changed to the 1.15 release notes (now published): https://golang.org/doc/go1.15 -- these are much more interesting and useful.
453.
ZZT Stories: The Reconstruction(blog.asie.pl)
1 points by benhoyt 6y ago|0 comments
454.
by benhoyt 6y ago
I was interested to see the section, "A lawyer's physical attractiveness" -- it reminded me of a few years ago when my wife was supporting a friend during a messy divorce by being present in court with her. Both parties'
455.
Go Filesystems and File Embedding(lwn.net)
2 points by benhoyt 6y ago|0 comments
456.
Different approaches to HTTP routing in Go(benhoyt.com)
1 points by benhoyt 6y ago|0 comments
457.
A Look at Dart(lwn.net)
3 points by benhoyt 6y ago|0 comments
458.
Scalability but at What Cost? (2015)(frankmcsherry.org)
2 points by benhoyt 6y ago|1 comments
459.
by benhoyt 6y ago
I've recently started writing for LWN and have written nine articles now: https://lwn.net/Archives/GuestIndex/#Hoyt_Ben It's definitely a stringent style and editing process -- I find it good discipline.
460.
by benhoyt 6y ago
It's true, but I've used patterns like this to good effect: { "_COMMENT": "default; override with --s3-bucket", "s3_bucket": "foo-bar" }
461.
The sad, slow-motion death of Do Not Track(lwn.net)
19 points by benhoyt 6y ago|4 comments
462.
NanoLog: A Nanosecond Scale Logging System (2018)(usenix.org)
1 points by benhoyt 6y ago|0 comments
463.
What's New in Lua 5.4(lwn.net)
138 points by benhoyt 6y ago|131 comments
464.
How to write technical posts so people will read them (2019)(reasonablypolymorphic.com)
257 points by benhoyt 6y ago|54 comments
465.
Hugo: A Static-Site Generator(lwn.net)
2 points by benhoyt 6y ago|0 comments
466.
Generics for Go(lwn.net)
2 points by benhoyt 6y ago|0 comments
467.
More Alternatives to Google Analytics(lwn.net)
4 points by benhoyt 6y ago|2 comments
468.
by benhoyt 6y ago
I actually use GoAccess on my personal site, which runs on GitHub Pages. Obviously you don't get the actual web server logs (only GitHub has those), but I have a few lines of JavaScript that hits a 1x1 image on CloudFront with the page
469.
Lightweight Alternatives to Google Analytics(lwn.net)
2 points by benhoyt 6y ago|1 comments
470.
by benhoyt 6y ago
What would be a real-world example of what you're referring to ("implement your own interfaces on built-in types")?
471.
by benhoyt 6y ago
I started to write one in the "Go 2 playground", but then realized they had that exact example in the draft design: func Keys(type K comparable, V interface{})(m map[K]V) []K { r := make([]K, 0, len(m)) for k := range
472.
An introduction to Go for non-Go developers(benhoyt.com)
3 points by benhoyt 6y ago|0 comments
473.
by benhoyt 6y ago
Agreed. Or as I've heard it said, "microservices solve a people problem, not a technical one". This is certainly how they were pushed at my current workplace -- it was all about "two-pizza teams being able to develop and
474.
by benhoyt 6y ago
My brain. Which is true :-) ... but maybe more what you are asking: a todo.txt file, as well as my personal website with my public writing -- that's as much for my memory/knowledge as anyone else's.
475.
by benhoyt 6y ago
I don't disagree with this from a design point of view (I'm not a designer), but I can't stand the modern web thing of "I'm using a fancy custom font, so you'll see website load and then flash over to the corre
476.
by benhoyt 6y ago
What are your complaints about Go? I'm curious to know whether they match mine.
477.
by benhoyt 6y ago
As I read the first five items on that list, each one made me think more and more "then isn't the answer to not write distributed systems?". But then the last item gives almost the opposite advice: "Extract services&quot
478.
ZZT in Go (using a Pascal-to-Go converter)(benhoyt.com)
1 points by benhoyt 6y ago|0 comments
479.
Testing in Go: Philosophy and Tools(lwn.net)
1 points by benhoyt 6y ago|0 comments
480.
by benhoyt 6y ago
> although I really don't think the lack of namespaces it what has hindered Awk from widespread use I agree (I side more with Kernighan than Robbins here). My take on what hindered it from larger-scale use: lack of a big standard li

More ›