I think the late Robert Dewar once quipped that modern jet fighters aren't safety-critical applications because the aircraft disintegrates immediately if the computer system fails.
> The more messages you need to process overall, the more attractive a solution centered around monotonically increasing sequences becomes, as it allows for space-efficient duplicate detection and exclusion, no matter how many messages you have.
It should be the opposite: with more messages you want to scale with independent consumers, and a monotonic counter is a disaster for that.
You also don’t need to worry about dropping old messages if you implement your processing to respect the commutative property.
You only need monotonicity per producer here, and even with independent producer and consumer scaling you can make tracking that tractable as long as you can avoid every consumer needing to know about every producer while also having a truly huge cardinality of producers.
hash your thing you want to do and see if you did it recently or in order by hashing each thing you wanted to do in order to get a new hash of all the things you did in the order you did it in one value.
I remember reading somewhere that these curves were based on the curves that naturally occur on smooth pebbles due to the abrasion of water, but can’t find a link now (searching “apple” and “pebble” only gives me results about the smartwatch)
> a squircle doesn’t look like a square with surgery performed on it; it registers as an entity in its own right, like the shape of a smooth pebble in a riverbed, a unified and elemental whole.
But I seem to remember reading about Jobs or maybe Ive stating smooth pebbles as a source of inspiration for how objects should feel in the hand – I believe it was in the context of the first iPhone shape.
> That should make arr[1] possible but arr[1] = 9 impossible.
I believe you want `=`, `push`, etc. to return a new object rather than just disallow it. Then you can make it efficient by using functional data structures.
At TypeScript-level, I think simply disallowing them makes much more sense. You can already replace .push with .concat, .sort with .toSorted, etc. to get the non-mutating behavior so why complicate things.
You might want that, I might too. But it’s outside the constraints set by the post/author. They want to establish immutable semantics with unmodified TypeScript, which doesn’t have any effect on the semantics of assignment or built in prototypes.
Well said. (I too want that.) I found my first reaction to `MutableArray` was "why not make it a persistent array‽"
Then took a moment to tame my disappointment and realized that the author only wants immutability checking by the typescript compiler (delineated mutation) not to change the design of their programs. A fine choice in itself.
To be fair, ads on a map aren't the same as Windows 11 start menu ads – the former are useful and contextual.
I feel the story being told would be more equivalent to what Microsoft is doing rather than Google.
That said, advertising is like a virus, and every company and product is eventually infected by it. It's too tempting to not monetize your customer's eyeballs once you have enough of them.
I actually consider the windows start menu ads less objectionable. At least you can turn them off (for now). There is no way to disable ads embedded in the maps app. And it’s only useful and contextual if you’re using the map to look for somewhere to spend money. I rarely do this. I’m using it to check traffic, get directions to somewhere, or exploring out of geographical curiosity. In all of these use cases, ads are an unwanted distraction.
This article is a good example of how, sometimes, starting from scratch is a blessing, since you can adopt the best tech right away instead of fighting market inertia and monopolies trying to keep a status quo - as a counter example, see Japan being stuck w/ fax past the internet advent.
