I'd like to read the accounts of contemporary curmudgeons bemoaning the way young Greeks are clamoring for mom's mirror, and how you should limit your kids to no more than one twelfth of a day of mirror time, setting the clepsydra if necessary.
Yeah, for sure! I mean, Narcissus is in the public consciousness there to back up your idea.
It's an interesting idea: that a piece of tech can represent one thing and have certain moral sensibilities that form around it, and then some innovation or something changes our relationship with it (in this case, puts it on a wall in every bathroom).
Maybe it changed us in ways we can't fully know! Maybe commoditizing the mirror largely robbed it of its power. Or maybe we're all a bunch of narcissists in ways we can't comprehend because we don't have the anti-mirror people out there scolding us.
Hey, with the appropriate overclock, that could be audiophile-grade [0]! I want to see an appliance that takes DSD input and uses it to drive a 2.8224 MHz musical Tesla coil.
This reminded me of a Kurzgesagt video from a few months ago on the same topic [0]. I see that the author, Karen Lloyd, was one of the experts they consulted when making that video.
Thank for finding that, yes that's the one. It was incredibly accurate.
I'm in two minds about the fact it's down.
1. It's probably a good thing that it isn't super-easy to quickly find everyone's alternate accounts.
2. The capability is clearly there and the technology is out there, but now in the hands of the few people who bother to re-implement it.
It was a useful tool for highlighting the naivety of believing that throwaway accounts were a real possibility when stylometry analysis is so relatively cheap to do.
Can they eventually throw away Android and replace it with Fuchsia? In the reporting about Fuchsia that I read ages ago, it sounded like it was intended to be an Android replacement but, looking into it again just now, it seems more like an embedded OS for other non-smartphone hardware -- maybe with some (aspirational?) claims of utility on smartphones and tablets.
Fuchsia has components for running APKs (Android Runner) and Linux binaries (Starnix), but that probably isn't what you meant.
The problem with replacing a UI toolkit - any toolkit - is that any change to the toolkit requires modification of all software, including third-party software. Typically, when an OS wants to provide a new toolkit, they wrap the existing toolkit in new code. For example, on macOS, UIKit wraps AppKit, and on all Apple platforms SwiftUI is a wrapper around AppKit and UIKit (depending on platform). On Windows, every UI toolkit ultimately is creating "windows" as they are understood by USER[0], which creates corresponding objects in CSRSS and/or the NT kernel, which can then be used to draw on or attach to a GPU. The lowest level UI abstraction either OS provides is the objects supported by their oldest toolkit, and the lowest level programming language you can write apps in is whatever can call it.
Linux is a bit different, because it inherits its windowing model from X11. X shipped with no default toolkit and a stable window server protocol that apps could program against directly, in an era where most GUI OSes[1] didn't have 'servers' or 'protocols'. You populated resource files and called the relevant function calls to make things happen, and those function calls became sacrosanct. Even Windows NT couldn't escape this; it still used USER despite USER being years older than NT.
The best you can do is shim the library - write something more lower level than the old junk and then rewrite the old library in terms of the new one. This is what Xwayland does to make X apps work on Wayland; and it's what Apple did (mostly) with Carbon to give a transition path to Mac OS 8/9 apps on OS X. Google could, say, ship a new Android toolkit that doesn't use Java bindings, and then make Android's Java toolkit a shim to the new native toolkit. However, this still means you have to keep the shim around forever, at least unless you want to start having flag dates and cut-offs. For context, Apple didn't kill Carbon until macOS 10.15 Catalina, and if they hadn't refused to ship Carbon on 64-bit Intel, it probably would still be in macOS today.
[0] An interesting consequence of this is that disabling "legacy input" in games turns off the ability to move the application window since all that code is intimately coupled to every app that has to open a top-level (i.e. not a widget) window.
[1] At the time that would be XEROX Star, the Lisa, and the Macintosh
[2] This is also why Apple will never, ever ship an iPad that can run macOS software in any capacity. Even if they were forced to allow root access and everything else macOS can do. The entire point of the iPad is to force software developers to rewrite their apps for touch, and I suspect their original intent was for the Macintosh to go away like the Apple ][ did.
Correct, tl;dr roadkill. I don't mean to be disrespectful, someone anonymous picked a bitter fight about this once. But to your point, its clear there was a larger context that Fuchsia was born from, and the ambitions and commitment to it are greatly different than they were at some previous juncture.
It sounds like GP would benefit from satellite internet bypassing the firewall, but I don't know how hard the Chinese government works to crack down on that loophole.
In the US, HIPAA grants you the right to access your own health information [0]. I recommend asking providers to burn the DICOMs to a DVD (or send your images to you via an online portal, if they and you prefer) whenever you have medical imaging done.
For anyone wanting a better image of the "Modern model of the Lehmer Bicycle Chain Sieve" than what is embedded in TFA, it can be seen on page #4 of the Spring 1983 Computer Museum report (which is also a PDF):
> there is a pretty famous former M$ performance engineer who worked on Xbox and bunch of other large projects, he has webpage about how he tracks down bugs and performance issues, don't it have it handy unfortunately.
