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

151–160 of 307 posts

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

#151

Post by ducharmdev »

couchand wrote: post #104
SavantIdiot wrote: post #74

Earlier quoted context omitted.

Frameworks are designed for the following (this is obviously an incomplete list): 1. large teams (not just one webmaster, circa 1999) 2. tooling like syntax checking, style enforcement, minification, and transpiling 3. component-based development & reuse; forces smaller files which are easier to lint and test 4. separation of concerns. in the old days there was one Apache www folder and everyone took a big shit in it…

> JavaScript allows getter/setter methods that can update the DOM when a value changes; this includes before/after and around-like methods that can integrate AJAX calls in a VARAIBLE name. e.g., you access the variable and an AJAX call fires and updates your DOM when the data returns with you doing ZERO coding. Maybe I'm old but that sounds TERRIBLE. When my code is doing something expensive like a network call, I wa…

Is this really new though? MVVM .NET apps similarly use getters & setters in this manner, except with XAML.

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

#152

Post by abraxas »

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.

Yeah, this is basically Vaadin and Spring for young hipsters.

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

#153

Post by jtsiskin »

aarpmcgee wrote: post #136
flybayer wrote: post #127

Earlier quoted context omitted.

Yes, definitely different takes on the same problem! We could make a comprehensive list of all the differences, but the end result is that you can use all three (four if you include Next.js) to build any web app imaginable. At the end of the day, you must try them each for yourself and find which one resonates most with you and your team.

Thanks for the reply. Honestly, I'd love to see such a list, or even a short summary of each that provides as solid intuition as to why I might choose one over the other.

Agreed, would really love this. Please update if you find anything good!

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

#154

Post by acemarke »

unclebucknasty wrote: post #137
newsbinator wrote: post #126

Earlier quoted context omitted.

I don't mind vouching for this comment because it does further the discussion. It's a lot more interesting that the "let's should be lets" comments.

Hey, I appreciate that. I noticed in another of your comments you mentioned it seemed similar to Nuxt.js and you were digging in further to look for differentiation. That's kind of what I'm getting at here: things in this space are moving needlessly incrementally at this point, creating so many permutations on largely the same underlying themes and staying pinned to original Web semantics. Why do we accept HTML as an…

Given that the entire Remix team has spent the last several years doing training teaching people how to use React, and building one of the core libraries in the React ecosystem, this seems like a rather off-tangent train of thought and unrealistic expectation for what Remix might have been.

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

#155

Post by chairmanwow1 »

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!

It truly is one of the best mobile-optimized product explanation pages I’ve ever visited. Good callout.

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

#156

Post by folkrav »

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 suspect the reason it's not as daunting as it usually can be is cause it doesn't feel like it's scroll-jacking you, in a sense. When you're scrolling, it still feels like you're going "downwards". You stop scrolling, animation stops in its tracks pretty quickly.

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

#157

Post by shrimpx »

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.

The broader way to see it is that people are trying to bake reactivity into these old school paradigms that have a lot of good things about them in terms of separation of concerns and working with data, but suck at reactivity.

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

#158

Post by unclebucknasty »

acemarke wrote: post #154
unclebucknasty wrote: post #137

Earlier quoted context omitted.

Hey, I appreciate that. I noticed in another of your comments you mentioned it seemed similar to Nuxt.js and you were digging in further to look for differentiation. That's kind of what I'm getting at here: things in this space are moving needlessly incrementally at this point, creating so many permutations on largely the same underlying themes and staying pinned to original Web semantics. Why do we accept HTML as an…

Given that the entire Remix team has spent the last several years doing training teaching people how to use React, and building one of the core libraries in the React ecosystem, this seems like a rather off-tangent train of thought and unrealistic expectation for what Remix might have been.

>this seems like a rather off-tangent train of thought

It's funny to hear someone complain about tangents on an HN thread. And, right on cue, as of this writing the top comment [0] literally starts with the phrase ”Off topic:" and has 7 replies.

Irony aside, my point is very much on topic, as I am asking exactly the question, "what if teams like Remix had instead invested their considerable talents and years-long efforts in building a truly paradigm shifting approach to webdev?"

What I'm suggesting here is that it's time to advance the state of the art in Web development. But, I could certainly be wrong. It might instead be time for another incremental improvement in the React/Vue/Angular-ish, HTML/code-mashing, shadow DOM-rendering, SSR-driven, reactive framework universe.

[0] https://news.ycombinator.com/item?id=29313460

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

#160

Post by bryans »

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 need to scroll to fit the text in the available space. The text is even so large that some sentences don't fit in that space. It becomes a seemingly endless loop of reading 6 words, scrolling, reading 8 words, scrolling too far and then scrolling up, reading a 5 word joke, scrolling not far enough, etc.

In fact, it's 39 mouse wheel scrolls to get to the bottom of the page, all to read one paragraph of actual information -- and that information is mostly a bunch of boisterous posturing, in order to make a pitch that amounts to a couple of prescribed patterns.

Post reply on HN