Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

React 19 Breaks Async Composability

github.com

Post reply on HN
Print view View original

101–110 of 114 posts

Re: React 19 Breaks Async Composability

#101

Post by [deleted] »

yencabulator wrote: post #96
azemetre wrote: post #95

Earlier quoted context omitted.

Yes but the issue is that Vercel has all the core Svelte maintainers on their payroll too. My Q is why would we expect Vercel to not interject as well? I mean we have evidence they did this in one community library, why not another? That is the risk.

Svelte has a pretty prominent BDFL, having to corrupt him first might be enough. Personally, I think the moment SvelteKit stops working on plain container images & Cloudflare Workers is the moment Svelte dies.

[deleted]

Re: React 19 Breaks Async Composability

#102

Post by meiraleal »

yencabulator wrote: post #96
azemetre wrote: post #95

Earlier quoted context omitted.

Yes but the issue is that Vercel has all the core Svelte maintainers on their payroll too. My Q is why would we expect Vercel to not interject as well? I mean we have evidence they did this in one community library, why not another? That is the risk.

Svelte has a pretty prominent BDFL, having to corrupt him first might be enough. Personally, I think the moment SvelteKit stops working on plain container images & Cloudflare Workers is the moment Svelte dies.

> Svelte has a pretty prominent BDFL, having to corrupt him first might be enough.

I don't know him personally, but the power dynamics is clear: one person vs a corporation is often just one attractive offer away from significant changes

Re: React 19 Breaks Async Composability

#103

Post by yencabulator »

rich_harris wrote: post #100
yencabulator wrote: post #96

Earlier quoted context omitted.

Svelte has a pretty prominent BDFL, having to corrupt him first might be enough. Personally, I think the moment SvelteKit stops working on plain container images & Cloudflare Workers is the moment Svelte dies.

This simply isn't going to happen.

Just in case it wasn't clear: I mean this might be enough to prevent bad things from happening.

Re: React 19 Breaks Async Composability

#104

Post by rich_harris »

yencabulator wrote: post #103
rich_harris wrote: post #100

Earlier quoted context omitted.

This simply isn't going to happen.

Just in case it wasn't clear: I mean this might be enough to prevent bad things from happening.

For sure — just wanted to be totally explicit that SvelteKit will always be platform agnostic

Re: React 19 Breaks Async Composability

#105

Post by JakaJancar »

magnio wrote: post #32
JakaJancar wrote: post #11

Earlier quoted context omitted.

I've adopted the practice of avoiding libraries with major version > ~3. If you needed to re-design your API so many times, I don't trust your judgement enough to build on top of it. That said, I still use React and... it's at 19.x :'(

React jumped from v0.14 to v15.0, so in reality it's more like major version 4.3 right now.

Ah, cool, didn't know - joined the train late.

Re: React 19 Breaks Async Composability

#106

Post by creshal »

thibaut_barrere wrote: post #84
creshal wrote: post #37

Earlier quoted context omitted.

PHP devs meanwhile: You guys churn? For better or worse, you can take 10+ years old PHP code and it'll mostly just work.

The backward incompatibility story https://www.php.net/manual/en/migration70.incompatible.php is not empty

That was in 2015, and it barely impacted anything I touched. So, granted, technically not quite 10+ years, but you get worse churn in JS frameworks over an 8 months period. (Unless it's jquery.)

Re: React 19 Breaks Async Composability

#107

Post by icpmacdo »

rich_harris wrote: post #100
yencabulator wrote: post #96

Earlier quoted context omitted.

Svelte has a pretty prominent BDFL, having to corrupt him first might be enough. Personally, I think the moment SvelteKit stops working on plain container images & Cloudflare Workers is the moment Svelte dies.

This simply isn't going to happen.

Thanks for the work you put into the Svelte platform, competition helps keep ecosystems more honest

Re: React 19 Breaks Async Composability

#108

Post by harrisi »

danfritz wrote: post #53

Ha great we finally arrive at the "Next.js React features" which basically forces everyone to use Next.js or an additional framework on top of React which now have to play catchup with whatever react - next.js think is "best" (for Vercels wallet). Expected outcome if half or the react core team is a Vercel employee. Kinda new this day was coming, sad to see it actually happen

This is why I'm sad about Svelte core being maintained by Vercel employees as well. They have definitely positioned themselves well to be in control of a lot of modern web development and deployment, but it makes me not want to use Svelte, SvelteKit, React, or Next.

Vue is the only main independent framework that exists now, apart from jQuery.

Re: React 19 Breaks Async Composability

#109

Post by sebazzz »

wordofx wrote: post #29
anonzzzies wrote: post #26

Terrible shitshow. Web dev is all broken and horrible. Well at least the popular stuff is. No idea why anyone uses this outside resume building.

HTMX is the way forward.

If you want to reduce maintenance costs, yes. Javascript is a shitshow of constant breaking changes left and right, whether it is in your runtime framework, or your build system like gulp or more prominently webpack. Try maintaining 10 projects with these frameworks. You'll quickly look for something that is not as maintenance intensive.

No, you can't stay on Webpack version X, because (real example) it turned out that version of webpack relied on md5 which wouldn't work in newer node.js versions.

Post reply on HN