Fullstack Frameworks aren't worth it

Hey,

I've been burned too many times by fullstack frameworks, and I just need to get this off my chest. Here’s why they don’t work out for me:

1. Frontend Frustrations: These frameworks usually stick to basic HTML templates, and making even simple CRUD functionalities work is a huge pain. (Laravel, Django)

2. Locked In: Once you pick a framework, you’re stuck with it. It’s like being in a relationship that you can’t get out of.

3. Team Nightmares: Working with a team on these projects sucks because there’s no clear division of work, and it gets messy fast.

4. External Dependencies: Need authentication? You’ll have to look outside the framework, and it just adds more complexity. (Next.js)

5. Feature Imbalance: I’ve yet to find one that’s great for both frontend and backend. They always compromise on one side. (Laravel, Next.js)

6. Scaling Woes: Scaling and keeping things organized becomes a real headache. (Django)

7. Mobile App Hassles: If the client wants a mobile app, you’re out of luck. You can’t just serve HTML to mobile apps, so you end up building APIs separately.

8. Performance Pains: Dreaming of a fast app? Keep dreaming, because fullstack frameworks rarely hit the mark. (Django, Laravel)

9. Stunted Learning: You don’t get to learn much because these frameworks do so much for you, leaving you with little growth.

In the end, splitting up frontend and backend is way better. It’s more manageable, scalable, and just works better overall. Just my two cents based on way too many regrets!