Ah, sorry about the error! I guess it could use some optimisation. It will remain free for the users. I haven't thought about monetisation but for sure it won't be on the final user. Either ads or sponsored places by companies etc. Similar to TripAdvisor
I have a GitHub action that runs every night. It uses Youtube API to fetch all the new videos in a curated list of channels and playlists, then selects some of the new videos and creates the schedule.
What really stands out is the difference in design philosophy. In London, the gates are normally closed and only open if your Oyster card is valid. In Tokyo, the gates are open by default and only close if your card fails. You don’t have to wait for doors to open and close every time—it just keeps the flow moving and feels way faster.
Are we repeating history though? I've worked for a company that used Oracle plsql for everything (shall we return html snippets from the database as a reactive frontend, why not!, the whole business logic is in huge stored procedures anyway) and it was clearly an utter mess. Now, new tools may make this better, but every time I see too much business logic getting close to SQL I get suspicious.
Supabase is another example of doing everything with postgres. Sounds cool, but is it maintainable?
It's a joke. Or at least I've interpreted it as such. Still true that you always spend more time terraforming the little things compared to what you expected.