3 ms·

I've just started playing with Remix since it seems to be the recommended route for Shopify app development. I must say I'm not entirely blown away by it. It's

I've just started playing with Remix since it seems to be the recommended route for Shopify app development. I must say I'm not entirely blown away by it. It's unique feature (frontend/backend coupling) kind of feels like it's just a re-engagement with the traditional web app. Or even just akin to a mono repo for a modern frontend/backend. Beyond that, it's main let down (which is in no way unique to it) is not having a straight forward application entry point that allows you to wire things up as you see fit (composition root). Instead we get a request handler that we hook into another server technology that in turn makes their controller equivalents work like magic. My struggle with it, as of this afternoon, was to figure out how to bundle raw SQL files in the build until it became apparent that you have to unbox all the Vite functionality and do it that way (which seems to have some depth) or literally have a parallel step outside the build for copying the files into the build dir. Not the greatest experience for what is a pretty basic step (embedding resource files in the build output). Very much feels like a project that is just a small twist on what already exists in the ecosystem and will fall into the growing black hole of JS web frameworks. Sorry to be glum :/

jackbravo 3y ago
why do you want to bundle raw SQL files?
- aswerty 3y ago
  To execute them against a database during runtime. I'm a little amused as to the question, I'm certainly not using them as tea coasters. Edit: and maybe to add more context (and a bit less glib). My approach to interacting with an rdbms is to put each query in a separate SQL file (so no dynamic SQL and no query builders - ORM or otherwise) and execute them with a simple db client. In this case pg-promise. I've landed on this approach after many years of using various approaches and seeing how those approaches take affect on a team/product over time. Though of course ORM vs raw SQL is an argument as old as time (or as old as ORMs at least).
0xblinq 3y ago
While I like and use Remix I do agree with your prediction about its future. Sadly.

jackbravo 3y ago

why do you want to bundle raw SQL files?

aswerty 3y ago
To execute them against a database during runtime. I'm a little amused as to the question, I'm certainly not using them as tea coasters. Edit: and maybe to add more context (and a bit less glib). My approach to interacting with an rdbms is to put each query in a separate SQL file (so no dynamic SQL and no query builders - ORM or otherwise) and execute them with a simple db client. In this case pg-promise. I've landed on this approach after many years of using various approaches and seeing how those approaches take affect on a team/product over time. Though of course ORM vs raw SQL is an argument as old as time (or as old as ORMs at least).

0xblinq 3y ago

While I like and use Remix I do agree with your prediction about its future. Sadly.