Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ameliaquining
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
31.
▲
by
ameliaquining
29d ago
My objection has always been that advocates either can't or don't care to explain how such a thing would actually work from the perspective of a unionized engineer.
32.
▲
by
ameliaquining
29d ago
Are the employees supposed to front the capital themselves?
33.
▲
by
ameliaquining
1mo ago
Yes, if the tech works but in a way that doesn't let the labs command premium prices for inference, then that also means a crash. But that's a fundamentals-based argument like Marcus's (despite being based in economics rather
34.
▲
by
ameliaquining
1mo ago
Pangram confirms: https://www.pangram.com/history/9ccdf6ed-5016-4325-b1ac-b3b0... I find it amusing that even the AI skeptic articles are written with AI these days.
35.
▲
by
ameliaquining
1mo ago
Marcus believes that the underlying technology doesn't work. If that's true, then of course the whole thing will crash as soon as everyone realizes this. This article is mostly making a different argument (though it contradicts it
36.
▲
by
ameliaquining
1mo ago
This just sounds like land value tax but worse.
37.
▲
by
ameliaquining
1mo ago
I consider it basically an accident of history that the first non-research languages to support ADTs were functional. (The first language to have them was actually CLU, which was imperative, but it was a research language.) There isn't
38.
▲
by
ameliaquining
1mo ago
The article anticipates and responds to this: https://sockpuppet.org/blog/2026/08/20/stop-making-tuis/#:~:...
39.
▲
by
ameliaquining
1mo ago
Non-cooperatively terminating a shared-memory thread is an inherently unsafe thing to do, and basically every runtime that has an API for it regards it as a design mistake. See, e.g., https://docs.oracle.com/javase/8&#x
40.
▲
by
ameliaquining
1mo ago
The Bun rewrite is a long-term investment; the idea is that you initially compromise on idiomatic Rust for the sake of being able to keep shipping, but then the codebase becomes more idiomatically Rust-like over time. It will probably take
41.
▲
by
ameliaquining
1mo ago
This post advocates rewriting incrementally instead of all at once. Just like Joel said back in 2000, and like everyone continues to always say to this day. Yet in practice, people don't actually do this; complete rewrites in Rust rema
42.
▲
by
ameliaquining
1mo ago
What exactly do you mean by "goroutine termination"?
43.
▲
by
ameliaquining
1mo ago
C++23 introduces std::expected, which is a simpler alternative to std::variant designed specifically for the result-or-error use case. You still don't get pattern matching, but Go-style tuples don't give you that either.
44.
▲
by
ameliaquining
1mo ago
Those seem quite different to me? Any kind of endeavor reliant on paid labor needs a source of funding and has to shut down if it can't find any; that's different from a situation where a business could have been sustainable by it
45.
▲
by
ameliaquining
1mo ago
This was caused by the company running out of money, not by investor pressure, and it resulted in the language becoming more open rather than less. So it doesn't seem like an example at all.
46.
▲
by
ameliaquining
1mo ago
I'm confused, C and C++ do require unsafe primitives? I think I must be misunderstanding your comment somehow.
47.
▲
by
ameliaquining
1mo ago
Has that ever happened to a programming language?
48.
▲
by
ameliaquining
1mo ago
Can you explain this in more detail? I'm not really familiar with Mojo but I can't think of obvious ways in which Rust's semantics (as opposed to syntax) are more functional than C++'s.
49.
▲
by
ameliaquining
1mo ago
Version differences in distributed systems (including Web apps) are a real pain! In many circumstances they're unavoidable, and we've developed various techniques to make them marginally easier, but if you can avoid the issue enti
50.
▲
by
ameliaquining
1mo ago
Stored procedures have the wrong versioning model. If they were version-locked to the application code, instead of to the database schema, they'd be less of a pain and people might be more willing to use them.
51.
▲
by
ameliaquining
1mo ago
Aren't there already lots of products that offer that, often more integrated with enterprises' existing systems than Keybase would be?
52.
▲
by
ameliaquining
1mo ago
I thought of "The Colour Out of Space".
53.
▲
by
ameliaquining
1mo ago
IIUC "FDIC insurance doesn't cascade into your customers' accounts" is not true in all cases, pass-through deposit insurance is a thing ( https://www.fdic.gov/financial-institution-employees-guide-d... ).
54.
▲
by
ameliaquining
1mo ago
Which blog posts?
55.
▲
by
ameliaquining
1mo ago
The claude.ai frontend contains defenses against automated access.
56.
▲
by
ameliaquining
1mo ago
no-panic relies on a linker hack because that's what's possible to do in stable Rust today; there's no API for adding an additional compiler pass that prohibits you from calling certain functions. Constants are well-defined i
57.
▲
by
ameliaquining
1mo ago
I wonder whether any of this is people confusing SOC 2 with SOX.
58.
▲
by
ameliaquining
1mo ago
Can't they? I thought this kind of thing was within Fable's capabilities.
59.
▲
by
ameliaquining
1mo ago
Google's security record at avoiding that kind of breach is just about the best in the industry, and their system that handles custody of password manager secrets is designed to withstand even a compromise of their production infrastru
60.
▲
by
ameliaquining
1mo ago
The ones ostensibly from 1981 have IDs (which you can map to URLs as, e.g., https://cvd.z.ai/findings/?id=ZAI-2026-0CJ0FC , substituting the last six characters): 0CJ0FC 0P0LJ6 3MLQD7 760CFQ AIT1IV APB04D BFR6N4 E64UY8
More ›