HN user

neftaly

133 karma

https://neftaly.com

Posts0
Comments65
View on HN
No posts found.

For a modern fighter jet, it's a lot. It's planned to remain in service till 2070.

One of the most important strategic innovations of the F-35 has been economies of scale.

Fair enough, I didn't investigate them very far, as IMO only pubsub maps to the "webrtc signalling for misers" problem neatly enough to make it worth adopting (probably -- they haven't actually said how much it will cost).

From my understanding, yes. I asked about the billing model on the CF Discord 6-12? months ago. I don't know how much it costs per message, or if there is a catch wrt cheap wrtc signalling, however my understanding is that you won't be paying per user or per hour etc. To be clear this is through their MQTT 5.0 service only.

R2 was used because it was the only database-like service CF offered at the time.

IIRC the P2pcf client polls the worker for new peers. Pubsub would let you use an ongoing websockets connection, plus all the channel management logic is built-in. The game-changer is that they've said they'll charge per-message as opposed to per-connection-second, unlike everyone else!

I evaluated using this in prod, but came to the conclusion that R2 was a bit shaky as a database. CF has since come out with D1 SQL, DO (beware vendor lock-in), queues, and my favorite, MQTT pub-sub, which would be better options. They've also been teasing some vastly improved options for STUN/TURN; I wouldn't be surprised if more turnkey signalling popped up.

The issue was that a specific library would be pinned at a specific version for the rest of the history of the web. As good as SQLite is, I hope to hell we're not still stuck using it to handle mining operations in the oort cloud in 200 years.

I have been writing a video game using automerge-repo for networking & save files. I researched Yjs and Automerge and felt that Yjs is better suited to an ongoing session like a conference call, whereas automerge is better suited for network partitions etc. This fit my use-case best. My opinion might be out-of-date as this area is moving quickly, and there are quite a few options out there now.

If this article is true (i.e. the quoted bullet points were actually said by Kwon) I would feel a bit more optimistic. I haven't checked the veracity at all.

The metaculus wager says replication within 15 months. Point #2 #3 #5 & #8(!) is that this stuff is really really hard to make. Point #6 is pretty noncommittal about how long till the recipe is published (in the context of 20 years of work).

I've been tooling around with "Tuple Database", which claims to be FoundationDB for the frontend (by the original dev of Notion).

https://github.com/ccorcos/tuple-database/

I have found it conceptually similar to Relic or Datascript, but with strong preformance guarantees - something Relic considers a potential issue. It also solves the problem of using reactive queries to trigger things like popups and fullscreen requests, which must be run in the same event loop as user input.

https://github.com/wotbrew/relic https://github.com/tonsky/datascript

Having a full (fast!) database as my React state manager gives me LAMP nostalgia :)

We've been in a 20-year old class-C for a year, it requires regular handyman maintenance (we bounce down a lot of dirt roads) but it has been very mechanically reliable. Upgrading to 200ah of LiFePO4, adding a 140L water tank on the hitch, and plumbing in an external hose for beach showers really improved our quality-of-life. The only thing that will kill them is roof leaks, make sure you replace the rubber roof every 5 years or so.

Give it a few months before you start accessorising, we've kept it to a couple of ebikes, camp chairs+table, and a paddleboard. Don't bother with Starlink unless you need to be online 24/7, and if you do get it, consider it only as a supplimentary to a good rugged dual-sim 4G modem.

Back home (NZ) we were in a almost-new Sprinter, which was great on fuel, but less fun once you wanted to go off-road or abuse it in any way. Our 2WD Ford goes places people don't dare bring their shiny new 4x4s.

I wouldn't go over 22' long, especially in Mexico and the fun parts of Canada, otherwise you'll just be touring RV parks with all the other people towing F150s and jetskis and bouncy castles.