AssemblyLoadContext.Unload https://learn.microsoft.com/en-us/dotnet/api/system.runtime....
4,573 karma · joined September 7, 2015
Compile C# to a minimal RISC-V runtime. You run the program once, and instead of shipping all the outputs and logs, you generate a zk proof—a tiny math receipt that says "this execution was correct." Anyone can verify that receipt in milliseconds.
It's a bit like TEEs (Intel SGX, AMD SEV) where you outsource compute to someone else and rely on hardware to prove they ran it faithfully. The difference is zk proofs don’t depend on trusting special chips or vendors - it's just math.
Implications:
* Offload heavy workloads to untrusted machines but still verify correctness
* Lightweight sync and validation in distributed systems
* New trust models for cloud and datacenter compute
Ethereum has a Market Cap of $249Bn and $34bn of other assets in smart contracts.
So you could say .NET on Linux has under management $116Bn and handles $800m of asset transfers per day, napkin math
https://en.wikipedia.org/wiki/Betteridge%27s_law_of_headline...
Though the minimum redeemable amount is $100k https://tether.to/en/fees
Why they are depegging is people are selling for under a dollar on coinbase (perhaps in panic); and Alameda Research (re: FTX exchange) who normally makes a ton of money doing the arbitrage between dollars and tether is having liquidity problems, so not doing it currrently.
https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotne...
<RuntimeIdentifier>linux-x64</RuntimeIdentifier>
<PublishReadyToRun>true</PublishReadyToRun>
https://www.ageofascent.com/2018/01/26/stack-trace-for-excep...
> The reason was apparently that the database is managed in Excel and the number of columns had reached the maximum.
> The reason was apparently that the database is managed in Excel and the number of columns had reached the maximum.
Tools…Options -> Environment -> Preview Features -> “Show all .NET Core templates in the New Project dialog”
https://devblogs.microsoft.com/dotnet/net-cli-templates-in-v...
Go being only faster in one benchmark
> Although they were in common use, the terms "master" and "slave" do not appear anymore in current versions of the ATA specifications, or any current documentation. Since ATA-2 the two devices are referred to as "Device 0" and "Device 1", respectively. This is more appropriate since the two devices have always operated, since the earliest ATA specification, as equal peers on the cable, with neither having control or priority over the other.
> It is a common myth that the controller on the master drive assumes control over the slave drive, or that the master drive may claim priority of communication over the other device on the same ATA interface. In fact, the drivers in the host operating system perform the necessary arbitration and serialization, and each drive's onboard controller operates independently of the other.
> While it may have remained in colloquial use, the PC industry has not used ATA master/slave terminology in many years.