Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
haberman
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
haberman
8mo ago
If I'm criticizing the linked post, then I'm also criticizing myself, because I could easily imagine having written it.
32.
▲
by
haberman
8mo ago
Lately I'm seeing more and more value in writing down expectations explicitly, especially when people's implicit assumptions about those expectations diverge. The linked gist seems to mostly be describing a misalignment between th
33.
▲
by
haberman
8mo ago
More concretely, I think the magic lies in these two properties: 1. Conservation of mass: the amount of C code you put in will be pretty close to the amount of machine code you get out. Aside from the preprocessor, which is very obviously
34.
▲
by
haberman
9mo ago
The rate of college attendance has increased dramatically in the last 250 years, and especially in the last 75. In 1789 there were 1,000 enrolled college students total, in a country of 2.8M. In 2025, it is 19M students in a country of 340
35.
▲
by
haberman
10mo ago
I’ll repeat what I said at that time: one of the benefits of the new design is that it’s less vulnerable to the whims of the optimizer: https://news.ycombinator.com/item?id=43322451 If getting the optimal code is relying on
36.
▲
by
haberman
10mo ago
A long time ago I read that CadQuery has a fundamentally more powerful geometry kernel than OpenSCAD, so I dropped any attempt to try OpenSCAD. Years later, I never actually got the hang of CadQuery, and I'm wondering if it was a mista
37.
▲
by
haberman
10mo ago
> Hotspot is the choice for high performance programs. Approaching its performance even with C++ requires a dedicated team of experts. It's very surprising to hear you say this, as it's so contrary to my experience. From the sm
38.
▲
by
haberman
1y ago
I agree, but in my experience arena allocation in Rust leaves something to be desired. I wrote something about this here: https://blog.reverberate.org/2021/12/19/arenas-and-rust.html I was previously excited
39.
▲
by
haberman
1y ago
Good to know! Thanks for confirming. Yes, I would guess that the tail call interpreter explains part of the difference between 3.13 and 3.14. Previously the overall improvement to the interpreter has been measured at 1-5%, or even 10-15% d
40.
▲
by
haberman
1y ago
Do any of these tests measure the new experimental tail call interpreter ( https://docs.python.org/3.14/using/configure.html#cmdoption-... )? I couldn't find any note of it, so I would assume not. It would be i
41.
▲
by
haberman
1y ago
The article says exactly this in bold at the bottom: > If you can break up a task into many parts, each of which is highly local, then memory access in each part will be O(1). GPUs are already often very good at getting precisely these k
42.
▲
by
haberman
1y ago
LuaJIT bucks the trend of slow-warmup JITs. It is extremely quick to compile and load, and its interpreter is very fast -- faster than the JIT-compiled code from LuaJIT v1 IIRC, and certainly faster than the interpreter of Lua. It wasn
43.
▲
by
haberman
1y ago
This was an interesting article, but it made me even more interested in the author's larger take on R as a language: > In the years since, my discomfort has given away to fascination. I’ve come to respect R’s bold choices, its clari
44.
▲
by
haberman
1y ago
These features look compelling. When will they all be available in mainstream browsers?
45.
▲
by
haberman
1y ago
I advocated for PrefixVarint (which seems equivalent to vint64 ) for WebAssembly, but it was decided against, in favor of LEB128: https://github.com/WebAssembly/design/issues/601 The recent CREL format for EL
46.
▲
by
haberman
1y ago
For me, that was a moment when I realized that the received wisdom about military things can be just completely wrong. I had considered myself to be reasonably informed about the F-35, and how "everyone knows" it's a boondogg
47.
▲
by
haberman
1y ago
Landed on target in the Indian Ocean! Engines relit successfully and it touched down vertically (and then promptly exploded, which I guess was the plan :)
48.
▲
by
haberman
1y ago
Ha, I don't know much about Dolby Atmos and spacial placement. But from prior experience I'm somewhat skeptical about what this kind of clever DSP can do for choral music. For example, when I learned about convolution reverb, and
49.
▲
by
haberman
1y ago
I completely agree that one-per-part singing really brings out the beauty in 16th century choral music. I sing in a choir that specializes in music of this period, and while our live performances usually use two singers per part to fill a
50.
▲
by
haberman
1y ago
As someone who had perfect vision until 40 but now must wear reading glasses, I am super intrigued to hear about lens exchange! When I heard that LASIK is not a solution to farsightedness, I specifically asked my eye doctor if there are oth
51.
▲
by
haberman
1y ago
I love the concept -- I've often wished that lean languages like Lua had more support for static typing, especially given the potential performance benefits. I also love the focus on performance. I'm curious if you've consid
52.
▲
by
haberman
1y ago
Shameless plug, I helped produce and sang on this disc of Pärt by tbe Byrd Ensemble of Seattle: https://www.youtube.com/watch?v=xc96YWX4qAE&list=PLbeKTzt34V... Excerpts of it were later featured in a French movie called
53.
▲
by
haberman
1y ago
I think you can alias the input data using Cord fields? As long as the input is Cord.
54.
▲
by
haberman
1y ago
This kind of "expected next field" optimization has a long history in protobuf, but results are mixed. The generated code in C++ used to check for the expected next field before falling back to the switch() (example here: https:&
55.
▲
by
haberman
1y ago
I think I can shed some light on this, as the creator and lead of upb. Calling a Protobuf Parser an "interpreter VM" is a little bit of rhetorical flourish. It comes from the observation that there are some deep structural simila
56.
▲
by
haberman
1y ago
I wrote a portable abstraction for this that works across Linux, MacOS, and Windows: https://github.com/protocolbuffers/protobuf/blob/4917ec250d3... I call them "linker arrays". They are great when
57.
▲
by
haberman
1y ago
The paper mentions that the authors implemented tree borrows in Miri. Is this change likely to be adopted by Miri as the default model going forward?
58.
▲
by
haberman
1y ago
I would be satisfied if the language supported this use case by offering a “void my warranty” annotation that let a given source file access the privates of a given import. Companies with monorepos could easily just ban the annotation. OSS
59.
▲
by
haberman
1y ago
This is company code in a monorepo. If a change breaks users, it will simply be rolled back. Everyone is brainstorming ways to work around Zig's lack of "private". But nobody has a good answer for why Zig can't just ad
60.
▲
by
haberman
1y ago
Most data structures have invariants that must hold for the data structure to behave correctly. If users can directly read and write members, there's no way for the public APIs to guarantee that they will uphold their documented API b
More ›