This is not true. They remove the downloaded and encrypted files (sure) but your library remains in your iCloud. And I have unsubscribed many times and came back, it gets your account synced with iCloud and everything comes back.
Wait until your bank proactively blocks your card because you used ATM where a skimmer was found, and then apple icloud monthly payment bounces... That is even more exciting!
Many moons ago I was preparing for an interview to join wasmer, back then they showed me that by running wasmer as a kernel extension in Linux they have made it run four orders of magnitude (10,000 times) faster. Given the WASI, I keep thinking more than the plugin usability of things like wasmer, what is the point of WASM not being accepted as a second binary in all operating systems? Windows could support .exe as well as .wasm for example and we would finally have a cross-plaform binary. Apple would never accept; Microsoft will do, and Linux can simply have,
Such speedup is not plausible at all. It had to be a flawed benchmark relying on some API being very slow in userspace (probably on purpose, not using it the right way). The raw execution speed of WASM can't change much just because it is in a kernel.
That's probable, though if we want to give them the benefit of the doubt, it could be a non-optimised benchmark, ie, something that may be written during the average devoper might ordinarily write, rather than hyper-optimised code specifically for that benchmark.
What they had done was wiring kernel level operations, without any of the userspace security checks into the wasmer. Their logic was that given the sandbox of wasmer; what would happen if you removed the sandbox of the OS? And I remember their article was featured in HN for two days or so as well. It was interesting. It wasn't that WASM ran faster than C, it was the API calls. And I keep wondering about an architecture where you have a highly sandboxed universal assembly with some API hardening; a middle ground, and so imagine an app that ran everywhere and was 10~100 times faster. Could be really cool.
Yes, it's not a new idea. See Microsoft Singularity research OS for a more recent example.
You would still have slower than native execution speed, security problems with Spectre attacks (in HW process isolation it's avoided by not having other memory mapped at all, other mitigations exist but they cost a lot of performance).
Syscall speedups affect only specific programs or stupidly written SW like some games that are checking current time many many times per frame.
It's not just syscalls. If you trust all of the running code, you can use a single address space for all applications and even the kernel, which lets you avoid TLB flushes.
Whether that's still a good idea given Spectre is another question.
What a truly beautiful simplex/meta-balls pattern in the website. The two layers of blue and one red within the blue is such a beautiful design. I spent so much time looking at it that I forgot to read the article.
Given how many times Trump declared the war a victory, I'm also curious to know if they declare it a war, how many time the families will be compensated? ten wars? a hundred wars? two wars and a a hundred rounds of ceasefire friendly matches?
This was an amazing read. I try to make hyper-documents as Nelson wanted and I have seen much of the contradictions. Yet I still believe you have to give people a hundred ideas for them to use 10. He did just that.
Exactly! I worked with a couple ex Xanadu acolytes at Apple back in the day. What they took away from the experience were the many inspirations rather than the project as a model for organizations. One of them brought him in to speak and he spent the time exhorting us to think beyond WYSIWIG (be careful about how your metaphors limit what your avoidances can be) which at the time I found rather eye-opening.
I'm so happy to see it be released. I had watched their YouTube coverage of what and why they were doing what they were doing and I'm so happy. As much as Audacity bears a nostalgia and mental safe zone in its look and design, it was too good of a software to let rot in technical debt and code spaghetti and getting behind. The world really needed an open source good looking easy to use workstation that is not as complicated as Pro Tools or Logic... I'm so thankful for Muse rescuing so many of the great apps (I really really am thankful for the MuseScore getting that amazing recently for example, or bringing the wonderful wonderful engine of StaffPad to it...)
reply