open source medical devices is a tricky thing. medical devices are heavily regulated for a reason. what individual in their right mind would contribute to a medical device software that has huge liability risk if people are injured or killed?
It is awesome! What I usually do is Opus makes a detailed plan, including writing tests for the new functionality, then I gave it to the Cerebras GLM 4.6 to implement it. If unsure give it to Opus for review.
Where they differ also from Apple, and indeed is insanely amazing for a network hw company is that I'm still getting software updates for my , I don't know, at least 7 years old AP. A consumer device.
The vulnerable code exists inside of the React Flight wire protocol that is used by Next.js but also Vite, Parcel, Waku and any other custom RSC implementation that exists. Your comment was accurate circa 2019 but not since React released server components.
You're wrong, but this is one of the unsettling things about the vulnerability and what React has become. Intuitively, you'd think a view library can't have RCE vulnerabilities like this. But that's not what React is anymore.
The Next.js server runs React modules. While one may argue that Next.js shouldn't bundle vulnerable dependencies, React does have modules for server-side runtimes these days and should be accountable.
reply