Live data from Hacker News

Remix – A framework focused on web fundamentals and modern UX

remix.run

91–100 of 307 posts

Re: Remix – A framework focused on web fundamentals and modern UX

#93
post #92

This doesn't tell me anything at all, it looks like 100% marketing. Is there a comparison between this and Next.js, Gatsby or any other framework?

Exactly. They basically admit to being slower than static and try to call that clunky when really, Gatsby just takes forever to build.

Re: Remix – A framework focused on web fundamentals and modern UX

#94

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.

Re: Remix – A framework focused on web fundamentals and modern UX

#95

Earlier quoted context omitted.

> If you look at this example[0] you'll see there's not a single useState, useEffect, etc. Sorry to point it out, but there is useRef, useEffect and a useUserData on lines 48, 53, and 47 respectively.

Ah i missed those cause this is different from the demo they showed. But the point still stands. There’s not a useDtate per form field which is how react normally handles forms

Forms are one of those things that are so much easier to manage in Vue (and no extra dependencies)

https://v3.vuejs.org/guide/forms.html

Re: Remix – A framework focused on web fundamentals and modern UX

#97

I really wish there were frameworks that developed ways to plug in with your already favorite backend kit instead of solely isometric with Node. You couldn't pay me to give up Phoenix in Elixir for backend work but it does lock off a healthy amount of the neat things being done to make data loading on the frontend more optimal. Phoenix has LiveView + AlpineJS but I really don't want to give up React which still feels…

I'd say that framework are like, mmm, rails. (RoR was a genius and very candid name.) They allow you move fast and safely as long as you move in the direction the creators if the framework had in mind. Their keyword is cohesion, and their drink is kool-aid.

When you need to move in a slightly or severely different direction, you're better of with a set of libraries. They allow you to build a contraption that matches your unique problem space. They require much more time and thought to achieve the first results. Their keyword is composability, and their drink is a cocktail.

At the start, or if you are a contractor, you want something really fast, so a framework is usually inevitable, unless you're overqualified.

Down the road you keep needing to move across the rails, so you slowly switch to using more libraries.

Re: Remix – A framework focused on web fundamentals and modern UX

#98

I wonder how Remix ranks next to Blitz.js[1] or Redwood.js[2]. They seem like they're all trying to do similar things. [1] https://blitzjs.com/ [2] https://redwoodjs.com/

That's what I'm most interested in. What's the difference between remix and blitz.js? I can't find a detailed comparison anywhere

The one-line answer would be: Blitz is an additional abstraction layer on top of Next.js that offers a Rails-style set of conveniences like feature generation, plus a "compile-away" RPC abstraction that hides all data fetching. Remix is a from-scratch framework built around React Router that tries to adopt existing web APIs to minimize the amount of data-related code being written in the first place.

Re: Remix – A framework focused on web fundamentals and modern UX

#99

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...

It's hilarious isn't it. That being said, as we all know cobbling Rails + Angular or Rails + Whatever other client side library was always a hack that just used Rails as a JSON REST pump. At that point why not just use Node/Express? And so we come full circle.

Re: Remix – A framework focused on web fundamentals and modern UX

#100

This seems interesting but the rendering bugs on the website don’t give me much confidence. https://ibb.co/DfNw2GV https://ibb.co/FgW3jQb

Also the docs don’t have scroll restoration when you use the browser back button. You’d think a framework that prides itself on using the web platform would have that working automatically.
Post reply on HN