101–110 of 307 posts
So the web dev madness has come full circle - the react people just built rails in react. In the mean time I just keep using rails...
So the web dev madness has come full circle - the react people just built rails in react. In the mean time I just keep using rails...
Might consider Vue.js for writing new very interactive components...
Nice. Defining multiple zones, each with their data and error boundaries, at little to no cost is a nice approach. Though as silly as it might sound, Remix’ publicity work has put me off it. Will read the docs anyway.
Same, the way they have went about "evangelizing" for it really left a bad taste
So as a 56yo "old school" LAMP-stack monkey, could someone please give me a quick rundown exactly what benefits would investing the mental energy (a non-trivial amount) and time (less an issue) give to someone in my ancient yet comfortable canvas Cons? For sure next.js is an interesting framework and of course I use plenty of typescript in my projects to keep the UXs from feeling stale, but I have yet to see the over…
Frameworks are designed for the following (this is obviously an incomplete list): 1. large teams (not just one webmaster, circa 1999) 2. tooling like syntax checking, style enforcement, minification, and transpiling 3. component-based development & reuse; forces smaller files which are easier to lint and test 4. separation of concerns. in the old days there was one Apache www folder and everyone took a big shit in it…
Maybe I'm old but that sounds TERRIBLE. When my code is doing something expensive like a network call, I want to know about it.
So the web dev madness has come full circle - the react people just built rails in react. In the mean time I just keep using rails...
More than madness, this seems like evolution, learning, and standing on the shoulders of giants.
Off topic: this is the best landing page I've ever seen on a mobile device. Keep scrolling down for some surprises!
Earlier quoted context omitted.
There's no strong requirement to use Node for your backend...your Remix codebase can fetch() data from anywhere in the `loader` function: https://remix.run/docs/en/v1/guides/api-routes#api-routes
I get that I can run this as a SPA, but then don't I lose out on the prerendered HTML fetched from the server? That's what I mean by isometric with Node.
Earlier quoted context omitted.
More than madness, this seems like evolution, learning, and standing on the shoulders of giants.
Also as much as rails seems so popular, I REALLY don't like rails so this seems to take what's good about it and removes some of the nonsensical opinionated crap. I'm not too much of a fan of node either but it's easier to work with IMO
Earlier quoted context omitted.
There's no strong requirement to use Node for your backend...your Remix codebase can fetch() data from anywhere in the `loader` function: https://remix.run/docs/en/v1/guides/api-routes#api-routes
I get that I can run this as a SPA, but then don't I lose out on the prerendered HTML fetched from the server? That's what I mean by isometric with Node.
I agree with you in the sense that I don’t want to write server code in Node since I like batteries-included frameworks (Django)…
I guess you’re talking about features like form validation and whatnot?