[GH-ISSUE #51] Question: vinext vs rari #17

New issue

Closed

opened 2026-05-06 12:36:31 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-06 12:36:31 +02:00

Owner

Originally created by @XavierGeerinck on GitHub (Feb 25, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/51

I'd like to start off by saying "AMAZING JOB". Really happy to see someone tackling the nextjs issues that have been around for ages

While working through this repo, I couldn't stop wondering the question "Why work on a re-shim and not a deeper implementation such as Rari".

This is personally more out of curiosity asa my current experience with Next.js is "SLOW", so would love to see either vinext or rari become a good replacement offering.

Originally created by @XavierGeerinck on GitHub (Feb 25, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/51 I'd like to start off by saying "AMAZING JOB". Really happy to see someone tackling the nextjs issues that have been around for ages While working through this repo, I couldn't stop wondering the question "Why work on a re-shim and not a deeper implementation such as [Rari](https://github.com/rari-build/rari)". This is personally more out of curiosity asa my current experience with Next.js is "SLOW", so would love to see either `vinext` or `rari` become a good replacement offering.

BreizhHardware closed this issue

2026-05-06 12:36:31 +02:00

BreizhHardware commented

2026-05-06 12:36:32 +02:00

Author

Owner

@mktcz commented on GitHub (Feb 25, 2026):

I think that is not a feasible path in workers runtime.

@mktcz commented on GitHub (Feb 25, 2026): I think that is not a feasible path in workers runtime.

BreizhHardware commented

2026-05-06 12:36:32 +02:00

Author

Owner

@southpolesteve commented on GitHub (Feb 25, 2026):

Thanks for the kind words and for flagging Rari. This is actually the first I've heard of the project. Just took a look. Pretty neat, and genuinely cool to see other people working on similar problems.

I'd say there's plenty of room for multiple implementations here. Honestly more than one is a good thing. It means we can validate that we're standardizing around the right behavior rather than just enshrining one-off bugs.

As for why we didn't go the Rari route, it wasn't really an explicit decision not to do a deeper implementation. It just wasn't something I considered. This started as a Friday night idea a week ago. I'm a JavaScript developer by background, I'm a big fan of Vite, and I knew from our experience using it with other frameworks that it'd be a solid foundation. So that's where I started.

@mktcz I haven't looked deeply enough into Rari to say for sure, but Workers does support Rust via workers-rs. So it's definitely feasible in principle, though I'm sure there'd be a lot of details to sort out.

@southpolesteve commented on GitHub (Feb 25, 2026): Thanks for the kind words and for flagging Rari. This is actually the first I've heard of the project. Just took a look. Pretty neat, and genuinely cool to see other people working on similar problems. I'd say there's plenty of room for multiple implementations here. Honestly more than one is a good thing. It means we can validate that we're standardizing around the right behavior rather than just enshrining one-off bugs. As for why we didn't go the Rari route, it wasn't really an explicit decision not to do a deeper implementation. It just wasn't something I considered. This started as a Friday night idea a week ago. I'm a JavaScript developer by background, I'm a big fan of Vite, and I knew from our experience using it with other frameworks that it'd be a solid foundation. So that's where I started. @mktcz I haven't looked deeply enough into Rari to say for sure, but Workers does support Rust via [workers-rs](https://github.com/cloudflare/workers-rs). So it's definitely feasible in principle, though I'm sure there'd be a lot of details to sort out.

BreizhHardware referenced this issue

2026-05-06 12:38:45 +02:00

[PR #17] [MERGED] v0.0.4 #246