pavpanchekha

9 ms·

31.
by pavpanchekha 10mo ago
Author here. This specific quirk of CSS is minor, and probably if CSS didn't have this quirk it'd be fine. But I'd guess that you've at least once in your life been on your phone and been browsing a website which used a
32.
by pavpanchekha 10mo ago
Fixed
33.
by pavpanchekha 10mo ago
Author here. The problem isn't the technical challenge of writing a constraint solver. It's making sure that the resulting layout looks good, despite contradictory guidance from the designer. Yes, a constraint solver can figure ou
34.
Should CSS be constraints?(pavpanchekha.com)
25 points by pavpanchekha 11mo ago|44 comments
35.
by pavpanchekha 1y ago
Your argument can't be so strong as to imply that IPv4 should actually have used 24-bit addresses, though.
36.
by pavpanchekha 1y ago
Great reply, much appreciated. I searched a bit for a number like ~70B and didn't find one. Perhaps 36 bits wouldn't have actually worked. I do think we'd have wasted more Class As, but that's where the "minor marke
37.
by pavpanchekha 1y ago
It's not an argument for longer roads or can kicking? The thesis is stated at the top: with 9 bit bytes we'd avoid a couple of bad numerological coincidence (like that the number of Chinese characters is vague but plausibly around
38.
by pavpanchekha 1y ago
Author here. I agree that this would have a similar effect; we'd probably still end up with 36-bit or 48-bit IP addresses (though 30-bit would have been possible and bad). We'd probably end up with a transition from 24-bit to 48-b
39.
by pavpanchekha 1y ago
Author here, copied from another comment above. Actually I doubt we'd have picked 27-bit addresses. That's about 134M addresses; that's less than the US population (it's about the number of households today?) and Europe
40.
by pavpanchekha 1y ago
Author here. The argument was that by numerological coincidence, a couple of very important numbers (world population, written characters, seconds in an epoch, and plausible process memory usage) just happen to lie right near 2^16 / 2^
41.
by pavpanchekha 1y ago
Author here. My argument in the OP was that we maybe would never need to transition. With 36-bit addresses we'd probably get all the people and devices to fit. While there would still be early misallocation (hell, Ford and Mercedes s
42.
by pavpanchekha 1y ago
Author here. The point is that with 9-bit bytes we'd have designed IPv4 to have 36-bit addresses from the beginning. There wouldn't have been a transition.
43.
by pavpanchekha 1y ago
Author here. I kind of doubt it. Copied from a comment earlier: I doubt we'd have picked 27-bit addresses. That's about 134M addresses; that's less than the US population (it's about the number of households today?) and
44.
by pavpanchekha 1y ago
Author here. Really great comment; I've linked it from the OP. (Could do without the insults!) Most of the changes you point out sound... good? Maybe having fewer arbitrary limits would have sapped a few historically significant coders
45.
by pavpanchekha 1y ago
Author here. Actually I doubt we'd have picked 27-bit addresses. That's about 134M addresses; that's less than the US population (it's about the number of households today?) and Europe was also relevant when IPv4 was bei
46.
by pavpanchekha 1y ago
Author here. It's true that you'd need one more bit to represent a bit position in a word, like for shifts, but we're already vastly over-provisioned; even in 64-bit registers we're only using six of eight bits. (Plus, i
47.
by pavpanchekha 1y ago
Thanks
48.
by pavpanchekha 1y ago
Author here, in fact all the words you read I wrote, LLMs are not very good at writing.
49.
by pavpanchekha 1y ago
The point of this work is to pin down the exact boundaries of undefined behavior. Certainly the code above is accepted by the Rust compiler , but it also breaks rules . What rules? In essence, we know that: - Anything accepted by the borr
50.
by pavpanchekha 1y ago
The minimization is regularized, meaning you add a penalty term for large coefficients. The coefficients will be different for the two bases, meaning the regularization will work differently.
51.
by pavpanchekha 2y ago
Fabs recycle the water so it's not a big deal. A lot of water by industrial standards is not a lot of water by state standards, even if we're talking about a pretty desert-y state.
52.
by pavpanchekha 2y ago
To summarize: the post is phrased in terms of an existing controversy about whether Gorbachev was "powerless" in the face of the bureaucracy (and how much he feared a coup), but concludes he wasn't. Instead, the author thinks
53.
by pavpanchekha 2y ago
I think Rapid Dragon, plus recent talk of using the B21 for air combat/to replace NGAD are pointing in this direction: use large, numerous, and cavernous planes for Pacific firepower.
54.
by pavpanchekha 2y ago
Realistically, the copyrighted works that are most valuable to training machine learning models, at least if we go by The Pile as typical of training data [1] is: - Web pages; hard to argue that royalties are due since these are publicly av
55.
Does O3 beat a specalized numeric compiler?(pavpanchekha.com)
2 points by pavpanchekha 2y ago|0 comments
56.
by pavpanchekha 2y ago
I loved this clever, weird, awesome paper, so a short summary. In many dynamic languages some values are stored on the heap ("boxed") and represented as a pointer, while others are represented as an immediate value ("unboxed&
57.
by pavpanchekha 2y ago
Author here, and I also teach web dev, including CSS, at the University of Utah (including this semester). Newer parts of CSS, like flex-box layout are both simple and powerful. Just use those! I think it's important to start thinking
58.
by pavpanchekha 2y ago
Ah, weird! We can ask our publisher. This HN post was a surprise (Chis & I didn’t put it up) so we weren’t prepared.
59.
by pavpanchekha 2y ago
Thanks!
60.
by pavpanchekha 2y ago
The book isn’t out yet, so no promo code, but the whole thing is free online.

More ›