Remix first impressions
I've run through the basic Remix tutorial, and I wasn't wowed. Still, it's good to see a team trying to solve a new type of problem, so I'm going to keep an eye on it.
I'm not quite sure about the
action APIs for pages. As I understand it, the
ActionFunction exported from a route file is a generic handler for POST requests to that route—but it doesn't have the explicit clarity of e.g. SvelteKit, where the handlers are called
patch/etc and all live in an "endpoint" file that handles requests. I'm generally a fan of colocating code that all works together, but I like keeping templating separate from logic, and SvelteKit does a better job on that front. That's just personal preference, though.
Remix is officially on the tech tool carousel, so I'm keen to see where it goes in future. But I don't think I'm going to reach for it when scoping out new projects.
Strava's new(-ish) privacy controls allow you prevent other users from viewing your data. But what about the privacy controls to prevent the application itself from viewing your data?
Compute is moving back to the server, and that's a great thing! Here's why.