C#/.NET being pushed hard running infrastructure at Ethereum's scale.
Nethermind runs on ~3k nodes and accounts for ~33% of staked nodes - supporting a ~$334B native asset, ~$146B of stablecoins and ~$54B deposited in DeFi apps.
Nethermind 2.0 has some amazing performance work in it: up to 2.55x block throughput, p99 block processing from 1.65s to 208ms, eth_call RPC 15-27% faster and Keccak-256 ~30% faster with platform intrinsics.
Nethermind Client 2.0.0 is out. It changes how the node stores Ethereum's state: archive nodes drop from ~30 TB to ~2 TB, you choose the history you keep, and blocks process 2–3× faster than the previous release on a fresh node.
Nine years since the first commit. The fastest execution software we've ever built.
Breaking changes; read the notes before upgrading. Release: https://t.co/vOBxwWLUAa
@rorysutherland Get a washing machine that has a tank that you fill up once every 30 washes with the two products, then you don't worry about it being in the cupboard anymore. Its the boiling water tap, air fryer of the washing machine world, once you have it you don't go back.
@Carnage4Life@neilquinn@stratechery MacOS has all but removed kernel level drivers since the M series processors. If you want to run in the kernel now you have to boot to an insecure mode, which no one does.
@ITStudiosi @MartinDotNet macOS 10.15 or later enables developers to extend the capabilities of macOS by installing and managing system extensions that run in user space rather than at the kernel level. By running in user space, system extensions increase the stability and security of macOS.
@m4rkchapman@allenholub I guess Apple took the "sue me then" approach to the anti-trust argument. But also with less MacOS penetration in the market its a harder anti-trust argument to make for MacOS.
@m4rkchapman@allenholub Actually Mac shut the walled garden on them running in the kernel around the time of the M1 roll out. Crowdstrike runs in user space with APIs on MacOS these days.
@ics_blitz@shuv1337 I truly find it weird that a product with such reach is just rolled out to everyone all at once, surely a phased approach for a product with such reach is the norm. It certainly is with OS patches etc. this seems to be a process issue totally disregarding the bug