News for hackers. Stuff that matters.

A comment on RCE Vulnerability in React and Next.js. Parent comment

Re:RCE Vulnerability in React and Next.js by halflife on Wednesday December 03, 2025 @04:50PM (#46140678)
Well, the official statement is that 1 and 2 are 2 different frameworks. That’s why they were later named to angular JS and angular, to avoid confusion.

The migration path between angular 1 and 2 is the same as react and angular, it’s just glue holding 2 frameworks together

And that change happened 10 years ago

[ Parent | on HN ]
Re:RCE Vulnerability in React and Next.js by azangru on Wednesday December 03, 2025 @07:02PM (#46142037)
> That’s why they were later named to angular JS and angular, to avoid confusion.

Angular.js and angular. That's not confusing at all :-)

[ Parent | on HN ]
Re:RCE Vulnerability in React and Next.js by sysguest on Thursday December 04, 2025 @03:55AM (#46145313)
this -- even google search results were mixed up

should be more different: eg "rect-angular vs angular"

[ Parent | on HN ]
Re:RCE Vulnerability in React and Next.js by yearolinuxdsktp on Wednesday December 03, 2025 @06:44PM (#46141876)
Easy migration was promised but never delivered. Angular 2 was still full of boilerplate. “Migrating” an AngularJS project to Angular 2 is as much work as porting it to React or anything else.

So yes, people got burnt (when we were told that there will be a migration path), and I will never rely on another Google-backed UI framework.

[ Parent | on HN ]
Re:RCE Vulnerability in React and Next.js by azangru on Wednesday December 03, 2025 @07:05PM (#46142065)
> I will never rely on another Google-backed UI framework.

Lit is pretty good :-) Though it was never positioned as a framework. And it recently was liberated from google.

[ Parent | on HN ]