frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Start all of your commands with a comma

https://rhodesmill.org/brandon/2009/commands-with-comma/
143•theblazehen•2d ago•42 comments

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
668•klaussilveira•14h ago•202 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
949•xnx•19h ago•551 comments

How we made geo joins 400× faster with H3 indexes

https://floedb.ai/blog/how-we-made-geo-joins-400-faster-with-h3-indexes
122•matheusalmeida•2d ago•33 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

https://arcadeblogger.com/2026/02/02/unseen-footage-of-atari-battlezone-cabinet-production/
53•videotopia•4d ago•2 comments

Jeffrey Snover: "Welcome to the Room"

https://www.jsnover.com/blog/2026/02/01/welcome-to-the-room/
17•kaonwarb•3d ago•19 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
229•isitcontent•14h ago•25 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
28•jesperordrup•4h ago•16 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
223•dmpetrov•14h ago•117 comments

Show HN: I spent 4 years building a UI design tool with only the features I use

https://vecti.com
330•vecti•16h ago•143 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
494•todsacerdoti•22h ago•243 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
381•ostacke•20h ago•95 comments

Microsoft open-sources LiteBox, a security-focused library OS

https://github.com/microsoft/litebox
359•aktau•20h ago•181 comments

Show HN: If you lose your memory, how to regain access to your computer?

https://eljojo.github.io/rememory/
288•eljojo•17h ago•169 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
412•lstoll•20h ago•278 comments

PC Floppy Copy Protection: Vault Prolok

https://martypc.blogspot.com/2024/09/pc-floppy-copy-protection-vault-prolok.html
63•kmm•5d ago•6 comments

Was Benoit Mandelbrot a hedgehog or a fox?

https://arxiv.org/abs/2602.01122
19•bikenaga•3d ago•4 comments

Dark Alley Mathematics

https://blog.szczepan.org/blog/three-points/
90•quibono•4d ago•21 comments

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
256•i5heu•17h ago•196 comments

Delimited Continuations vs. Lwt for Threads

https://mirageos.org/blog/delimcc-vs-lwt
32•romes•4d ago•3 comments

What Is Ruliology?

https://writings.stephenwolfram.com/2026/01/what-is-ruliology/
44•helloplanets•4d ago•42 comments

Where did all the starships go?

https://www.datawrapper.de/blog/science-fiction-decline
12•speckx•3d ago•5 comments

Introducing the Developer Knowledge API and MCP Server

https://developers.googleblog.com/introducing-the-developer-knowledge-api-and-mcp-server/
59•gfortaine•12h ago•25 comments

Female Asian Elephant Calf Born at the Smithsonian National Zoo

https://www.si.edu/newsdesk/releases/female-asian-elephant-calf-born-smithsonians-national-zoo-an...
33•gmays•9h ago•12 comments

I now assume that all ads on Apple news are scams

https://kirkville.com/i-now-assume-that-all-ads-on-apple-news-are-scams/
1066•cdrnsf•23h ago•446 comments

I spent 5 years in DevOps – Solutions engineering gave me what I was missing

https://infisical.com/blog/devops-to-solutions-engineering
150•vmatsiiako•19h ago•67 comments

Understanding Neural Network, Visually

https://visualrambling.space/neural-network/
288•surprisetalk•3d ago•43 comments

Why I Joined OpenAI

https://www.brendangregg.com/blog/2026-02-07/why-i-joined-openai.html
149•SerCe•10h ago•138 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
183•limoce•3d ago•98 comments

Show HN: R3forth, a ColorForth-inspired language with a tiny VM

https://github.com/phreda4/r3
73•phreda4•13h ago•14 comments
Open in hackernews

Next.js: The "Versatile" React Framework That Can't Handle Dynamic Routes

https://github.com/vercel/next.js/discussions/64660
17•batchfy•8mo ago

Comments

batchfy•8mo ago
Next.js claims to be a versatile React framework, yet it doesn’t support something as fundamental as dynamic routing in a single-page app. The issue was raised by one of their own developers—two years ago—and it's still unresolved. I genuinely don’t understand the hype. Everyone seems to be using Next.js, and the internet is flooded with tutorials like it’s the holy grail of React frameworks.
fixprix•8mo ago
Did you miss the comment where they said, "We’re still planning to address this within the next few months."?

Just because your niche issue isn't resolved, it is kind of a jerk move to blast them on HN especially when they've recently replied saying the issue is on their radar.

