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

171–180 of 307 posts

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

#171

Post by mcintyre1994 »

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.

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

#173

Post by tshaddox »

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?

They used to openly albeit implicitly mock open source software projects taking big VC money, by saying things along the lines of “we have a radical business model where we just charge people to use our product.” Noble, perhaps, and probably a good way to kickstart community good will, but the VC money is undoubtedly a much faster way to scale the fiscal size of the company!

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

#174

Post by mirzap »

bryans wrote: post #160
danr4 wrote: post #18

I usually have deep hatred towards scroll-jacking but this was actually quite well done. Not because of the pizzazz but because it essentially put only one thing to learn on the screen at once. It was like a "getting started" section that might be slower to go through but feels like it's faster to understand.

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…

Well, on a first page without any scroll you have action buttons which leads you to the pages where you can read at your own pace. For people who don't want that they've put small bits of information on each scroll. Every information is carefully chosen, so you keep scrolling and reading. After that you go to the doc to read more. I've never seen better UI/UX that hook me in so quickly. If it was just regular page I would think "ah, just another framework" and close the tab. This is is how UI/UX should be done. Bravo!

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

#175

Post by BigJono »

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…

No, I didn't downvote you because I'm "suffering from a lack of imagination". I downvoted you because those "web fundamentals" are the web fundamentals. Putting another abstraction layer over it to obscure it does jack shit other than make your code more complicated. As long as I need to render a h1 or a div to draw anything on a web page, then I want control over the h1s and the divs. If there was a way to get away from that then sure, I'd be all for it.

And "smashing together" code and templates is the best thing to ever happen to web development. Template languages suck ass, they rely on thousands of lines of build time magic to work. JSX is a line for line transform (which is as simple as the build time logic can get while still enabling any sort of templating whatsoever), that conceptually maps back to a simple call to add an element to the DOM some time in the future.

As soon as you get over the "ew, code and "html" together" reaction, you realise that "everything as code" is the easiest way to just completely avoid hidden complexity and surprises.

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

#176

Post by BigJono »

kreeben wrote: post #55
npilk wrote: post #50

I know this is low-value, but it always stuns me to see basic typos on a product’s landing page (lets —> let’s). Have the creators shown it to anyone else? Has nobody close to them told them about it? I don’t blame anyone for making a mistake - everyone does it, and I’m certainly no exception. But typos like this make a product feel much less professional and by extension less trustworthy. To me, good copy feels impo…

Sure but on the other hand you have copy that has gone through five levels of managers OK-stamping it but only after fixing the errors and sanding down all sharp edges, your text churned into corporate yogurt that no one in their right mind would ever believe because it resembles FAANG speak too much. I kind of like the odd error here and there. Makes me feel safe to at least try out their product.

Is that not what's happened to this site anyway? Looks an awful lot like corporate yogurt to me.

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

#177

Post by pssdbt »

cyral wrote: post #131
magicink81 wrote: post #128

Earlier quoted context omitted.

Next.js has had nested routes since version 6. Not sure I see the difference in what Remix is offering? https://nextjs.org/docs/routing/introduction#nested-routes

I don't think the nested routes mean the same thing on the NextJS page. To my knowledge, NextJS doesn't support nested routers which is really what many are after. Like in the Remix demo, there are various content areas with nested content, which would be controlled by the URL. You can create url parameters manually like /account/:tab/:id but it's kinda hacky as you have to use router.params['param-here'] to get the…

I think what you're looking for is nested routes _and_ layouts. It's possible in Next but IMO it's not the prettiest.

https://nextjs.org/docs/basic-features/layouts#per-page-layo...

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

#178

Post by kome »

lifeformed wrote: post #169
kome wrote: post #145

Earlier quoted context omitted.

wow, i have a radically different opinion from yours. for me it is the perfect example of some bad trend in webdesign. It feels like a powerpoint. And just to be clear: powerpoint is useful in some cases, but not on the web. On the web, it sucks. It's mindbogglingly bloated and terrible.

What's wrong with using a familiar presentation style for what is essentially a presentation?

it's not the right format for the medium. slides are ok in class, or during a meeting - the web is different.

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

#179

Post by nsonha »

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.

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

#180

Post by gherkinnn »

bryans wrote: post #160
danr4 wrote: post #18

I usually have deep hatred towards scroll-jacking but this was actually quite well done. Not because of the pizzazz but because it essentially put only one thing to learn on the screen at once. It was like a "getting started" section that might be slower to go through but feels like it's faster to understand.

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.

Post reply on HN