Live data from Hacker News

Ask HN: What is your preferred “full-stack in a box” solution and why?

news.ycombinator.com

11–20 of 37 posts

Re: Ask HN: What is your preferred “full-stack in a box” solution and why?

#11
For me it's Next.js + postgres, using TypeScript.

I've been building projects in React since around 2016, and Next.js just makes the annoying things go away (static rendering for SEO pages, image optimisation, code/bundle splitting, page routing, etc).

Re: Ask HN: What is your preferred “full-stack in a box” solution and why?

#15
SvelteKit. I have a high risk tolerance but SvelteKit is the framework I've been waiting for since I first started using Pyramid & Django in 2010. All the plumbing, optimization, and performance is done with no configuration and a harmonious integration of back-end and front-end (finally!). I really really love it.

Heck, I'm even releasing my SvelteKit stack as a SaaS boilerplate for others to launch projects more quickly: https://sveltesaas.com

Re: Ask HN: What is your preferred “full-stack in a box” solution and why?

#18
Typescript, React & Posgres or SQLite. I’m really enjoying Remix.run. It’s shares some commonalities with SvelteKit & NextJS. . This is subjective of course, but I enjoy how in Remix there is only 1 way to fetch data, which I believe is simpler mental model & way to get started with or work with:

“The fundamental difference here is that Next.js has four "modes" for getting data on the page: (1)getInitialProps - called server and client side (2)getServerSideProps - called server (3) getStaticProps - called at build time (4)client fetching - called in the browser with Remix there is only 1 called loader”

https://remix.run/blog/remix-vs-next

Post reply on HN