Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Remix – A framework focused on web fundamentals and modern UX

remix.run

Post reply on HN
Print view View original

191–200 of 307 posts

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

#191

Post by hnbad »

nsonha wrote: post #179
CGamesPlay wrote: post #164

So, after looking over the docs, here's my comparison list between Remix (which I haven't used) and other things that I've used. - Forms seem better in Remix. Remix seems focused on progressive enhancement here, rather than fetch. Imagine if Next supported POST endpoints, and the idiomatic way of making your site was to use that instead of API endpoints. I hope that we soon see a Remix-compatible form validation libr…

> Forms seem better in Remix. Remix seems focused on progressive enhancement here, rather than fetch. Imagine if Next supported POST endpoints, and the idiomatic way of making your site Remix does nothing to make this happen, it's just the way html works. I dont see how it would not work on next. The difference is api is in a separarate directory and remix have them in the same file. Superficial.

It actually seems that Remix just wraps the form element with its Form element that prevents "the way html works" from happening and instead provides a loading/submission state to the UI while performing the form submission via fetch in the background. At least that's what the demo suggests.

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

#192

Post by gherkinnn »

unclebucknasty wrote: post #67

They lost me at: return ( {projects.map((project) => ( {project.title} ))} . . . I don't know why we need another framework that smashes together code and HTML/directive-based templates like this and, generally, keeps us bound so tightly to web idioms. Would be nice to have a framework that obscures these kinds of "web fundamentals", so we no longer have to wrangle such low-level primitives to build complex apps. EDI…

This comment is at least 5 years late. JSX has been a thing for so long now and it works.

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

#193

Post by bryans »

gherkinnn wrote: post #180
bryans wrote: post #160

Earlier quoted context omitted.

I disagree wholeheartedly. This site breaks every UI/UX rule in the book, and in the worst ways. Instead of just letting people read the information at their own pace, they've decided to limit the information to one partial sentence at a time, and more than half of those sentences are just irrelevant jokes. Possibly even worse is the lack of snapping to the sentence, which means the user has to guess how far they nee…

Think of it as a video but you scroll through it. It’s really not that novel a concept.

I never said it was a novel concept or that the functionality is confusing. I just said that it's terrible, which it absolutely is, and your video comparison actually reinforces my point.

They could have made this presentation into a 30 second video, which would have extremely simplified the access to information, while also only requiring one click, and still providing the ability to pause the flow of information when necessary. Instead, the page takes 39 manual scrolls to read through a bunch of tech bro jokes.

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

#195

Post by hnbad »

PKop wrote: post #138
msoad wrote: post #118

I remember the team had the idea of charging for the software but now I am seeing that they raised VC money. There is no question that this sort of company can be big (See Vercel) but I'm wondering why this decision was made?

because this sort of company can be big

If this sort of company is vercel, sure. But right now remix has no obvious monetization strategy. It seems obvious they'll announce a SaaS solution eventually but it's not clear what the value add will be.

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

#196

Post by jack_riminton »

jacobsenscott wrote: post #91

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

Maybe the next great new thing is react code that gets converted into ruby.

In serious though I really hope that Hotwire can become mature and intuitive enough to completely negate any need for a js framework on top of a rails backend

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

#197

Post by Kiro »

bryans wrote: post #193
gherkinnn wrote: post #180

Earlier quoted context omitted.

Think of it as a video but you scroll through it. It’s really not that novel a concept.

I never said it was a novel concept or that the functionality is confusing. I just said that it's terrible, which it absolutely is, and your video comparison actually reinforces my point. They could have made this presentation into a 30 second video, which would have extremely simplified the access to information, while also only requiring one click, and still providing the ability to pause the flow of information wh…

That's just your opinion. I think it's awesome and if it really "breaks every UI/UX rule in the book" it's a great example of how breaking the rules can be a good thing.

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

#198

Post by peterhunt »

dreyfan wrote: post #147
jacobsenscott wrote: post #91

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

Watch the demo, they're not full circle yet. They're intermingling business and presentation logic all over the place. Their data models depend on createPost(), getPost(), and getPosts() style boilerplate methods. It'll be a couple years yet before the JS community reinvents MVC and ORMs (under a really slick name of course), then we'll be full circle.

Intermingling business and presentation logic is fine - even preferred - when they are tightly coupled. Lots of “business logic” is actually just presentation logic anyway.

I don’t think the JS community is going to make the same mistakes Rails did. I for one am glad the days of highly mutative, untyped MVC are coming to an end.

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

#199

Post by Vinnl »

jacobsenscott wrote: post #91

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

I find this "everything old is new again" such a tiring take. Sure, you can do things you could already do in Rails, but without giving up on the things people adopted React for. Like client-side updates without full page refreshes.

If you fool yourself into thinking that a few similarities to what you're used to means that there's nothing new to learn, you're missing out.

(To be clear, I'm not saying that everything new is automatically better, or that even Remix is. I'm saying that it's foolish to dismiss something without trying to understand what it brings to the table that you've not experienced yet.)

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

#200

Post by andrewingram »

mcintyre1994 wrote: post #171
CGamesPlay wrote: post #164

So, after looking over the docs, here's my comparison list between Remix (which I haven't used) and other things that I've used. - Forms seem better in Remix. Remix seems focused on progressive enhancement here, rather than fetch. Imagine if Next supported POST endpoints, and the idiomatic way of making your site was to use that instead of API endpoints. I hope that we soon see a Remix-compatible form validation libr…

Next does technically support POST endpoints, in that API endpoints support any HTTP method and receive which one it is as part of the incoming request. Definitely less nice than the way Remix handles it though.

It does, but the convention with forms is that you POST to the path you're on, rather than a different one. This is so that if there are any form validation errors you can easily re-render the current page with the errors added. To get this behaviour in Next, you'd have to hijack getServerSideProps (which is what the lib in one of your sibling comments does).
Post reply on HN