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

111–120 of 307 posts

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

#111

Post by npsomaratna »

cubano wrote: post #60

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…

Check out Laravel Livewire: https://laravel-livewire.com/ — this is based on a similar concept. (If course, you do need to be using Laravel in the first place!)

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

#112

Post by danr4 »

brundolf wrote: post #76
danr4 wrote: post #30

Earlier quoted context omitted.

the team behind remix probably has the biggest following in the react scene, so even without having any major differentiation (though I happen to think they do have) it's going to gain popularity.

I'd never heard of Remix before today. To contrast, I heard about Next 3-4 years ago, despite not using it at work until a few months ago

Well Remix just released today, so it's not surprising you haven't heard about it. You'd have to follow Ryan, Michael and Kent, the people behind remix.

Guillermo Rauch (main dude behind Next and Vercel) was well known in the scene before next which also helped it gain the initial traction to build upon.

Feels like a similar case. IIRC remix wasn't suppose to be open source, but feels like nowadays it's a better choice for them to go the Next route and build services around their framework.

My bet is they'll build a Cloudflare Edge Suite abstraction (or even get bought by CF for their edge offerings)

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

#113

Post by azangru »

haolez wrote: post #79

Off topic: this is the best landing page I've ever seen on a mobile device. Keep scrolling down for some surprises!

Which device did you view it on? I tried to view it in mobile Chrome on a Samsung Galaxy S7, and apart from the page not fitting the screen, there were quite a few visual bugs. If I hadn't viewed this page on a laptop before, I would have been discouraged.

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

#114

Post by kall »

Grimm1 wrote: post #71
colinclerk wrote: post #57

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.

Well you could run it as a sort of rendering layer in front of your backend, and talk to your phoenix app on an internal API or local socket. May not be worth it though. Unlike next, I don‘t think you can even run this as SPA only.

I think for remix to be able to do what it does, it kind of needs to run as a JS (not node!) backend, because a big part of it is running react on the server. Also, you are literally writing the server and client code in the same file. Closure and Reason which have strong react ports/bindings might be able to do it, but otherwise I don‘t see how.

What other backends need is probably a totally different framework, that wraps up a react server renderer with native language bindings. Might be neat, but totally different.

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

#116

Post by andrewingram »

magicink81 wrote: post #87
timdorr wrote: post #26

Earlier quoted context omitted.

I like to think of like this: I use Next.js for my marketing site. I use Remix for my web app. Next is good if you just need to get some HTML on the page. Remix is good if you need a connect to a database or backend API.

I'm curious what do you think is missing from Next.js that would make it better at connecting to databases and backend APIs? There is a bit of evidence that people are building heavily used web apps with Next.js that connect to databases, backend APIs, and expose APIs of their own, for example: https://nextjs.org/showcase

Yeah, other than the nested route thing, there doesn’t seem to be that much difference between Next and Remix when it comes to talking to a database.

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

#119

Post by chrisweekly »

micahbule wrote: post #10
Bilal_io wrote: post #3

Earlier quoted context omitted.

They just did (maybe still going) Q&A session where they did a demo and answered question. Remix seems to be more like PHP or Ruby On Rails, it handles both server side functionality (calls to db, third-party APIs...) as well as the frontend code in a single file.

That can be done on NextJS as well using getInitialProps, getServerSideProps, or getStaticProps Some of the notable differences between NextJS and Remix are the following: - While both support file-based routing, Remix is baked with React Router -- giving developers the capability to declare custom routes without sticking to file structure conventions - NextJS banks on its static site generation to generate "cache-ab…

NextJS ships with both the built-in fs router AND a traditional imperative router.

Also, there's a lot more to caching with NextJS than SSG.

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

#120

Post by jijji »

I was reading through the documentation and the only thing I think is really lacking is the fact that there's no screenshots or examples of what the UI winds up looking like after the code has been written... is there any examples of what any of this looks like from the user perspective from the web browser side?
Post reply on HN