101–110 of 113 posts
Here is an article I wrote of why we chose it https://d13z.dev/blog/07-why-kleinanzeigen-picked-astro-over...
I still dont understand the lie, that its difficult to host next.js. I am hosting several nextjs apps for my day job. We just put them in a docker and throw them on the server, whats the confusion?
For example if you stay as close as possible to the framework defaults, everything is golden. But as soon you start pushing it to the limits the cracks start to appear.
Last year I was working on a NextJS app with 15k files, 18k unit tests, 100+ developers in the same repository and a page with hundred of millions of page views daily. Under that conditions NextJS doesn't scale, but again, those conditions are not the majority of the NextJS cases.
In that project, we have been using NextJS as a standalone for around 5 years and each time NextJS rollout a major version it take us at least 2 months to be able to upgrade and keep it working.
Next has become a joke. It’s mildly frustrating that with Remix’s inexplicable transformation into react-router, there’s few great react frameworks left (for me), I’m back to plain vite with tanstack router.
I’m surprised this post is able to stay up on hackernews. One time I simply made a post about how a page was simpler to code and understand in Remix. You may not believe this but I had 3+ chat requests from multiple employees at vercel. Across multiple social media accounts. All asking to take it down or meet and discuss with them.
What's the recommend full-stack setup, if not NextJS? My background: I have ~15 years of software development experience, but practically all of it in backend stuff. (Well, I did some AngularJS a decade ago but that's it.) So, when I recently wanted to build a fullstack app for the first time for a side project, I looked around and learnt NextJS was the way to go. (Gemini said that, then Cline's official documentatio…
What are you building? I am working on a classic SaaS webapp, and I have found that using React/Refine.dev/Vite has been great. Refine.dev let me focus on my features, and not basic CRUD page stuff.
I still dont understand the lie, that its difficult to host next.js. I am hosting several nextjs apps for my day job. We just put them in a docker and throw them on the server, whats the confusion?
Instead of being cowards, please reply what features of Next do not work in self hosting through a simple 1 line Docker image?
Next and RSCs have become some of the most frustrating things I've worked with on frontend. Dealing with FE is already annoying enough, but having to wrestle the magic of Next and then vendor lock-in to Vercel to top it off. Team is trying out Tanstack router + vite this week. Excited to build a regular ass CSA.
> Next and RSCs have become some of the most frustrating things I've worked with on frontend What is frustrating about RSCs? They work really well for me and I'm still using Next.js only because of RSCs.
But don't let a random internet stranger detract you. If it works for you, go for it.
Next has become a joke. It’s mildly frustrating that with Remix’s inexplicable transformation into react-router, there’s few great react frameworks left (for me), I’m back to plain vite with tanstack router.
I'm not sure if you are implying that you aren't using remix anymore after the rebranding, or that it's not a framework anymore? Because React Router 7 definitely works as a framework [1] and it works like a charm. Source: Backend developer with 15 years experience, lately switched to full stack, using RR7 after advice from a very good friend, still getting amazed every day. [1] https://reactrouter.com/start/framewor…
Earlier quoted context omitted.
What's the issue with the remix -> react-router transition? As far as I can tell it's just a branding thing.
I started learning Remix, which was then relaunched as RRv7. Now Remix is going to be revived, and based on Preact instead[0]. I have given up and started learning NextJS. At least it has marketshare, while Remix will never gain traction because it keeps getting torpedoed by a couple of pivot artists. [0] https://remix.run/blog/wake-up-remix
Earlier quoted context omitted.
Can you suggest alternatives? I've used Next and Svelte[kit] in prod and have been very unhappy with both.
Can you name/explain your problems with them? What was the intended use case and goals, what did you like about them, and what you didn't, and what was something that was definitely missing for you?
Built in scoped CSS is a great idea and compiled bundle is nice. I used it for multiple projects (order system, admin panels, etc) and it always feels that little bit more brittle when I use Svelte vs something more mature. I won't use it again for any project.
I have less experience with Next and it was longer ago but iirc I found it needlessly hard to use and deploy as well as some problems with Image tags (you need the exact size of the images?). I also found their gamified tutorial really off-putting and indicative of corporate bloat which I guess makes sense now that they're locking users in. The reason I used it was for page loading speed optimization (SSR) and didn't find any better alternatives that use React at the time. I use Next for my landing page https://audiodiary.ai and for its admin panel.
Earlier quoted context omitted.
Can you name/explain your problems with them? What was the intended use case and goals, what did you like about them, and what you didn't, and what was something that was definitely missing for you?
Svelte is very immature in terms of tooling and IDE support and that hasn't seemed to improve in the last 7 years of using it. Libraries are sub-par vs React and the design of the language does not favor making things explicit. $:{} for example is not explicit, I'd much rather use a slightly longer token (like useEffect) to help document what's going on. That's just one example, it's riddled with things like that (e.…
FWIW you're describing a legacy syntax — modern Svelte has explicit effects, and addresses your other concerns. I think you'll find it's much more to your liking https://svelte.dev/docs/svelte/$effect