If someone commits a wrong lockfile they are fired where I work at lol (exaggerating, but only slightly)

Fyi, building a collaborative editor right now and it's still hard to do outside of Node

Still better time spend than doing leetcode.

It's my go-to argument against leetcode style interviews.

I would rather ask a candidate to spend 30 mins and do research together on collaborative editing, or visualizing distances used in pgvector or similar vector database.

Imagine how far the whole colabarative editing space moved forward if 1% of leetcode grinding were rerouted

Is there a way to use it without decorators?

Just create a uuid and store it in a cookie or local storage. You're fine, you're allowed to do this. As long as you don't relate it anywhere to some other information and treat it as "some user" you're on the safe side.

It's only ever an issue when you generate the uuid based on device parameters or use the same uuid across multiple sites (that don't belong to the same entity).

this would require a cookie banner.

How's the performance with Longhorn with databases?

Too bad that uWebsockets was used for Node because a lot of higher level libraries are built on top of https://www.npmjs.com/package/ws

I was able to make a uWebsockets adapter for NestJS pretty easily. It's a bit sensitive of a library to integrate though, a single write when the connection is gone and you get a segfault, which means a lot of checking before writing if you've yielded since you last checked. This was a few years ago, perhaps they fixed that.

Just use Postgres. Sqlite migrations are a PITA

Your code sections are almost unscrollable on mobile

(author here) hmm it seems to work on my device. what happens when you try to scroll?

Just sucks if you are a service provider and need some kind of SLA to be taken seriously (see the flak Fly.io / Resend are getting) since it's so difficult to find good resources on solid setups. Think for every guide for bare metal there are a few hundred for cloud and both assume a handful of users

Maybe you can scratch the experiment and downscale it? Seems like you are very very very far away from needing something as beefy as that. Unless you got it for very cheap, I'd feel bad having so much money in idle hardware