4 ms·
Interesting take. I had the experience with Remix and drew the comparison to Tailwind.css [1]. I get the sense that Remix's move away from REST + SPA will be po
by jackconsidine 5y ago
Interesting take. I had the experience with Remix and drew the comparison to Tailwind.css [1]. I get the sense that Remix's move away from REST + SPA will be polarizing because of the magnitude of the shift, but tremendously productive for many developers who embrace it.
[1] https://koptional.com/article/remix-fullstack-paradigm-pros-and-cons.html#a-short-intro https://koptional.com/article/remix-fullstack-paradigm-pros-...
- fastball 5y agoIs Remix really moving away from REST + SPA? I got the sense that they're just co-locating the two things in the same file. It's like how CSS-in-JSS didn't get rid of CSS, it just put it in the JS file.
- vosper 5y agoThere’s no REST in Remix, at least not in the original sense of REST. But that’s also true of most JS web frameworks, where many use REST to mean “some API endpoints that speak JSON”. (You could do REST with Remix, but I really don’t think that’s what they’re going for)