Having RCEs in general is fine. It's the rate and severity that matter.
We have evidence that large unsafe codebases suffer from more and more severe CVEs than those who are not in memory unsafe languages.
In other fields of engineering, people use stats and actually measure things like this, and use the results to determine what to do. They don't just assume something is better because its "battle tested" (whatever that even means?).
No, with TRAMP its a one way thing. The remote side can't wander around the local side at all, at least from my understanding of TRAMP. So it's no the same at all.
Wait, you mean that with the VS Code protocol, the remote side can send the commands to my local VS Code, making it do all kinds of funny stuff? Seriously? That's not really obvious from TFA at all and mostly reads as their unease with running somewhat opaque piece of software at the remote written for Node instead of presumably well-maintained bunch of sh scripts (a very interesting supposition IMHO).
The IPhone runs on a battery, with no active cooling.
There is no chance the sustained single core perf is better than a 150=200+w ryzen with a big noctua cooler on it. The power draw alone would kill the battery in a few minutes(?), and the heat would make it catch fire. lol
I don't think you are correct for single-core performance.
A20 Pro scores around 4725 at 8.9w. Geekerwan's review showed that the iPhone 18 pro could dissipate as much as 6.4w during long gaming tests. Cutting power by 50% likely still keeps around 80% of the clockspeed.
As 9950x scores around 3400-3450 in geekbench, or around 28% slower.
There's a very good chance that the iPhone single thread performance is genuinely faster even during sustained loads.
Sustained performance is usually based on cooling, not the chip. There is no reason the iPhone chip can't sustain its performance if you give it a small fan.
So whatever your argument is, it doesn't make much sense.
The M6 is based on A20 Pro and it sustains its performance in a Mac Mini indefinitely - likely longer than Ryzens.
The 9800X3D doesn't pull anywhere near that much in single threaded workloads, it'd fry the core. It's also way less efficient than the iPhone CPU design and on an older and less efficient semiconductor process from TSMC.
You can’t allocate collections without nightly or without reimplementing them in the library. Every implementation uses it’s own set of trade offs to provide safety in unsafe implementation.
We have evidence that large unsafe codebases suffer from more and more severe CVEs than those who are not in memory unsafe languages.
In other fields of engineering, people use stats and actually measure things like this, and use the results to determine what to do. They don't just assume something is better because its "battle tested" (whatever that even means?).
reply