My impression is that burn-in isn't nearly as much of an issue on newer panels as it once was. At least, I've been using the same OLED phone for 4 years and have no sign of burn-in yet.
My impression is that burn-in isn't nearly as much of an issue on newer panels as it once was. At least, I've been using the same OLED phone for 4 years and have no sign of burn-in yet.
Here's an interesting write-up about an attempt to develop a large-scale urban maglev system in the 1970s: https://en.wikipedia.org/wiki/Krauss-Maffei_Transurban
tl;dr: there were so many technical issues that when the West German company developing the tech lost funding and the Ontario government took over the project, they immediately abandoned the maglev concept and replaced it with linear-induction propulsion with steel wheels on rails (the mag, without the lev).
Even this tech, which does have a few advantages over conventional rail and is still used today in cities like Vancouver, is falling out of favour due to general logistical issues with using bespoke technology over conventional rail -- fewer people know how to build and maintain it, you're relying on usually just one company to supply your trains and infrastructure until the end of time, you can't reuse any existing infrastructure, etc. I'd imagine these issues still get in the way of maglev development today -- even more so because you can't even reuse existing rails
OneNote. Don't love being super reliant on all the Microsoft Office cloud stuff but there really isn't anything that comes close to what I use it for
Not really the same thing at all if there's no handwriting support.
Non integer display scaling will always look like crap.
No it won't, Windows has had this figured out for at least a decade
I use it for a mix of text, handwriting/drawing, PDF annotation and image annotation, and I also pretty heavily rely on realtime sync between my devices. If none of that is stuff you use then I can see why you might want something simpler
not as great as his dad vomiting on the prime minister of Japan though
I do this but it's a pain in the ass. They keep making it harder to access certain features without opening Android Studio (i.e. the AVD manager, logcat, app signing functionality, etc)
Also sometimes gradlew decides to just not build your project and you have to open Android Studio to get it to work. Why? No idea
I don't even use low power hardware, Android Studio just manages to be an incredible resource hog even on normal hardware
Yeah but if we all wrote "joules per second" instead of watts we'd encourage everyone to measure energy in joules instead of watt-hours. It's like speed, we don't need an entirely separate unit that just means m/s
Or just joules per second for power. Eliminate watts entirely. Dumbass unit