Research next.js vs express.js and decide which to use

[jxz12]

next.js makes deployments easier, but may be difficult to learn a new framework.

[AnnaFYZ]

Cons

• Requires an in-house development team to handle development and management.
• Avails a few plugins
• Developers need to create the complete front-end layer since Next.js does not include the installed front end pages. This elevates the cost of flexibility.
• Does not have a built-in state manager. You need to use state containers like Redux or MobX.
• Longer development time since it supports static web development

[jxz12]

I found a nice tutorial here, see what you think! https://www.freecodecamp.org/news/build-a-full-stack-application-with-nextjs/

[AnnaFYZ]

I think this part "To get started with this tutorial, I highly recommend using the provided starter boilerplate https://github.com/Yazdun/next-fcc-familyguy/tree/starter that I specifically created for this tutorial. It saves your valuable time by already including the necessary dependencies and folder structure, eliminating the need to set up your project from scratch." tells us already where we're going to stack. Setting up from scratch a thing we don't have an experience with will take a huge amount of time

пн, 13 лист. 2023 р., 22:27 користувач Jonathan Zheng < @.***> пише:

I found a nice tutorial here, see what you think!

https://www.freecodecamp.org/news/build-a-full-stack-application-with-nextjs/

— Reply to this email directly, view it on GitHub https://github.com/This-team-CFY/classplanner/issues/8#issuecomment-1809235767, or unsubscribe https://github.com/notifications/unsubscribe-auth/A265WNSHIPEOOIQQCP4W5I3YEKNG3AVCNFSM6AAAAAA7HJ6ZXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBZGIZTKNZWG4 . You are receiving this because you commented.Message ID: @.***>

[jxz12]

I agree in general that we should just stick with express.js for now. Another benefit of express.js is that you get practice calling endpoints from the UI which is probably good experience anyway.