Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
badrequest
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
61.
▲
by
badrequest
3y ago
Treating a context value as a bag to fetch data out of is the first mistake. They should only ever be used to control things like deadlines and whether or not a part of a function executes. IMHO they should disallow attaching values to a co
62.
▲
by
badrequest
3y ago
IIRC Roblox was using Consul
63.
▲
by
badrequest
3y ago
> Tan, for his part, apologized over the weekend, noting that his post was a reference to a Tupac Shakur lyric Ah, so if it's a quote, it doesn't matter, because even though you've decided when to use them, they're no
64.
▲
by
badrequest
3y ago
Even if they use in-house counsel? I would assume having salaried lawyers lowers the cost of registering that many patents at least a little, but I suppose it could also end up still being $1B.
65.
▲
by
badrequest
3y ago
"Why are people making new tools instead of using the antiquated ones I'm familiar with?"
66.
▲
by
badrequest
3y ago
Pages predates Microsoft's acquisition, and I can use Copilot on the repos I commit to any other source control system.
67.
▲
by
badrequest
3y ago
Those posts are an HN staple, this place wouldn't be the same without it. I think I've been using GCP longer than most people's projections of how long it would last.
68.
▲
by
badrequest
3y ago
"This tech will only make people dumber over time" was also claimed about the Internet.
69.
▲
A Comparison of Hugo Nomination Distribution Statistics
(alpennia.com)
1 points
by
badrequest
3y ago
|
0 comments
70.
▲
by
badrequest
3y ago
what a great platform for free speech when you can get banned for angering a billionaire
71.
▲
by
badrequest
3y ago
This basically doesn't happen, mostly an urban legend.
72.
▲
Err != nil is good (and why) [video]
(youtube.com)
1 points
by
badrequest
3y ago
|
1 comments
73.
▲
by
badrequest
3y ago
Protected from what, end-to-end encryption?
74.
▲
by
badrequest
3y ago
I remember seeing a talk[1] at Gophercon a while back on how nightmarish macaroons were to implement. [1] https://www.youtube.com/watch?v=MZFv62qz8RU
75.
▲
by
badrequest
3y ago
`docker system prune --force --all --volumes` and they're gone.
76.
▲
by
badrequest
3y ago
"What if I had significantly increased barriers to doing this very inappropriate and deeply weird thing?"
77.
▲
by
badrequest
3y ago
It should, obviously, be necessary to do this.
78.
▲
Preventing Problems with Generated Files
(blog.verygoodsoftwarenotvirus.ru)
1 points
by
badrequest
3y ago
|
0 comments
79.
▲
by
badrequest
3y ago
Is it a race between those three when the public can only use two of them?
80.
▲
by
badrequest
3y ago
I've been watching folks here on HN speculate that Google will kill GCP "any minute now" for at least the last 4 years, so ya'll can keep holding your breath, I will be having fun deploying things for 1/10th the pri
81.
▲
by
badrequest
3y ago
If it doesn't scale down to zero, then it doesn't compete with Cloud Run.
82.
▲
by
badrequest
3y ago
Recently tried writing some async Rust to compare the error handling when nested async calls are made to how errors are handled in Go, and it seemed like the trivial example I was trying to write up simply couldn't be done without invo
83.
▲
by
badrequest
3y ago
It also prevents adding relevant context to the errors, meaning you get all the joy of hunting through call stacks to figure out what went wrong in a sufficiently complex program.
84.
▲
by
badrequest
3y ago
Coincidences can happen. :)
85.
▲
by
badrequest
3y ago
I genuinely have no idea what you're referring to by "stringly-typing all over stdlib". I've written Go every day for the better part of a decade and used the standard library the whole time. What standard library functi
86.
▲
by
badrequest
3y ago
This pattern already works and would work with this change, you'd just need to define `/foo/bar` first.
87.
▲
by
badrequest
3y ago
> Only if you don't know C# or asp.net (or bootstrap). In which case: why would you be working for an organization which does? You've never taken a job working in a language you don't know yet? Anecdotally this is a common
88.
▲
by
badrequest
3y ago
It adheres to the Go 1 compatibility promise.
89.
▲
by
badrequest
3y ago
Go is type safe.
90.
▲
by
badrequest
3y ago
What common use-cases does it not support?
More ›