Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
nrds
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
nrds
8mo ago
Wait, that's not right, let me think through this more carefully...
32.
▲
by
nrds
8mo ago
If that's the author's point then the article needs a rewrite. I suspect that was _not_ the author's point and it's offered as a good faith but misplaced post-hoc justification.
33.
▲
by
nrds
8mo ago
Is it even worth pointing out that the author misunderstands how UB works in Rust, given that at this point such a misunderstanding has to be willful than otherwise? There is _no_ UB in the safe subset of Rust, and in mixed safe-unsafe rust
34.
▲
by
nrds
8mo ago
> Also, we've realized the scientific reality that traveling faster than light is likely impossible I'm confused at what speculative fiction exists from before the 1910s (or thereabouts) which involves FTL? I've no doubt t
35.
▲
by
nrds
8mo ago
And if the automatic payment doesn't go through, well, then there's nothing to report on so no email generated.
36.
▲
by
nrds
9mo ago
What else could they do? If they don't vibecode Claude Code it is a bad look.
37.
▲
by
nrds
9mo ago
I understand there's an increased error rate, that's how I concluded there is an attempted DOS. But it appears not to be working completely, and so a post claiming X is "down" does appear to be pre-coordinated to reflect
38.
▲
by
nrds
9mo ago
There are no types whose fields "live on the heap", nor are there types whose fields "live on the stack"; these are simply not properties of types. Values always live exactly where you put them and you can put values any
39.
▲
by
nrds
10mo ago
The federal circuit COA has never met a patent they don't like. That's all that matters. Statute text is irrelevant. The federal circuit openly ignores SCOTUS precedent about patents (e.g. Alice).
40.
▲
by
nrds
10mo ago
That's the traditional answer parroted in the Wireguard documentation but a few hours' serious thought and design is enough to reveal the fatal flaw: any encapsulating protocol will have to reinvent and duplicatively implement all
41.
▲
by
nrds
10mo ago
It takes a lot of uncached tokens to let it learn about your project again.
42.
▲
by
nrds
10mo ago
> Use Opus 4.5. This drives up price faster than quality though. Also increases latency.
43.
▲
by
nrds
10mo ago
> beliefs and assumptions Unfortunately during coding I have found many LLMs like to encode their beliefs and assumptions into comments; and even when they don't, they're unavoidably feeding them into the code. Then future sess
44.
▲
by
nrds
11mo ago
As a first guess, they're trained on lots of social media and Q&A content. The former has lots of complaints about "look how complex rust is!" while the latter has lots of "help I've written very complex rust&qu
45.
▲
by
nrds
11mo ago
IME with this sort of thread there is a huge correlation between praising OOP and believing that encapsulation is an identifying feature of OOP. Also polymorphism to a much lesser extent, but the other two almost none. It is very difficult
46.
▲
by
nrds
11mo ago
Maybe rust should put a function in the core library which does this! Send a PR!
47.
▲
by
nrds
11mo ago
I only do it if no one is behind the flasher; I thought was obvious. And I have OEM headlights.
48.
▲
by
nrds
11mo ago
> BLUE MEANS BLINDING ONLY IF YOU'RE LIVING IN THE '90S! THE REST OF US HAVE MATRIX HEADLIGHTS! ALSO TURN OFF YOUR CRUISE CONTROL FOR COOL!
49.
▲
by
nrds
11mo ago
When I get incorrectly flashed I force my high beams on and keep them on, FYI. Don't do it.
50.
▲
by
nrds
11mo ago
> If this blue indicator is on, you're blinding everyone Your information is outdated. My Tesla with matrix headlights keeps the high-beam indicator on but oncoming drivers are not blinded.
51.
▲
by
nrds
11mo ago
TL;DR. Zig now has an effect system with multiple handlers for alloc and io effects. But the designer doesn't know anything about effect systems and it's not algebraic, probably. Will be interesting to see how this develops.
52.
▲
by
nrds
1y ago
I have long felt the killer feature of QUIC is its ability to encapsulate _both_ reliable in-order delivery and unreliable datagram delivery in the same opaque-to-middleboxes container. Whereas HTTP becoming the everything-protocol is debat
53.
▲
by
nrds
1y ago
What works for Kmett most often does not work for mere mortals. As for your first point, I think it's self-defeating: You claim "you don't have to worry about libraries providing an interface to your chosen incremental strea
54.
▲
by
nrds
1y ago
I do not claim they are the only or even best tool :)
55.
▲
by
nrds
1y ago
Only countably many of those subsets can be distinguished from other ones. So "anything I could ever imagine caring about" is surely still a countable set. I think the argument you are trying to make rests on a pretty serious fall
56.
▲
by
nrds
1y ago
I think it's worth specifically calling out that the right way to set environment variables is in execve() only, as communication across an exec() is the precise niche for which they are the right tool.
57.
▲
by
nrds
1y ago
> minds struggle I never believed this explanation for SC as provided by Culture-aligned unreliable narrators. It seems far more likely that it's an outlet for people who desire to have control over others, a supermajority of the We
58.
▲
by
nrds
1y ago
And that means they know what lane they need to be in 100, 200, 500 ft down the road. Tesla has map data but it's so poor that they can't get the lanes right.
59.
▲
by
nrds
1y ago
Waymos stop in the middle of the street several times a day, behavior I've never seen or even heard of from FSD. And I'm not sure what it has to do with lane selection. FSD goes around stopped vehicles without any problem too.
60.
▲
by
nrds
1y ago
As you observed, lane selection is basically the one thing that FSD is completely incapable of. But other things it does well. It's important to note this is completely incompatible with the narrative spun by Tesla haters, that it all
More ›