The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I copied the WinXP binaries into a non-OS folder, and run them in Win7 (in a VM). I don't like the Win7 versions either.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
I didn't experience XP very much (only for testing) as Win2K was really, really good. I moved straight from that to 7 and now on 10.
I really don't get all the ranting about Win10 except that it's probably the most widely used OS for developers and we don't complain about the things we don't use.
The only major problem I've ever had with 10 is the seemingly uncontrollable updates and unattended restarts. I changed my behavior to not leave unsaved work in progress overnight. There are still the weird things like custom registry settings/permissions getting reset, but those are small problems that only happen occasionally. Yes, I've tried various Linux flavors in VMs through the years, but then could never find anything really useful to do with them...at least nothing that contributed to the business.
I'd second that. In particular, when I was "upgrading" my NT box to Win2K, the entire process was fully completed in just 10 minutes. It took me a lot longer than that to be convinced that everything really was upgraded and working properly, but it all was and that machine carried on for me for years. In contrast when I eventually moved the machine to XP it took about 90 minutes and initially left quite a bit broken.
I have a machine in our lab running XP. If it ever dies, one of our products will no longer be supportable. This machine runs a development environment for an embedded process, and the IDE is protected by a (God save us) parallel port dongle.
And before any of you say "but you can still buy parallel port adapters!", yes, I know. Unfortunately our experience is that most of them don't implement bidirectional I/O properly, which causes the dongle to fail.
And then the cat crept in and crept out again
The cat crept in and crept out again
So I open the door for that high-heeled paw
I said the cat crept in
And crept out again.
I said the cat crept in and we crept out again.
How do blind people even find the braille messages?
Well, when they fall over the object they will want to feel it to figure out what it was [that they fell over]...
"you have just fallen over a visual aide you stupid git, next time look where you are going."
Watch blind people using an electronic braille line - you'll be impressed! They use both hands, reading the first half with the left hand, then the right hand takes ove reading the second half while the left hand moves back to the beginning, ready for the next line. Some of them read braille faster than I read printed text! Their hands move so fast that you'd think they are trying to brush away the flies...
Another point that impresses me: I look at the Braille tables and do not recognize some codes that they read, but they tell: Oh, that's just because they use the OP table for representing the special Norwegian alphabetics! Or they use this table, or that table, or maybe UTF8 coding or ... There was at least three different ecodings in use for non-AZ-characters before UTF8, but they never thought of it: A single occurence of a "strange" braille code revealed "This text uses encoding so-and-so". Problem solved, nothing to worry about