1,329 karma · joined April 11, 2011
I did later run Windows 98 on my kids' machine for games, but I never tried, or wanted to try Windows ME.
Windows 2000 has the best look and feel for the GUI, but I do recall that I usually saw my first Explorer crash within an hour of a fresh install. Windows 7 was peak Windows because you could still get the "Classic" Windows 2000 theme, but with all the under-the-hood improvements. I've gotten used to the Windows 10/11 UI, but I've never liked it and just wish I could go back to the way it looked when Microsoft cared about usability, as opposed to trying to make everything look like a phone.
Next thing you'll be asking to make OneDrive even remotely predictable in its behavior (other than the predictability of "never doing what I expect or want").
I'm so disappointed that all those years later, the Windows UI is literally less configurable than Windows 2.1, which is the earliest version I used. Yeah, I don't miss 16-color mode, but I definitely miss that you had so much flexibility to tweak the UI. Now you're just stuck with some art-school dropout's idea of "flat UI" (seeing as how Microsoft has thrown out most of the great HCI work they, IBM, and others did in the 1980s, in favor of lame aesthetics that are entirely orthogonal to usability) and there's almost nothing meaningful you can change about it.
I also started programming in BASIC, and moved on to Pascal when I discovered Turbo Pascal around 1983, which also happened to be the language most of my CS classes used a year later when I switched majors from foundering in EE to excelling in CS.
I still have a bunch of my BASIC programs from the day.
Those two words have almost exactly opposite meanings, and as stated, they are literally saying they are collecting identifiable data.
All those Windows Media Player skins were awful because they used so much screen real estate on dead space. Whereas the plethora of Winamp skins kept the economy of screen real estate while still providing unique and imaginative visuals.
The whole skeuomorphic trend starting in the mid-90s was similarly awful for the same reason. First, it was often hard to tell what was a control and what was just decoration. Second, it often took trial and error to figure out what was what. And, as I mentioned above, these designs almost inevitably wasted huge chunks of screen space on decoration that provided no functionality.
Of course, we have the opposite problem now. All windows look the same. Title bars are mostly gone. And since companies like Microsoft replaced all their HCI experts with art-school dropouts who think the "flat" look with low contrast is cool, not only can you not tell what app you're looking at. Half the time you can't even tell where one window stops and another starts.
The only good UI thing that's come out of the last decade or two is a near universal support for "dark mode". Otherwise, I would greatly prefer the Windows 2000 "classic" look, or something similar.
While there is definitely something to the plasticity of young brains, for example in language acquisition, or the fact that the Fields Medal eligibility ages out at 40, I believe it's not a linear thing and not a one-way thing.
Awesome book regardless.
If a program didn't work on a newer version of Windows, there's a good chance it was doing something unsupported.
A step on a thousand-mile journey, perhaps, but it's a step.
> NewValue = OldValue >> 3; > This is basically the same as
> NewValue = OldValue / 8;
> RCT does this trick all the time, and even in its OpenRCT2 version, this syntax hasn’t been changed, since compilers won’t do this optimization for you.
The author loses a lot of credibility by suggesting the compiler won't replace multiplying or dividing by a factor of 2 with the equivalent bit shift. That's a trivial optimization that's always been done. I'm sure compilers were doing that in the 70s.
IIRC, originally it echoed one glyph per character typed, but later it definitely echoed 1 to 3 glyphs at random so it wouldn't leak your password length.
The password thing was pretty cool, but it's literally the only good thing about Lotus Notes, which was the most archaic and primitive piece of commercial GUI software I've ever used in 45 years of software experience. I last used it in 2003, and even then its UI was so archaic, it didn't adhere to behaviors (like keybindings, and other basic UI elements) that had been standard since the 80s.
Absolute garbage software.
At the general election, you need to be pragmatic, and decide who is the least worst and vote for that candidate, because the nominee will probably never be someone who is your ideal choice. But in a two-party system, a vote for a third candidate at that level ends up being an effective vote for candidate you _don't_ want. That's not politics, that's game theory.
There's a lot more subtlety to it in a parliamentary system, and I can see some advantages to it, but at least here in the States where it's First Past The Post with a Two-Party system (which is mathematically inevitable with FPTP), sometimes you need to place strategy or ideals.