GC is such a mistake though, you don't have to use rust but to never have to think about memory is a disservice to the programmer. Because that is something you always should do, and if you do then GC is nothing but a hindrance.
Needs to be logged in, so not exactly user friendly. But made me happy, I was afraid I might have to do updates again now I can continue life not being bothered by windows update.
It will try to do that yes, but there are consequences, drawbacks and imperfections.
You can only cheaply do so with free blocks, and if 70% is occupied you can only spread it out over the remaining 30%. After you've done that for a while you'll have to rearrange existing data which incurs more writes and less performance. And fragmentation is still an issue.
There are tons of tradeoffs - which will be better or worse for different workloads. But to assume that it wear perfectly, which most people seem to do because it is easy, isn't particularly realistic.
These tests are quite misleading as they typically (didn't find any details) just go through the entire drive writing to it evenly. Which, to be fair is probably not that bad of a test unless you have intimate knowledge about how the controller operates.
But it means that every single cell gets even use and there are no write amplification and it doesn't expose controller or usage characteristics.
Depending on use it will most likely fail way earlier under more normal conditions. Not saying that filling a drive time and time again is completely abnormal, but it the nicest thing you can do to an ssd in many aspects.
1) Lots of desktop displays provide picture and high power, but very few laptops (and rarely even desktops) can provide any significant power from their ports (can be done of course but it is a cost thing).
2) I'd say yes (if the iphone supports it). Biggest caveat in my mind is whether the iphone allows enough current to drive the display.
3) Doubt it.
4) That is how these normally work, I don't know but that would be my expectation.
The best feature of flash was that it was so easy to disable. Because 99% of the use was annoying ads that pinned your cpu at 100%.
And that was Jobs argument, that it was too resource intensive. Predictably though, now that annoying crap moved to "newer" tech (javascript) and now we can't disable it as easily or without as little consequence. Just as resource intensive though...
But you still have to think about memory in those languages.