Nahasco
Explore posts from serversTTCTheo's Typesafe Cult
•Created by Nahasco on 6/16/2024 in #questions
Should I ditch Django for GO or full stack Next.js
Thank you for the great input @Juraj98 , I am convinced the t3 stack is the most productive and easiest to manage when solo working on a project, although it has its drawbacks. I will for sure give it a shot in my next projects.
But I am not sure if I should do it for my current project. The issue is that I see this project as a long term one and I wont stop working on it anytime soon. I am slowly leaning towards sticking with Django, maybe switching to Django ninja but with no certainty. I can't decide if it's worth it.
25 replies
TTCTheo's Typesafe Cult
•Created by Nahasco on 6/16/2024 in #questions
Should I ditch Django for GO or full stack Next.js
It is a personal project, yet it is big. I have been working on it for a while now and it has become quiet complicated. Migrating to anything will defienetly take a very long time to do. But I was thinking if Django as a rest api isnt a good solution then I better migrate now than later.
Learning a new language is not what I need either, it will make the migration process much harder and time consuming. I only know JS and Python.
Should I stay with Nextjs + Drf?
Or migrate to
Nextjs + Prisma
React + FastAPI + SQLAlchemy
React + Express + Prisma
25 replies
TTCTheo's Typesafe Cult
•Created by Nahasco on 6/16/2024 in #questions
Should I ditch Django for GO or full stack Next.js
Should I stay with Nextjs + Drf
or switch to Nextjs + Prisma or Nextjs + other backend
25 replies
TTCTheo's Typesafe Cult
•Created by Nahasco on 6/16/2024 in #questions
Should I ditch Django for GO or full stack Next.js
I am a junior and I am not sure what I am comfortable with yet.
For now I have been using NextJS + Django rest framework
It works but I am starting not to like Django, especially when I migrated to typescript in next. Types are just so nice.
I just am wondering if other backends are a better fit for me and my project.
25 replies
TTCTheo's Typesafe Cult
•Created by Nahasco on 6/16/2024 in #questions
Should I ditch Django for GO or full stack Next.js
25 replies
TTCTheo's Typesafe Cult
•Created by Nahasco on 6/16/2024 in #questions
Should I ditch Django for GO or full stack Next.js
But I am not just fetching data, the backend processes data. It reads and writes. Frontend can add students, teachers, classes, edit them or delete them. This is mostly what the app will do.
Receive input from managers, teachers about students and their daily class. Information about what the student recites and reads will be recorded.
I will them use the data to present it in different ways throughout the frontend and also create analytics and pdf reports.
25 replies
TTCTheo's Typesafe Cult
•Created by Nahasco on 6/16/2024 in #questions
Should I ditch Django for GO or full stack Next.js
Things in Django that I take for granted like it taking care of the database and providing a admin backend. Like I fear such things would take me ages to implement in other backends like Go.
25 replies
TTCTheo's Typesafe Cult
•Created by Nahasco on 6/16/2024 in #questions
Should I ditch Django for GO or full stack Next.js
I moved from react to nextjs because I liked how routing works in nextjs. It is simple and easy to work with. Thats the only reason I am using nextjs instead of react.
The application I am building is not that simple. It is a management system that will store, manipulate, and show alot of data.
I went with Django because it was what I learned in the course that got me into web development.
I did have some pain using it, more specifically type checking. Laos is having some very nice out if the box features I sometimes suffered from fully understanding whats exactly going on. Things just worked most of the time.
Some folks at a different server were incredibly negative about using Django and they shared and amplified my concerns with it.
Many suggested Go, aps.net, or any other backend but django or basically python.
I was honestly upset that if I decide to switch backends Ill have to spend tens of hours migrating to a new backend.
However if other backends are really a better fit for me and my project then I would put the effort and time in migrating.
Then I have the issue in deciding which backend I should migrate to.
I really am convinced Next.js backend isn't a good idea. Coupling frontend and backend isn't very advised in what I have read so far. And I like the idea of having separate frontend and backend. I like the flexibility and conveniance of being able to easily connect different frontends like a web app and mobile app to the same backend or the benefit of being able to change backend and frontends easily.
In this case what separate backends should I migrate to?
My first impression on Go is that its a language, not a web framework, and Ill have to write and learn shitload of code to make it work as a web framework.
I am just so confused and lost now and need some guidance.
25 replies