Next.js is infuriating

Posted by Bogdanp 9/2/2025

Next.js is infuriating(blog.meca.sh)

1029 points | 579 commentspage 8

chasd00 9/2/2025|

Reading the comments here is pretty funny, this time last year NextJS was the greatest thing ever.

rubenvanwyk 9/2/2025|

Reality is catching up.

dzonga 9/2/2025||

remember a while back when they was "rails is a ghetto" piece.

now that rather seems sane compared to next.js stuff n other javascript things.

if you gotta use typescript while not use java and at least benefit from the ecosystem of the jvm ?

for me I will stick with Rails - that's what I know

QuadrupleA 9/2/2025||

Every time I hear about modern JS/TS frameworks, I'm amazed at the unnecessary complexity.

In python / bottle.py this would just be a print statement to stderr in before_request() or before_response(). One additional LOC.

butlike 9/2/2025||

> Scientists discover a new super massive black hole at https://github.com/vercel/next.js/issues

got me good

nurettin 7 hours ago|

I loved it!

dumbledoren 9/3/2025||

The real question is how the hell some circles were able to push such complexity onto mainstream tech and what will it take to prevent it from happening again.

ddanieltan 9/2/2025||

A bit of a tangent, but how do you implement the feature when I highlight text on this blog, I get an option to generate a unique link directly to what I highlighted?

OtherShrezzing 9/2/2025|

Each paragraph/element has a unique ID, starting at 0, incrementing by 1. You originally land at the page https://blog.meca.sh/3lxoty3shjc2z . When you create a link, you're linking instead to a different page at https://blog.meca.sh/3lxoty3shjc2z/l-quote/64_25-65_174#64 . The format of the extra link metadata is `64_25-65_174#64`, which means:

- Start the highlight on the 64th element/paragraph. Inside of that paragraph, start from the 25th character.

- End the highlight on the 65th element. Inside of that element, end at the 174th character.

- Scroll the user to element #64 on page load.

They've then got some code on the page to add a highlighted span starting and ending at those points.

If the site maintainer is here: For me, the links are currently broken, as they should link to https://blog.meca.sh/3lxoty3shjc2z/l-quote/64_25-65_174#64, but currently link to https://blog.meca.sh/3lxoty3shjc2z/l-quote/64_25-65_174#64_2..., and `64_25` isn't a valid id on page-load.

dminik 9/2/2025|||

Ok, I think I can reproduce it by starting the selection from the end of the previous line.

I've reported the issue here: https://github.com/hyperlink-academy/leaflet/issues/196

dminik 9/2/2025|||

The blog itself is build on leaflet.pub.

I'll take a look and file an issue.

dakiol 9/2/2025||

My conclusion is to use nextjs only for very simple projects. Problem is that simple projects grow and become important ones. So, just dont use nextjs at all.

maelito 9/2/2025|

I have no major problem with Next running on Dokploy. I don't use lots of its functionnalities, just some SPA routes and dôme RSC routes.

That's fine. It works fine.

More comments...