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

301–307 of 307 posts

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

#301

Post by PKop »

e1g wrote: post #144
PKop wrote: post #138

Earlier quoted context omitted.

because this sort of company can be big

Remix, like other such attempts, will need to get into the hosting business. Give out a good framework to ensure lock-in, then sell the infrastructure/runtime to deliver the app built on your framework. Then sell add-ons like $5/mo for authentication, $10/mo for I18N, etc.

Yes this is what they discussed in their live stream this week. The blueprint is clear, execution is no guarantee, but seems like a no-brainer if they want to work on this full time and really want it to be a widely used javascript framework, and if someone is going to give them money to try. Personally I think it brings a lot to the table and I loved the programming model (SSR, loading data on server, common platform primitives etc) compared to Next.js prioritizing SSG. I think they have a good team and a good shot at gaining market share.

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

#302

Post by micahbule »

chrisweekly wrote: post #296
micahbule wrote: post #288

Earlier quoted context omitted.

I'm not aware of said functionality on the client-side. Out of curiosity, do you mind linking me to said documentation or article on how to circumvent routing on the client-side without using fs-based routing?

https://nextjs.org/docs/advanced-features/custom-server#disa... > "You may also wish to configure the client-side router to disallow client-side redirects to filename routes; for that refer to router.beforePopState." https://nextjs.org/docs/api-reference/next/router#routerbefo...

That is through using a custom server -- which is a whole other topic. I'm comparing apples-to-apples between NextJS's built-in router and Remix's usage of React Router as far as client-side routing is concerned.

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

#303

Post by e1g »

PKop wrote: post #301
e1g wrote: post #144

Earlier quoted context omitted.

Remix, like other such attempts, will need to get into the hosting business. Give out a good framework to ensure lock-in, then sell the infrastructure/runtime to deliver the app built on your framework. Then sell add-ons like $5/mo for authentication, $10/mo for I18N, etc.

Yes this is what they discussed in their live stream this week. The blueprint is clear, execution is no guarantee, but seems like a no-brainer if they want to work on this full time and really want it to be a widely used javascript framework, and if someone is going to give them money to try. Personally I think it brings a lot to the table and I loved the programming model (SSR, loading data on server, common platfor…

The execution challenge for Remix is how to navigate the tension where FOSS and commercial forces pull them in opposite directions. So far, they've been stressing "interoperability", "no lock-in", "run it anywhere", etc. To live up to this goal, they'll need to maximize how portable Remix is, which will minimize the value of their specialized runtime service. Meanwhile, players like Vercel always positioned their products+services as a natural pairing, where the best stuff is inside the walled garden.

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

#304

Post by [deleted] »

areeh wrote: post #294
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…

I can see how it scores poorly on the number of scrolls per paragraph of information, maximum words read per unit of time, etc, but clearly that is intended with the choice of spacing and font size which is different in the docs (typically optimized for providing information, similar to what your metrics seem to try to measure). I think it is more usefully analyzed as a landing page, with a lot of emphasis on how it…

[deleted]

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

#305

Post by austinthetaco »

bryans wrote: post #295
austinthetaco wrote: post #291

Earlier quoted context omitted.

Analyzing usability metrics is not in the purview of a developer typically, especially not for random tech tools.

What a ridiculously untrue and narrow-minded statement. If you've only worked at companies where you're one tiny cog amidst ten thousand employees, sure, you may have a designer or psychologist who specializes in UI/UX analysis. However, that does not describe the VAST MAJORITY of tech teams, and frankly, any frontend developer who isn't analyzing their output or at least taking a moment to think "hey, maybe 39 scrol…

I specialize in working with startups and small development teams getting their tech stack up and running or fixing growing pains. I must have worked with hundreds of teams at this point, and not once has it been standard fair. You are MASSIVELY conflating noticing a UI inconsistency with analyzing usability metrics, the two things aren't even in the same arena, and the fact that you would compare the two gives me the idea that you may be on the more junior side.

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

#306

Post by jacobsenscott »

PikachuEXE wrote: post #102
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 haven't used any modern framework yet (still rails). Might consider Vue.js for writing new very interactive components...

Be sure you try stimulus and turbo first - you might find it is much better that way. Vue and react both have the same problem - it forces you to move your html into the JS. At that point you have no other choice but to move everything to js the database (vuex), validations, routing, internationalization, etc.

In theory you can just decorate your server side html with vue tags, but in reality that only works for simple hello world demos. Vue wasn't really built for that.

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

#307

Post by PikachuEXE »

jacobsenscott wrote: post #306
PikachuEXE wrote: post #102

Earlier quoted context omitted.

I haven't used any modern framework yet (still rails). Might consider Vue.js for writing new very interactive components...

Be sure you try stimulus and turbo first - you might find it is much better that way. Vue and react both have the same problem - it forces you to move your html into the JS. At that point you have no other choice but to move everything to js the database (vuex), validations, routing, internationalization, etc. In theory you can just decorate your server side html with vue tags, but in reality that only works for simp…

Thanks

I have stimulus in my scope too

We have some JS code works similar to it but still considering the testing and transition method.

Before that I got some dependencies need to be updated first

Post reply on HN