Need advice about which tool to choose?Ask the StackShare community!
Next.js vs Yesod: What are the differences?
What is Next.js? *A small framework for server-rendered universal JavaScript apps *. Next.js is a minimalistic framework for server-rendered React applications.
What is Yesod? A RESTful Haskell web framework built on WAI. Yesod believes in the philosophy of making the compiler your ally, not your enemy. We use the type system to enforce as much as possible, from generating proper links, to avoiding XSS attacks, to dealing with character encoding issues. In general, if your code compiles, it works. And instead of declaring types everywhere you let the compiler figure them out for you with type inference.
Next.js and Yesod belong to "Frameworks (Full Stack)" category of the tech stack.
Some of the features offered by Next.js are:
- Zero setup. Use the filesystem as an API
- Only JavaScript. Everything is a function
- Automatic server rendering and code splitting
On the other hand, Yesod provides the following key features:
- safety & security guaranteed at compile time
- developer productivity: tools for all your basic web development needs
- raw performance
"Automatic server rendering and code splitting" is the top reason why over 9 developers like Next.js, while over 5 developers mention "Haskell" as the leading cause for choosing Yesod.
Next.js and Yesod are both open source tools. It seems that Next.js with 38.7K GitHub stars and 4.69K forks on GitHub has more adoption than Yesod with 2.11K GitHub stars and 329 GitHub forks.
CircleCI, Avocode, and OverCode Solutions are some of the popular companies that use Next.js, whereas Yesod is used by DoxIQ, FP Complete, and SimplyRETS. Next.js has a broader approval, being mentioned in 82 company stacks & 69 developers stacks; compared to Yesod, which is listed in 5 company stacks and 5 developer stacks.
We choose Next.js for our React framework because it's very minimal and has a very organized file structure. Also, it offers key features like zero setups, automatic server rendering and code splitting, typescript support. Our app requires some loading time to process the video, server-side rendering will allow our website to display faster than client-side rending.
We’re a new startup so we need to be able to deliver quick changes as we find our product market fit. We’ve also got to ensure that we’re moving money safely, and keeping perfect records. The technologies we’ve chosen mix mature but well maintained frameworks like Django, with modern web-first and api-first front ends like GraphQL, NextJS, and Chakra. We use a little Golang sparingly in our backend to ensure that when we interact with financial services, we do so with statically compiled, strongly typed, and strictly limited and reviewed code.
You can read all about it in our linked blog post.
Next.js is probably the most enjoyable React framework our team could have picked. The development is an extremely smooth process, the file structure is beautiful and organized, and the speed is no joke. Our work with Next.js comes out much faster than if it was built on pure React or frameworks alike. We were previously developing all of our projects in Meteor before making the switch. We left Meteor due to the slow compiler and website speed. We deploy all of our Next.js projects on Vercel.
Hey guys,
My backend set up is Prisma / GraphQL-Yoga at the moment, and I love it. It's so intuitive to learn and is really neat on the frontend too, however, there were a few gotchas when I was learning! Especially around understanding how it all pieces together (the stack). There isn't a great deal of information out there on exactly how to put into production my set up, which is a backend set up on a Digital Ocean droplet with Prisma/GraphQL Yoga in a Docker Container using Next & Apollo Client on the frontend somewhere else. It's such a niche subject, so I bet only a few hundred people have got a website with this stack in production. Anyway, I wrote a blog post to help those who might need help understanding it. Here it is, hope it helps!
Pros of Next.js
- Automatic server rendering and code splitting49
- Built with React43
- Easy setup33
- TypeScript26
- Universal JavaScript24
- Zero setup22
- Static site generator21
- Simple deployment12
- Just JavaScript12
- Incremental static regeneration12
- Filesystem as an API10
- Frictionless development10
- Everything is a function9
- Well Documented9
- Has many examples and integrations8
- Testing8
- Isomorphic React applications7
- File based routing + hooks built in4
- Deployment2
- SEO1
Pros of Yesod
- Haskell6
- Super High Performance4
- Open source3
- Type safe URLs2
Sign up to add or upvote prosMake informed product decisions
Cons of Next.js
- Structure is weak compared to Angular(2+)9