Spent some time tonight reviewing the #RemixRun #JavaScript framework mad a lot of it really seems to mesh with my preferences. The one thing I'm strick by though is their apparent aversion to pre-rendering on the server. If I have some template that I know won't change why not just prerender as much as possible instead of combining it each time? It's low hanging but seems like an obvious win they're missing to me.
Been playing around with #RemixRun for a toy project. So far I'm pretty impressed! It does a pretty good job of walking the line between not being too magical and being understandable. And setting things up to ship a no-javascript frontend is pretty straight forward.

Get it while its hot #remixrun v1.14 is out with new dev server and HMR and new HDR (Hot Data Revalidation. https://github.com/remix-run/remix/releases/tag/remix%401.14.0 #react #webdev #javascript
#JavaScript #WebDev #react #remixrun
I was playing around with a #LeverageJS based system that works like #RemixRun a few months ago. I'm realizing now that the most challenging thing that Remix handles effortlessly is state. The way it handles actions, loaders, and future renders is really intuitive but technologically challenging.
I'm consistently impressed with how easy things are in #RemixRun while being so close to web standards as possible. But what gets me most is that Remix encapsulates the most important logic: state management. Simplifying the connection between client and server to let the server be the source of truth is so freeing. I'd be doing *at least* double the work with any other framework. Not to mention the consistency of state & render updates it manages for you.
2022 has seen a welcome shift of the needle towards #webframeworks that work with the core principles of the web rather than fight against them.
My brief thoughts on a year of using #remixrun and exploring @enhance_dev with more purpose.
To me, file based routing is a leaky abstraction for REST. Because files are files and they don't know what you mean. #SvelteKit, #Remixrun, #SolidJS through solid-start, #NextJS all have this problem.
There are not many other options than REST so don't let that above qualifier distract you.
I have some ideas but they are just ideas.
#sveltekit #remixrun #solidjs #NextJS
Another blog post!
#remixrun #reactjs #javascript #webdev
This one dives into Remix's optimistic UI system and leverages some less well known features to solve a problem I ran into.
#webdev #javascript #reactjs #remixrun
New blog post
My first blog post in... a while. It's about #remixrun, and I'll be adding more posts soon with more thoughts and some helpful tips I've discovered as I've delved into Remix.
#reactjs #javascript #webdev #remix #remixrun
@keb I'm not sure, haven't tried it π€
#remixrun feels like coding back before SPAs roamed the earth when you used forms to control your flow. It is SSR, and the state is managed beautifully. In most cases, things just kind of work how you want them to without you having to think much about it. It's developed by the team behind react-router-dom and built with react-router-dom v6 as a major feature. Simple and elegant.
Anyone else here playing with Remix.run #remixrun #remix #reactjs #javascript?
I've been using it pretty much since it went open source and I'm very happy with it. I'd love to hear some other people's opinions (the good, the bad, the ugly).
#javascript #reactjs #remix #remixrun
@retrovolcano #ReactJS has been my bread and butter for 5 or 6 years now. I've been using #remixrun (Remix.run) for a few months and loving it. They're the team behind react router as well. Remix is relatively new so it's got some rough edges, but it's very fun.
@nickr49 @jengilbert
π
#Javascript #typescript #nodejs #reactjs #remixrun #nestjs you know... I like js π
I'd love to find more people.
#nestjs #remixrun #reactjs #nodejs #typescript #javascript