Python has that property when you don't bring C extensions into the conversation. Data races exist, but can never cause memory corruption due to the GIL.
Usually people are talking about race conditions. When you say contrived you're thinking races conditions are difficult to win and unrealistic but attackers who have a lot of money on the line spend the time to win all sorts of wild race conditions consistently.
I've played with something similar with my M1 using Apple's MLX framework. The problem is I'm compute bound. I've never managed to get my M1 Max's GPU to process more than ~7.8k tokens per second at bf16 precision, so to train a 112M parameter model on ~20 billion tokens I'd need to run the model training for ~30 days.
One solution is to reduce the scope of the problem -- you can train on a smaller less diverse dataset such as TinyStories which is a collection of 1 billion tokens of chatGPT generated children's stories. After about 40 hours, less than one weekend, you'll have a model which can generate mostly grammatical children's stories.
If you have a newer mac and/or an ultra chip you'll have more and faster GPU cores, and might be able to train on FineWeb or a similar, larger and more diverse dataset.
I could be mistaken, but I think the mac studio comes with either an M3 ultra or an M4 max, and the ipad comes with an M4 chip. I think they decided not to make an ultra for the M4 generation, but don't take my word for it.
I think the audio quality gives this recording character. What could be more cyberpunk than hearing the quirky artifacts resulting from ripping an obsolete recording medium?
What happened? Microsoft used to have an army of testers who would do a mix of manual and automated testing to help ensure the quality of the product. In 2014 they were all fired. Their strategy for testing Windows is now three fold:
- Devs are expected to test their own code now
- There is now a program where customers can use beta builds of Win10 and report issues
- MS relies on telemetry to find and fix issues
Today there's lots of old code from the era before automated tests were widespread in the industry, and often automated tests which were previously maintained by the testers are now bitrotting. The culture of testing is not strong among developers in some parts of the company. The beta program can't catch everything either.
So telemetry it is.
And you need some telemetry. Minidumps/coredumps make debugging certain kinds of crashes much easier, and Apple captures that sort of data too. And I guess seeing whether people use some widget in Office a lot/not at all could be useful for improving the product. In practice it also leads to issues with the GDPR and governments, which MS does ultimately fix.
Apparently Win10 Enterprise users have a switch somewhere where they can turn off almost all telemetry, but not so for Home and Pro users, say what you will about that.