In less popular open source projects this is what drives devs to abandon them.

nhinck2•8mo ago
I love when these threads pop up.

It's fascinating to see people go nuclear over small issues and then take it public like everyone else should care.

sebmellen•8mo ago
I recently had to migrate a large project off of Next.js because of this issue. Have you tried TanStack Router? It is so many infinitely times better than Next.js for SPAs (and honestly most React use cases) that I can’t believe it’s not better known.

https://tanstack.com/router

nine_k•8mo ago
Vercel must be good at marketing. They are also good at offering Next.js hosting. They sustain that notion of Next.js being a natural choice.

Next.js offers some nice things as SSR and bundle slicing so that the initial load is (theoretically) way faster. There are other tools which do that, too. I personally find TanStack a more compelling "batteries included" proposition, despite its terrifying function signatures sometimes.

lolinder•8mo ago
This was your contribution to that thread last month [0]. Now a month after that insightful contribution you're on HN posting editorialized titles trying to get sympathy? Given your behavior in that thread I'm just impressed at how well the Vercel folks handled your aggression.

Maybe it's time to take your own advice and try a different framework instead of wasting time trashing on one you don't like.

[0] https://github.com/vercel/next.js/discussions/64660#discussi...

antisol•8mo ago
It seems someone hasn't been very thorough in their investigation.

Actually, this user has been posting in this thread for months - the earliest post I saw was in January. The user posted several times asking for updates as to whether this feature was planned or not, fairly politely it seems to me, and was totally ignored as far as I can see.

After repeatedly asking for updates and having no response whatsoever, it seems they became disillusioned. Which I think isn't unreasonable - it's my opinion that it's pretty rude for a maintainer to ignore reasonable questions put to them, and that it's quite reasonable to be offended when you are ignored in this way. You talk about "aggression", I say ignoring people is an act of aggression, and it seems to me that this user has simply responded in kind.

We could get into a discussion on whether a maintainer has any responsibility to respond to users asking questions, and then use that as a basis for deciding whether specific posts by this user were justified or not, but my point is that the picture you paint with your post is inaccurate and incomplete. At best.

lolinder•8mo ago
No, I was very thorough: I saw every comment and pulled out the obscene, aggressive, offensive acrostic embedded in months of harassing tagging of the target of that acrostic because that recent pattern of behavior overshadows everything else. There's no excuse for that entry no matter how frustrated they get.

Vercel owes them nothing—and the specific employee OP chose as a target owes them even less—and this entitled behavior is a long-standing plague on open source that needs to be called out and soundly condemned. If they need the feature so desperately they can add it themselves (Vercel already said it's something they want to implement!) or switch frameworks.

jemiluv8•8mo ago
This has been a plague for so long it nearly threatened the rails project. It also inspired a very interesting article https://dhh.dk/2012/rails-is-omakase.html about the maintainer that provides a framework of sorts for thinking about issues regarding open source entitlement
lolinder•8mo ago
Thanks, I hadn't read that before and it's a great piece!

> If most things on the menu disgust you, what on earth are you still doing at the table? The door is right over there, try not to slam it on your way out.

antisol•8mo ago
Interesting, thanks for sharing.

...but did you notice how the entire scenario presented in this article is predicated on the person who made their suggestion actually getting a response?

"I'm sorry, but hotdogs don't really fit our sushi menu, and while you may not care for unagi, we picked it for a reason. But thanks for the suggestions!"

Totally reasonable response. Polite. Reasonable explanation. 10/10 response. Totally unreasonable to then start insisting that hot dogs be added.

The example scenario isn't "person asks the waiter for a hot dog; waiter just keeps walking past them, blanking them as if they don't even exist".

I would be curious to know why OP chose to post this today, 3 weeks after they said they were working on it. That's an interesting detail.

lolinder•8mo ago
> The example scenario isn't "person asks the waiter for a hot dog; waiter just keeps walking past them, blanking them as if they don't even exist".

First: that scenario is actually still just fine when the establishment is a soup kitchen. When the people providing the service are providing it for free funded entirely out of their own pocket then no user of the free service is entitled to anything, ever.

Second: that isn't an accurate description of what happened, as you should know because you read the thread in full. What actually happened is that a maintainer responded to the issue back in January with a soft timeline. OP began harassing that maintainer less than halfway through the provided timeline.

When they got ignored for just over a week (which is, again, entirely reasonable especially given that a timeline was already offered) OP proceeded to write not one but three "FUCKUJimmy" acrostics further harassing the maintainer who had provided the initial timeline.

Then, on May 9, which is well within the initial estimate, the maintainer provided an update saying that the timeline had to be pushed back. OP's reaction to that was to try to bring the project hate on HN.

In what universe is any of this behavior by OP acceptable?

antisol•8mo ago
> a maintainer responded to the issue back in January with a soft timeline

It seems I missed that comment (https://github.com/vercel/next.js/discussions/64660#discussi...).

My apologies. There were a lot of comments.

I stand corrected, withdraw my support of OP's behaviour, and agree that it's not acceptable.

---

> no user of the service is entitled to anything, ever.

I say everyone is entitled to basic human decency and acknowledgement of their existence. I say that the waiter walking past and blanking them is rude and a dick move, and not "totally fine" at all. While you are correct that the user isn't entitled to the 10/10 polite response/explanation given in the article, they are entitled to some sort of basic human decency. The waiter blanking them and the waiter responding by calling them a cunt with no provocation are both aggression.

I also say that the "soup kitchen" analogy you gave doesn't really hold here - didn't you refer to that maintainer as "an employee"? So it's that person's job to respond to issues. Which entitles people asking them questions to a response. (Which, as I concede above, he did actually get)

But now we're debating philososophy, which I specifically didn't want to do. And I've conceded that in this instance your position on OP's behaviour is correct.

batchfy•8mo ago
The reason is that I don't think it's a technical issue — in other words, it's the managers, not the engineers, who decide the priority here. Therefore, the right place to try to expedite this is somewhere more influential, like HN or Twitter, not GitHub.

I can anticipate that this won't be resolved for at least 3 months. Just be aware this issue has been around for over 2 years, and the last time someone promised to fix it was 6 months ago. Let's see.

antisol•7mo ago
If you want to expedite development of the feature that you want, you could always a) do it yourself or b) pay someone else to.

