I just found out that f***ing Microsoft is forcing OEM computer
makers to replace the right Control key with their f***ing
co-pilot key before they'll allow them to install Microcrap 11.
Probably old news for a most of you, but I had no clue. I use
the right Control key all the time. Just one more reason to
despise MicroSlop.
Where is Europe and their lawsuits on unfair competition on
this one? Or are they doing this with European keyboards?
On 2026-05-17, RonB <ronb02NOSPAM@gmail.com> wrote:
<snip>
Just another reason I minimize all dependency on Microstupid's
products.
I went through about five of their ergonomic keyboards,--
all of which malfunctioned, before I bought a Logi one which has
been working ever since.
Scott Hoge wrote this screed in ALL-CAPS:
On 2026-05-17, RonB <ronb02NOSPAM@gmail.com> wrote:
<snip>
Just another reason I minimize all dependency on Microstupid's
products.
User-Agent: slrn/1.0.3 (Win32)
?
I just found out that f***ing Microsoft is forcing OEM computer makers to replace the right Control key with their f***ing co-pilot key before they'll allow them to install Microcrap 11. Probably old news for a most of you, but I had no clue. I use the right Control key all the time. Just one more
reason to despise MicroSlop.
Where is Europe and their lawsuits on unfair competition on this one? Or are they doing this with European keyboards?
On 2026-05-17, Chris Ahlstrom <OFeem1987@teleworm.us> wrote:
Scott Hoge wrote this screed in ALL-CAPS:
On 2026-05-17, RonB <ronb02NOSPAM@gmail.com> wrote:
<snip>
Just another reason I minimize all dependency on Microstupid's
products.
User-Agent: slrn/1.0.3 (Win32)
?
I have to use a Windows Surface Go to remote into my office
computer; hence my reliance on Win32. Rest assured I devote a
fraction of my office job to disparaging Microsoft.
I use slrn because it's text-driven, keyboard-based, and allows
me to reply using the Vim editor.
-- Scott Hoge
On 2026-05-17 12:54 a.m., RonB wrote:
I just found out that f***ing Microsoft is forcing OEM computer makers to
replace the right Control key with their f***ing co-pilot key before they'll >> allow them to install Microcrap 11. Probably old news for a most of you, but >> I had no clue. I use the right Control key all the time. Just one more
reason to despise MicroSlop.
Where is Europe and their lawsuits on unfair competition on this one? Or are >> they doing this with European keyboards?
They're probably doing this with all keyboard. Nevertheless, I imagine a
lot of people were similarly annoyed when Microsoft added the Windows
key in the 90s. There is no reason to believe that despite the key
having the Co-Pilot logo on it, we will be able to restore the CTRL functionality rather easily.
On 2026-05-17, CrudeSausage <crude@sausa.ge> wrote:
On 2026-05-17 12:54 a.m., RonB wrote:
I just found out that f***ing Microsoft is forcing OEM computer makers to >>> replace the right Control key with their f***ing co-pilot key before they'll
allow them to install Microcrap 11. Probably old news for a most of you, but
I had no clue. I use the right Control key all the time. Just one more
reason to despise MicroSlop.
Where is Europe and their lawsuits on unfair competition on this one? Or are
they doing this with European keyboards?
They're probably doing this with all keyboard. Nevertheless, I imagine a
lot of people were similarly annoyed when Microsoft added the Windows
key in the 90s. There is no reason to believe that despite the key
having the Co-Pilot logo on it, we will be able to restore the CTRL
functionality rather easily.
A little closer look, and it appears that they're only doing this with the Windows Co-Pilot machines, so that's probably why I hadn't heard about it before. I have zero interest in anything Co-Pilot, so I would not be looking at these.
I would definitely remap that key, but I would also want to find a CTRL key cap to replace it. And, in my case, buying a new computer is highly
unlikely, though I now have four new Raspberry Pis of varying ages, that I'm tinkering with. For the first time I've built a non-GUI Linux machine (supposedly a "writerDeck") and I'm figuring out to work without a Desktop. The Raspberry Pi 3 A+ only has one USB port, so when I need to transfer
files I have SSH into it and, pull it's keyboard to use the USB port for the thumb drive. I've also tried scp (it works), but that seems like more trouble than it's worth (I blame my ignorance). I guess I could set up a BlueTooth keyboard when doing this but, so far, I don't have the gumption.
A non-GUI Linux with a few shell files is pretty fast. I did much the same thing in the 80s and 90s when running DR-DOS. I made batch files to load my applications rCo because I'm lazy.
On 2026-05-18 4:30 a.m., RonB wrote:
On 2026-05-17, CrudeSausage <crude@sausa.ge> wrote:
On 2026-05-17 12:54 a.m., RonB wrote:
I just found out that f***ing Microsoft is forcing OEM computer makers to >>>> replace the right Control key with their f***ing co-pilot key before they'll
allow them to install Microcrap 11. Probably old news for a most of you, but
I had no clue. I use the right Control key all the time. Just one more >>>> reason to despise MicroSlop.
Where is Europe and their lawsuits on unfair competition on this one? Or are
they doing this with European keyboards?
They're probably doing this with all keyboard. Nevertheless, I imagine a >>> lot of people were similarly annoyed when Microsoft added the Windows
key in the 90s. There is no reason to believe that despite the key
having the Co-Pilot logo on it, we will be able to restore the CTRL
functionality rather easily.
A little closer look, and it appears that they're only doing this with the >> Windows Co-Pilot machines, so that's probably why I hadn't heard about it
before. I have zero interest in anything Co-Pilot, so I would not be looking >> at these.
I don't think there will even be Windows machines without Co-Pilot
before too long. It will likely be the default going forward, regardless
of how popular it is.
I would definitely remap that key, but I would also want to find a CTRL key >> cap to replace it. And, in my case, buying a new computer is highly
unlikely, though I now have four new Raspberry Pis of varying ages, that I'm >> tinkering with. For the first time I've built a non-GUI Linux machine
(supposedly a "writerDeck") and I'm figuring out to work without a Desktop. >> The Raspberry Pi 3 A+ only has one USB port, so when I need to transfer
files I have SSH into it and, pull it's keyboard to use the USB port for the >> thumb drive. I've also tried scp (it works), but that seems like more trouble
than it's worth (I blame my ignorance). I guess I could set up a BlueTooth >> keyboard when doing this but, so far, I don't have the gumption.
A non-GUI Linux with a few shell files is pretty fast. I did much the same >> thing in the 80s and 90s when running DR-DOS. I made batch files to load my >> applications rCo because I'm lazy.
I used to love being in a text environment at all times, using a GUI
only when necessary in a particular application. I would always be
fascinated by how people could do everything within a GUI as in MacOS,
but it just seemed like a bad idea because of the GUI overhead causing a performance penalty. I'm happy that the concerns of the 1990s no longer
exist today.
On 2026-05-18 4:30 a.m., RonB wrote:
On 2026-05-17, CrudeSausage <crude@sausa.ge> wrote:
On 2026-05-17 12:54 a.m., RonB wrote:
I just found out that f***ing Microsoft is forcing OEM computer makers to >>>> replace the right Control key with their f***ing co-pilot key before they'll
allow them to install Microcrap 11. Probably old news for a most of you, but
I had no clue. I use the right Control key all the time. Just one more >>>> reason to despise MicroSlop.
Where is Europe and their lawsuits on unfair competition on this one? Or are
they doing this with European keyboards?
They're probably doing this with all keyboard. Nevertheless, I imagine a >>> lot of people were similarly annoyed when Microsoft added the Windows
key in the 90s. There is no reason to believe that despite the key
having the Co-Pilot logo on it, we will be able to restore the CTRL
functionality rather easily.
A little closer look, and it appears that they're only doing this with the >> Windows Co-Pilot machines, so that's probably why I hadn't heard about it
before. I have zero interest in anything Co-Pilot, so I would not be looking >> at these.
I don't think there will even be Windows machines without Co-Pilot
before too long. It will likely be the default going forward, regardless
of how popular it is.
I would definitely remap that key, but I would also want to find a CTRL key >> cap to replace it. And, in my case, buying a new computer is highly
unlikely, though I now have four new Raspberry Pis of varying ages, that I'm >> tinkering with. For the first time I've built a non-GUI Linux machine
(supposedly a "writerDeck") and I'm figuring out to work without a Desktop. >> The Raspberry Pi 3 A+ only has one USB port, so when I need to transfer
files I have SSH into it and, pull it's keyboard to use the USB port for the >> thumb drive. I've also tried scp (it works), but that seems like more trouble
than it's worth (I blame my ignorance). I guess I could set up a BlueTooth >> keyboard when doing this but, so far, I don't have the gumption.
A non-GUI Linux with a few shell files is pretty fast. I did much the same >> thing in the 80s and 90s when running DR-DOS. I made batch files to load my >> applications rCo because I'm lazy.
I used to love being in a text environment at all times, using a GUI
only when necessary in a particular application. I would always be fascinated by how people could do everything within a GUI as in MacOS,
but it just seemed like a bad idea because of the GUI overhead causing a performance penalty. I'm happy that the concerns of the 1990s no longer exist today.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 01:56:55 |
| Calls: | 862 |
| Files: | 1,311 |
| D/L today: |
10 files (20,373K bytes) |
| Messages: | 264,321 |