My development is on Linux. Some of my work has to run on Windows as well; VirtualBox has several Windows VMs, a ReactOS VM, and Wine for testing.
I've never had to deal with the BSDs or Macs. If a customer was willing to pay for me to come up to speed on either of them I would consider it, but I have no interest otherwise.
I am slowly coming up to speed on Haiku, and now that most of my application and development software runs on Haiku and its hardware compatibility is much better, I'm looking to eventually move from Linux to Haiku for my primary workstation.
I finally got (very expensive) hearing aids, and made several trips back to the audiologist to have them tuned. Then I wound up not wearing them, because most people think they're speaking English, but it's some kind of mumbly slobbergobble with incorrect, missing, or mispronounced words. The aids just turned "mufuh dogga baytaaa" into "MUFUH DOGGA BAYTAAA."
Yeah, I heard that just fine without electronic assistance.
Paying attention to how often people with "normal" hearing said "what?" to each other was a revelation. Yes, I have a problem. But it's a small problem; the big problem is that a large number of people may as well be trying to communicate by interpretive farting and tap-dancing, because "the words what are coming out of their mouth" are mostly gibberish.
If it was local - implanted, or on my body, it might be a useful tool with the correct training.
If it was networked, it would need to have much tighter security than the current internet.
If it was just a terminal to some corporate server running unknown software for purposes I wouldn't necessarily agree to, nope, nope, nopity-nope. Even if it didn't start off as a device for pushing propaganda and advertising, there's no realistic expectation that it wouldn't evolve into that over time.
Sounds like Jeff Duntmann's "jiminy", which he wrote about in PC Techniques magazine back in 1992. A matchbox-sized general purpose computer and life log, infrared connections to peripherals as needed, with a mesh network to other jiminies and the internet-at-large. Jeff didn't use the term "AI", but that would describe how it worked.
> A matchbox-sized general purpose computer and life log, infrared connections to peripherals as needed, with a mesh network to other jiminies and the internet-at-large. Jeff didn't use the term "AI", but that would.
Notwithstanding that most of the mobile OS’s are locked down more than some would prefer for a “general purpose computer” (but less than is likely for a porta-Grok), and that most devices are bigger than a matchbook to support UI that wouldn't be available in that form factor (though devices are available in matchbook size with more limited UI), and that it mostly uses RF like Bluetooth instead of IR for peripherals because IR works poorly in most circumstances, isn’t that what a smartphone is?
Really interesting link to "Jiminy", I hadn’t heard of that before. Also didn’t know Musk was planning something similar, but I think it’s more of a phone than a wearable?
Windows Phone's UI is still with us, from Windows 8 onwards. Everything on 8, 10, and 11 is optimized for a touch interface on a small screen, which is ridiculous on a modern desktop with a 32" or so monitor and a trackball or mouse.
False. The Metro design was abandoned long ago. No live tiles, no typography-first minimal UIs in windows 10/11. I pin an email app to taskbar/start, I don't see the unread count.
From Windows 10, there is a switch between desktop and touch mode.
They stopped supporting small tablets some years ago though, and made it worse with every Windows update. I can only surmise that it was to make people stop using them. Slow GUI, low contrast, killed apps.
DESQview/X sucked the wind out of DESQview's sails. It was, on paper, a massive upgrade. I had been running DESQview for years, with a dial-up BBS in the background.
But you couldn't actually buy /X. After trying to buy a copy, my publisher even contacted DESQ's marketing people to get a copy for me, and they wouldn't turn one over. Supposedly there were some copies actually sold, but too few, too late, and then /X was dropped. There was at least one more release of plain DESQview after that, but by then Windows was eating its lunch.
I'm booting and running Haiku on my Thinkpad. It's a from-scratch workalike of BeOS, and able to run Be software. Though, frankly, Be software is totally 1990s, so a lot of Linux software written for Qt has been ported to Haiku.
In the end I wound up with basically the same application software as on my Debian desktop, except running on Haiku instead of Linux. Haiku is noticeably snappier and more responsive than Linux+X+Qt+KDE, though.
Wine predates ReactOS. It was basically a FOSS duplicate of Sun's WABI.
I wrote a bunch of software in Borland Delphi, which ran in Windows, Wine, and ReactOS with no problems. Well, except for ReactOS' lack of printing support.
As long as you stay within the ECMA or published Windows APIs, everything runs fine in Wine and ReactOS. But Microsoft products are full of undocumented functions, as well as checks to see if they're running on real Windows. That goes back to the Windows 3.1 days, when 3.1 developers regularly used OS/2 instead of DOS, and Microsoft started adding patches to fail under OS/2 and DR-DOS. So all that has to be accounted for by Wine and ReactOS. A lot of third-party software uses undocumented functions as well, especially stuff written back during the days when computer magazines were a thing, and regularly published that kind of information. A lot of programmers found the lure of undocumented calls to be irresistible, and they wound up in all kinds of commercial applications where they really shouldn't have been.
In my experience anything that will load under Wine will run with no problems. ReactOS has some stability problems, but then the developers specifically call it "alpha" software. Despite that, I've put customers on ReactOS systems after verifying all their software ran on it. It gets them off the Microsoft upgrade treadmill. Sometimes there are compatibility problems and I fall back to Wine on Linux. Occasionally nothing will do but real Windows.
As a Linux user, I hated Flash with a passion. It mostly didn't work despite several Linux implementations. About the time they sorted all the bugs out, it went away. Good riddance.
I've never had to deal with the BSDs or Macs. If a customer was willing to pay for me to come up to speed on either of them I would consider it, but I have no interest otherwise.
I am slowly coming up to speed on Haiku, and now that most of my application and development software runs on Haiku and its hardware compatibility is much better, I'm looking to eventually move from Linux to Haiku for my primary workstation.