5 ms·
> ... when you're deep in it, its hard to miss the forest for the trees. That's very confusing. But so is the entire article. While I have your attention, as
by hilux 3y ago
> ... when you're deep in it, its hard to miss the forest for the trees.
That's very confusing. But so is the entire article.
While I have your attention, as a relative newbie to web dev (with limited time and focus), is Next.js my way to go?
- 65 3y agoI hate Next.js because they make it extremely difficult to deploy an SSR app anywhere except Vercel. You basically have to use the Docker image to deploy your SSR Next.js app. I prefer https://remix.run https://remix.run or https://vike.dev https://vike.dev However, if you just want a static site, Next.js is great.
- Aeolun 3y agoOoh, looks like I need to check out Vike. It may address all concerns I have with Next :)
- 65 3y agoI use it on my personal site. It's great - easy to use and super robust. Hopefully more people use it.
- OccamsMirror 3y agoThere's also Astro: https://astro.build/ https://astro.build/ - which admittedly I haven't tried yet but am planning on checking out for my personal site.
- ringofchaos 3y agoAstro is great, using it for my blog site and. I have a mono repo setup React SPA and Astro For Blog. I can create a reusable component in React Repo and reuse in Astro blog. You could also write native astro components which are very close to vanilla html css with added benifit of making reusable components and scoped css. And you can also use svelte or vue components.
- pcthrowaway 3y agoAnother vote for Astro. Honestly, you can use Astro and then still use React if you want. Doing so would be similar to next.js in some ways, though you need to hook up an adapter if you want server-side rendering
- jitl 3y agoWhat is the challenge you’ve had deploying SSR Next, and how does it relate to docker? I’ve only used it in docker (I like docker), but I haven’t seen anything in about Next that seems docker oriented.
- 65 3y agoBecause of how Next.JS builds, you can't just deploy it as-is to something like AWS Amplify or Elastic Beanstalk. For example, if you attempt to deploy to Amplify, you'll get a bunch of 503 errors on SSR pages because of Cloudfront permissions. The static pages work fine though. I'm not exactly sure as to why you can't just "npm run start" on a Next.js app on a deployment service like ELB or Amplify. Perhaps because of the extra SWC compiler Next uses for builds? I believe Docker works because you're doing "npm run start" and containerizing Next.js, essentially proxying the server to then serve to the client. Basically running it on localhost. For example, you can run Next.js on EC2 if you want, but you have to proxy the connection to allow the client to connect to it. Again, I'm not an expert as to why exactly it doesn't work - I just know that it doesn't work the same way a simple node app works, which therefore adds a ton of steps involved that don't make it worth it to me.
- Inviz 3y agoWhat are frameworks that support async components on clientside?
- 0xblinq 3y agoRemix is so much better than Next. We moved a project at work and it’s been night and day for us. Not going back.
- dabber 3y ago> as a relative newbie to web dev (with limited time and focus), is Next.js my way to go? Obviously "it depends (TM)" on a bunch of things but for most of those things, Next.js is a safe bet, sure. It's a (the?) leader in the React framework space and the ecosystem reflects that (e.g. most problems or decisions a newbie would run into is likely to have a trove of docs/blogs/tutorials/ect. available to get past them quickly, plenty of options for hosting, marketable as a skill if that's what you're into, fine DevEx all things considered, it'll likely be around for quite some time even if vercel shuts down tomorrow.) The same is true for React. I'd personally go with Remix though :)
- Aeolun 3y agoI have both Next and Remix projects and I far prefer Next. While Remix is cool, and they were kind of the original, their build and dev process has become really bloated, so any change now means waiting a minute for the whole server to restart.
- garspin 3y agoTry Svelte - especially for personal projects. It's v. easy to get started. Downside is that there are many jobs yet.
- coldtrait 3y agoAs someone with just limited React knowledge I recently started with Next, got stuck with something and moved on to Svelte. It was really easy until I ran into some errors there and eventually came back to Next. Svelte is certainly easy to pick up, compared to anything React oriented like Next IMO. That said, the issue I had with most of these frameworks were integrating other libraries into them and quite a few of them seemed to not match with whatever version either the framework was using, or the libraries themselves were outdated. Then again, I'm a noob at this so it most likely could have been my lack of knowledge.
- hilux 3y agoThis is very helpful. I wanted a perspective from a "noob," since your experience and goals probably more resemble my own.