[HN Gopher] Remix - A framework focused on web fundamentals and ...
       ___________________________________________________________________
        
       Remix - A framework focused on web fundamentals and modern UX
        
       Author : canyonero
       Score  : 36 points
       Date   : 2021-11-22 22:03 UTC (56 minutes ago)
        
 (HTM) web link (remix.run)
 (TXT) w3m dump (remix.run)
        
       | gmaster1440 wrote:
       | Looks like another contender for transitional apps[1], all for
       | it!
       | 
       | [1] https://www.youtube.com/watch?v=860d8usGC0o
        
       | cercatrova wrote:
       | I've been hearing about Remix since they were sponsorware, but I
       | don't really get the appeal. They don't seem to show how it's
       | different from e.g. Next.js, especially version 12 which seems to
       | have a similar feature set of server-side plus static rendering,
       | as well as React server components.
        
         | Bilal_io wrote:
         | 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.
        
           | vosper wrote:
           | > it handles both server side functionality (calls to db,
           | third-party APIs...) as well as the frontend code in a single
           | file.
           | 
           | Blitz JS does this to an extent, by magicking away the API
           | and letting you right your queries in your front-end code. It
           | actually works really well, and it's quite a nice dev
           | experience once you get used to it. My favourite bit is
           | writing my zod schemas and having them validate (with
           | feedback in the form) on the frontend, and also on the
           | backend.
        
           | micahbule wrote:
           | 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-able" websites whereas Remix utilizes cache headers
           | for its server-rendered pages
           | 
           | - NextJS has no baked-in support for handling session and
           | cookies; Remix has
        
           | cercatrova wrote:
           | Next.js has an /api folder that does that, is it similar?
        
             | Bilal_io wrote:
             | Take what I say with a grain of salt since I haven't used
             | either. The API folder in Next.js simply exposes API routes
             | that you can use in the frontend code of your Next.js app,
             | or not use it if you don't want to. Remix does support this
             | behavior, but it also supports exporting a data loader
             | function and/or an action function for forms that can only
             | consumed by by the page you're working on. All of that runs
             | on the backend. Again, very similar to how things are done
             | in PHP where data is loaded from a DB and then consumed all
             | within the same file.
        
       | riidom wrote:
       | This website is impressive somehow, but also crazy to parse.
       | Always at least two things going on at same time, the viewers'
       | attention constantly split instead of being guided.
        
         | Touche wrote:
         | I would have made this be /about or something like that and had
         | the landing page be something more traditional. I don't think
         | repeat visitors are going to want to scroll through a
         | presentation like that all of the time. But that could be what
         | they ultimately do, I wouldn't be surprised if they moved it.
        
         | bee_rider wrote:
         | Also it does that thing where it hijacks scrolling and uses
         | your scrolls to control an animation speed. Which probably felt
         | really clever to invent, but it is just super annoying and
         | distracting. Like who are the people scrolling back up to
         | replay bits of these silly little animations?
         | 
         | What is the point? I think they put them in there as little
         | speedbumps to catch the attention of people who are flicking
         | boredly through the site on a tablet or phone or whatever. They
         | should be more confident in their ability to keep their users'
         | attention.
        
       ___________________________________________________________________
       (page generated 2021-11-22 23:00 UTC)