Recent submissions

Comment · 3 months ago
A replicated SQLite is very cool! One question I would have is why expose that as the storage instead of the platform providing a managed storage API? I guess I might be concerned about replication lag and complexity for consumers with the replicated SQLite.

Is it to have more sympathy for LLMs? More 1:1 with a local dev environment?

Comment · 2 years ago
I think that trust needs to be 'pushed deeper' than that so to speak. While this would be an improvement, what happens if there is a malicious actor at Github? This may be unlikely, but would be even harder to detect since so much of the pipeline would be proprietary.

Ideally, we would have a mechanism to verify that a given build _matches_ the source for a release. Then it wouldn't matter where it was built, we would be able to independently verify nothing funky happened.

Comment · 2 years ago
Comment · 2 years ago
I love dan luu's blog posts. Great examples of principled thinking. Much of their writing on (computer) performance has pushed my own thinking and expectations.
Comment · 2 years ago
Not just delivery, but also security. Browsers offer a level of isolation and safety that you generally don't get with native desktop apps. Things like iOS do bridge the gap a bit more though
Comment · 2 years ago
Comment · 3 years ago
Comment · 3 years ago
I understand what you are saying here in terms of the difference between using wall-clock or causal ordering to determine who 'wins' for LWW. However, both of these strategies seem convergent to me? In any case, all clients will agree on whose changes win.

1. With wall-clock decided by clients, A + B changes will win since C's wall-time is earlier (yes, C could lie, but still would converge).

2. With wall-clock decided by server C will win and everyone will agree.

3. With causal ordering, everyone will agree that A + B won.

2 is not a CRDT since it requires a central server, but I think 1 would still count? Or stated another way: I'm not sure the _convergence_ is what determines if these strategies are CRDTs or not, but rather whether or not this decision making is _distributed_ or not.

Comment · 3 years ago
> This is the same guy who tried to make "effective altruism" part of his image. That was a pretty strong signal that the outcome we all witnessed was highly likely.

Why do you think that was such a strong signal?

Comment · 3 years ago
FWIW I'm not sure analogies between intellectual property and actual property really work, since they are pretty fundamentally different if you compare the specifics.
Comment · 3 years ago
Even better, Jamie Lee Curtis was in both of those movies.
Comment · 3 years ago
I actually talked to the drifting in space team about our experience implementing multiplayer. Really cool to see their findings!

Our team ended up having a similar take away, we wrote a blog post detailing our approach and experience here: https://hex.tech/blog/a-pragmatic-approach-to-live-collabora...

For the most part is been surprisingly solid! I was very much expecting to need to completely rewrite it by now, but its met most of our present needs.

The only real shortcoming is not being able to support line specific commenting. While we _could_ support it, any minor update to the text would result in the comment being marked 'stale' with a high false positive rate. I've considered adopting CRDT/OT just for the text editing portion to solve this.

Comment · 4 years ago
I really like how well this bookends with https://hex.tech/blog/long-live-code!

(Disclaimer, I work at Hex but wish more tools would embrace ejecting to code in the same way)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton