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
I'm impressed a single individual got to 600K MRR by himself. Only a few people can say that they've done that. Who knows when shopify would've taken their checkout experience seriously were it not for this guy. you can have interesting experience, build temporary things, be proud of it, and move on to the next thing.
I think gas app type growth was cool, but I cannot imagine being on that hamster wheel long term. the goal would to have an exit at the peak and not be like snapchat. that said, I do admire blue chip sites that go viral simply b/c it feeds a global demand very simply (ie., sudoku.com); if wordle didn't sell, they could've easily surpassed their purchase price in a few months.
i haven’t, was going to start trying to make some attempts this year, static sites like istheshipstillstuck and howmuchtoiletpaper. also i don’t know how to answer the monetization question for new sites that pick up traffic quickly
You can put all your writes in a queue to be processed by a finite set of writers. I think most CRUD applications can afford the delay and if not you can pair it with a write through cache.
i think both fly.io and litestream were projects that spoke sweet words to the average developer wanting to build features without the infra headache, and what made sqlite so appealing was its simplicity. litestream kept that simplicity too. but i don't think the avg developer wants to spin up their own LiteFS. At a glance at the repo, i have no idea how to deploy this thing. It would have served fly and litestream users better to have kept replication within litestream.
just as no one using postgres on RDS will ever leave RDS not b/c RDS is so much better than its competitors but because the hurdle is too great and the migration so risky. right now, fly is the only one who lessens the burden to use LiteFS and as long as they're the only one, the average developer is essentially locked in.
i’ve been thinking of doing something similar but for anime and with semantic search (ie., “rudeous getting punched”) but i have concerns about DMCA notices. I also know that search engines have a different set of rules for copyright liability but i couldn’t make sense of them since IANAL.
I might just make it for myself and call it a day.