12
b2plane
149d

This is fucking mental. Nextjs is a fucking unoptimized piece of fucking trash framework. When i dont touch it for several days magically everything breaks and no longer works. What the FUCK is this garbage framework.

Also i just npm run dev after 3 days of not touching the project, when it started routing is fucking dead, freezes and loading forever, getting stuck at UI, checked activity monitor just to see this piece of fucking cum eat 330-390% of my fucking CPU

Powered by Shitcel

Nextjs unstable cum gargled bullshit garbage framework for script kiddies who think they know shit about programming but they're mindless retards who know nothing about security, jwt tokens or even devops infrastructure or IaC. Fucking useless overexaggerated trillions of dollars of marketing budget for Shitcel's framework called nextjs is not as good as the fake marketing campaign portrayed it to be. It was all a fabricated lie. A fascade. A hollywood shitshow. A faked moon landing type of framework. A fucking meme framework. Fucking pissed off for wasting my time learning it

Comments
  • 3
    here's the reproduction steps:

    1. work on a nextjs project, everything works fine
    2. don't touch the project for 3 days
    3. come back to the project after 3 days, make 0 changes and do `npm run dev`. everything is now broken, random errors, random 403, random freezing, routing no longer works, nextjs eats 330-390% of your CPU, infinite page load, 0 error logs in console
  • 1
    Yh, that's the thing, most devs knew this before trying.. C'mon, do vue.. Nothing to lose. It's really different. You'll learn in a few days. It's nothing like React what's not for winners anyway
  • 3
    @retoor i also knew it before trying. I thought i may be wrong but instead i was just affected by their extreme billion dollar marketing campaign to glorify that framework and overexaggerate its power
  • 0
    @retoor or Svelte. Especially Svelte 5.
  • 5
    Doesn't the "T" in JWT mean "tokens"? Why do people say "JWT tokens"?
  • 0
    Try with metalsmith.js:

    1. Work on metalsmith project, add the plugins you need and leave out anything you don´t.
    2. Leave alone for 5 years
    3. Come back after 5 years: it still works (as proven by nodejs.org until 2023 a.o.)

    Disclaimer: I maintain it.

    Commitment to stability, no framework lock-in, and yes you can combine it with any tools or framework of your choice
  • 0
    - Nuke .next folder
    - build project before running dev
    This might help.
  • 0
    @soberGhost turned out there was a conflict between server/client components that were nested within each other. Some server components had a nested client components and vice versa. This got cooked when the nav tried to be rendered using a static array variable in a server component instead of a client component. The icons were pulled from lucide react as Home and thats not possible to be rendered as a server component. So i had to change it into <Home /> to render the icons like that and then it worked even as a server component
  • 1
    @b2plane tough one. It''s a good thing you found a fix.
    But try to separate server comps from client ones.It will only give you headaches. At least don't use the "use client" directive if it's not required by a library or the component (when not usingi hooks) so you can import them anywhere needed.

    Next gave me plenty headaches the past 3 months.
  • 0
    @soberGhost there is no unversal or suggested rule or pattern to follow so im unsure how best practice looks like
  • 0
    @b2plane there might be something regarding that topic on the docs but am not sure.

    One way to go about it is to figure out the root cause and try to fix that

    If you only use server components to get some data (wether with serverProps or from a service) you can easily replace that with async requests for data fetching+ squelletons as placeholders and their is a way to get route props on client pages aswell on client components.

    If your app heavily rely on SSR for some reason and that's why you need server components buut you need hooks aswell then you're kinda royally fucked. You might need to review your whole architecture and decouple the different layers (in my POV).
  • 0
    @soberGhost the problem is next nextjs doesn’t have any design pattern architecture there such as MVC. Everything is arbitrary and when i asked experienced nextjs devs what architecture is supposed to be used they just reply use whatever you feel is best. This means ALL nextjs projects will have a different architecture and thats a giant clusterfuck.

    Also everyone recommends to use SSR components as much as possible due to impacting the best results for SEO
  • 0
    @b2plane try to refer to open source projects.
    Maybe Material-Kit-React from Devias io. It's a good starting point

    Regarding architecture, design patterns & most best practices, I believe they are "framework & language agnostic". They are proven solutions you have to implement yourself. They don't come bundled up with any tool as far as I know.
  • 0
    @dev0x01 even tho it doesn't happen in english that much, the same reason why people say atm machines.

    It's not our fault that the abbrevation includes the object and common people does not know the full meaning of the abb.
  • 1
    Write it in Rails 😉
Add Comment