The idea made sense to me, but the execution was trash.
Settings was slow, it wasn't any easier than control panel, and if you wanted to do anything that mattered you ended up in control panel apps which were completely jarring UI-wise from the rest of the PC.
The issue, and this is a recurring Windows theme, was "replacement without feature parity"
Imho, nothing should be allowed to ship in Windows unless it at least covers 100% of previous functionality.
If there are functional gaps, those should require approval at the CEO level.
The Windows team has incinerated a ridiculous amount of goodwill with 80% replacements that leave 20% of previous functionality (often including important workflows for power users) lost.
The issue isn't that Setting was different: it was that it didn't do as much as Control Panel. And that's a fixable issue! Just build the additional widgets / plug-ins.
Back then, unless you were using a projector, the screens weren't that big so we seated clother to the screens.
Besides there isn't that much operation you need to do with a DVD. Appart from volume control (which was set on the TV/speaker system command), you would just need a pause when you wanted to go for a pee so no big deal to only have the corded controller.
Yeah, weird to see a couple of linguistic mistakes like this in an article about linguistic mistakes. Another is the misuse of "latter-day". The article uses it to refer to an old thing that is analogous to a modern thing: "[a] latter-day 'yo!'" But "latter-day" actually describes something modern. (E.g., the "latter days" refers to the present age. See "Latter-day Saints".)
I went from Linux (10 years) to Mac (4 years) to Windows (8 months) to back to Mac. (I have not upgraded to Tahoe, and didn't even realize it was so different until recently)
IMO, there's basically no problem Linux has that isn't worse in Windows (at the OS level). Especially once you get into laptops.
As a counter-point, my company was original purely .NET, then added Python (and later JS).
For us, hiring .NET is WAY harder than the other stacks. We get a lot more applicants in general, but almost zero that meet our standards. For Python roles we get way fewer applicants, but the average quality is much much higher than the .NET average. (JS is a whole other thing, and we frankly aren't as good at hiring there yet)
No, we don't do any coding tests, just discussions of what you've done and how deep your knowledge of your tools goes. .NET folks are far less likely to understand much beyond the syntax, nevermind the "why" of things (even WHY you need StringBuilder) or what a database index is, etc.
Interesting. One would thing, "script kiddies" would be more common among Pythonistas. On the other hand, .NET might be more user-friendly, so that devs are productive even without the knowledge of what's going on under the hood. Kudos for the interview practices, that's similar to how I conduct as well :)
yeah, and mac too, can't run league or valorant. vanguard is their kernel-level anticheat, and windows is like 95% of their market and the difficulty of implementing it on another kernel i guess isn't worth the <5%.
League works on macOS just fine, I played yesterday. Vanguard is buggy (it occasionally quits the client after I finish a game), but the game generally works and has for at least several years.
Why would it be a "bold move"? Linux gaming population is damn near zero, they do not provide a higher profit margin like mac gamers would, and the documented evidence is that supporting Linux users is obnoxious because they are rude and entitled but not actually that much better at providing feedback.
Epic Games bought out rocket league and turned off a native linux build and faced no repercussions. Instead they made plenty of money.
Not sure that's fair, given most Linux gamers look like Windows gamers to the metrics.
That said, devices like the SteamDeck run games on Linux (and that's without considering that every Android game ever is technically running on Linux too).
Let's face it though, PC gaming is already small enough these vs the consoles, that further splitting the marked isn't going to make sense for a lot of companies.
>Not sure that's fair, given most Linux gamers look like Windows gamers to the metrics.
No. All the articles and testimony of game devs abandoning native Linux versions is from well before Proton was a thing, including Epic Games buying Rocket League and preventing you from playing the Native Linux build they had.
It also was not related to anti-cheat or underlying engine limitations or anything. Developers were clear that the problem was the massive lack of uptake mixed with a weirdly entitled community.
Personally I don't think gamers are entitled. Ultimately games are anywhere between 60 - 120 dollars and often barely work on their target platforms. With kernel level anticheat, you're literally being asked to pay them to rootkit your computer with software you cannot audit.
The last 10 years of AAA gaming have been an absolute shit show. The only people who seem to be even trying are Nintendo. Everyone else releases stuff that's buggy as hell and about as fun as a dental cleaning.
It's bold because it's breaking stuff that already works and will continue to work even if you do nothing.
It's one thing to choose not to develop a new game for Linux. It's another to take a game that already runs on Linux and intentionally break it. You're guaranteed to alienate SOME people who are already fans of the game.
Settings was slow, it wasn't any easier than control panel, and if you wanted to do anything that mattered you ended up in control panel apps which were completely jarring UI-wise from the rest of the PC.