> This is the kind of thing that can’t be represented in any safe language because the indication of whether a value is a pointer isn’t even in application memory.
Welcome to the wonderful world of high performance low level optimization.
Storing type ids everywhere would double the size small fields and quadruple tiny ones like booleans. It’s also not necessary for most persisted data as you know the columns for a table.
Smaller representation makes reading and writing faster, and it also makes more data fit in memory.
Great. So you store a type id separately. But you make that typeid define how to safely read (maybe not interpret, but still read) the data without needing to cross-reference to anything else.
I’ve written plenty of high performance code. You can have safety and high performance at the same timetime.
It’s been a slow climb, but even looking at the last year, you’d have been better off holding tbills than NVDA. It’s pretty much where it was 1.5 years ago.
The market as a whole has done much better.
> Yet if you followed that advice you'd have missed out on a bunch of equity gains
If you never sold your NVDA you’d have round tripped with only a paltry dividend to show for it.
This is a cool idea. Though trying this out using the claude CLI is kind of funny because by default it's suggestion for the next prompt is the answer to the question.
> The letter continued to claim that Lothian would be "single-handedly eviscerating DisplayLink's competitive advantage in this crowded market by educating our competitors and other third parties as to how we implement our proprietary technology". He said that DisplayLink is not a member of OIN, and none of its technology is licensable through OIN or any other organization.
Isn’t the whole point of a patent to make the “how” patently obvious so others may learn from it?
Welcome to the wonderful world of high performance low level optimization.
Storing type ids everywhere would double the size small fields and quadruple tiny ones like booleans. It’s also not necessary for most persisted data as you know the columns for a table.
Smaller representation makes reading and writing faster, and it also makes more data fit in memory.
reply