is there an decentralized org to ensure that all of the js css we use today remain backward compatible decades from now? or are we just at the whim of these browser vendors?
The main draw for me with elysia was that it maintains bun's perf benefits unlike express. When I got into the weeds of the documentation, their abstractions could use a lot of polish. The lifecycle of a request is not that clear imo and all the hooks you put into it look like hacks rather than integrations.
i also do the sit down a calculate exercise. i always end up down a rabbit hole of how to make a viral site as cheaply as possible. always ends up in the same place: redis, sqlite, SSE, on suspended fly machines, and a CDN.
i forgot what year but the year the spurs won the championship against lebron would be unusual today. tons of passing not necessarily for the 3 but to just dislodge the defense enough for a guaranteed bucket
i don’t think there’s any other input type you can apply the one million schtick to except color. i was thinking of squared shaped browser native color pickers on a 1000x1000 or 10k x 100 non responsive grid. but after seeing the infra and bandwidth costs from the guy who did checkboxes i don’t think my stack of choice could keep up (RoR) i was really looking forward to utilizing fly’s pause/resume feature