There might be other people who are also interested in this feature who would also be willing to chip in to a bounty. You might consider a platform like https://algora.io/bounties or https://bountyboard.dev/bounties :)

jemmyw•8mo ago
Why not use something else then? I wrote my own router, when I outgrew that I wrote an extension to react router to do the extra thing I needed. Complaining about stuff never gets you far with software written by others.
tudorconstantin•8mo ago
Am I the only one thinking that going back full circle to server side rendering, but to a way more convoluted way of having it, is actually a regression rather than evolution technologically? We had SSR since the times of Perl, PHP, Python, Ruby and even express. But in a way more straight forward way of doing it: here’s some HTML, with some db queries that takes data, puts it in said HTML and sends it to the browser. Today we have react components that can be executed both on the server and on the client, we need at least 2 servers - one for the frontend and one for the backend, we have to hydrate the components when we render them server side, but not when rendering them in the browser, etc. I feel like we’re inventing stuff just because we can and there’s a huge cohort of engineers who complicate their development experience just because.
antisol•8mo ago
You are not the only one thinking this. A couple of years ago I was working with some people who were using next.js.

For some feature they wanted, they explained to me how nextjs has this great "feature", which was "really exciting" and allowed all kinds of fancy stuff that I've been doing since about 2003. They were going to turn on next's server-side rendering.

My immediate reaction was to point out "congratulations, you've just reinvented PHP, only with a much much worse language and two extra servers".

A lot of these "solutions" use three servers, not the two you mention: you use one server you don't have any control over, e.g google static hosting, to host the "compiled" static stuff - then you have that point at a server running node and another copy of all your terrible javascript, and then finally a third server running some more sensible stack, which could easily and more cleanly do the job of the other two using tech that isn't trash.

It's called "progress", and people like you and me just need to get with the times, it seems.

genatron•8mo ago
It has been full circle indeed. React is great for front-end development but with the need for having some pre-rendering (e.g. SEO) it's understandable why server-side re-entered the picture. However, with Next it has been slower build times and various twists and turns (a lot of the same things PHP was always bashed for). That's why for SPA apps we now default to Vite + react-router for a 10x speed up in build times on the same hardware.
mdhb•8mo ago
It’s primarily the react crowd specifically who have been off doing their own thing for many years at this point and never seem to look outside their ecosystem and are stuck in this bizarre infinite loop of just reinventing the wheel constantly, never really improving anything just chasing one new buzzword after another. It’s really unlike any other dev or engineering ecosystem I’ve ever seen in over 25 years.