In political science, the term polyarchy (poly "many", arkhe "rule") was used by Robert A. Dahl to describe a form of government in which power is invested in multiple people. It takes the form of neither a dictatorship nor a democracy. This form of government was first implemented in the United States and France and gradually adopted by other countries. Polyarchy is different from democracy, according to Dahl, because the fundamental democratic principle is "the continuing responsiveness of the government to the preferences of its citizens, considered as political equals" with unimpaired opportunities. A polyarchy is a form of government that has certain procedures that are necessary conditions for following the democratic principle. So yeah, you are right. A representative "democracy" is not a democracy. It's a monarchy with more than one ruler. A gummy bear is as much a bear as representative democracy is a democracy. I didn't know that, because i was taught in school that a representative "democracy" is a form of democracy. And the name makes it sound like one. But it isn't. It's not even supposed to be in theory. I am sure 99% of people living in a representative "democracy" don't know this. I hereby encourage everyone to abandon the word representative "democracy" in favor of polyarchy or maybe oligarchy. This makes it much clearer what we are talking about. Also i doubt the authors of this article know this, because they imply that representative "democracy" is desirable, but it is obviously undesirable.

I wonder if Microsoft will do a stock split in the future?

Does anyone know if there's additional sandboxing of local ports happening for apps running in Private Space? E: Checked myself. Can access servers in Private Space from non-Private Space browsers and vice versa. So Facebook installed in Private Space is no bueno. Even if the time to transfer data is limited since Private Space is running for short periods of time, it's likely enough to pass a token while browsing some sites.

Part of the reason for my use of "might".

In those situations I usually enable 1.5x.

Forgive me for not explaining better. Here are the terms potentially needing explanation. Provisioning in this case is initial system setup, the kind of stuff you would do manually after a fresh install, but usually implies a regimented and repeatable process. Virtual Machine (VM) snapshots are like a save state in a game, and are often used to reset a virtual machine to a particular known-working condition. Preboot Execution Environment (PXE, aka ‘network boot’) is a network adapter feature that lets you boot a physical machine from a hosted network image rather than the usual installation on locally attached storage. It’s probably tucked away in your BIOS settings, but many computers have the feature since it’s a common requirement in commercial deployments. As with the VM snapshot described above, a PXE image is typically a known-working state that resets on each boot. Non-virtualized means not using hardware virtualization, and I meant specifically not running inside a virtual machine. Local-only means without a network or just not booting from a network-hosted image. Telemetry refers to data collecting functionality. Most software has it. Windows has a lot. Telemetry isn’t necessarily bad since it can, for example, help reveal and resolve bugs and usability problems, but it is easily (and has often been) abused by data-hungry corporations like MS, so disabling it is an advisable precaution. MS = Microsoft OSS = Open Source Software Group policies are administrative settings in Windows that control standards (for stuff like security, power management, licensing, file system and settings access, etc.) for user groups on a machine or network. Most users stick with the defaults but you can edit these yourself for a greater degree of control. Docker lets you run software inside “containers” to isolate them from the rest of the environment, exposing and/or virtualizing just the resources they need to run, and Compose is a related tool for defining one or more of these containers, how they interact, etc. To my knowledge there is no one-to-one equivalent for Windows. Obviously, many of these concepts relate to IT work, as are the use-cases I had in mind, but the software is simple enough for the average user if you just pick one of the premade playbooks. (The Atlas playbook is popular among gamers, for example.) Edit: added explanations for docker and telemetry