81–90 of 307 posts
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…
I really wish there were frameworks that developed ways to plug in with your already favorite backend kit instead of solely isometric with Node. You couldn't pay me to give up Phoenix in Elixir for backend work but it does lock off a healthy amount of the neat things being done to make data loading on the frontend more optimal. Phoenix has LiveView + AlpineJS but I really don't want to give up React which still feels…
My theory is, you can afford one big abstraction (React) on top of platform (HTML/JS/CSS/Browser). Try to abstract beyond that, and things get unnecessary, bloated, and difficult to reason about.
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, and then a separate /api folder for any backend apis you want to set up.
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.
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 thro…
If this is just Next.js with nested routes, it‘s already worth it. Seems like they have a bit more going on with progressive enhancement and interaction support, but nested routes are the headline for me.
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.
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
I wonder how Remix ranks next to Blitz.js[1] or Redwood.js[2]. They seem like they're all trying to do similar things. [1] https://blitzjs.com/ [2] https://redwoodjs.com/
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…
I think this new wave of server-enabled React is enabling codebases that are better organized than old MVC stacks. The MVC way was: 1. Look at the route 2. Recognize that this route has, e.g. A Header, A Sidebar, and Content 3. Load the data for the Header, Sidebar, and Content 4. Pass the data to the templating engine 5. Use the templating engine to render the route, which likely fans the data for the Header, Sideba…
https://engineering.fb.com/2010/06/04/web/bigpipe-pipelining...