That's just given me an idea...
The most evil prank for any *Nix based dev who forgets to lock their machine...
ComicSans on terminal.
Or maybe just slowly lowering the font size until they start complaining of needing glasses.
Those brave souls previewing Microsoft's new Windows Terminal were given a treat last night, as the team emitted an update to its latest take on command line shenanigans. The release comes hot on the heels of the eyeball-friendly monospaced Cascadia Code font, issued earlier this week after a lengthy gestation. The gang has …
I would rather they stopped dicking around with fonts and moving settings, apps and other sit around and did something useful like getting rid of the bugs that lead to blue screens, the bugs that mean stuff doesn't work, the bugs that reset things like the credential guard after reboots and the unbelievably piss poor slow performance of their bloated bug ridden shit
"I would rather they stopped dicking around with fonts and moving settings, apps and other sit around and did something useful like getting rid of the bugs that lead to blue screens"
Blue Screens? That was all the rage back in XP and earlier, but these days BSOD is usually just a sign of hardware failure.
If MS can come up with good monospace fonts I'm all for it. It's not like the font designers' work is taking any resources from the coders - I certainly hope it's not the same people coding kernel and designing UI elements!
Given what all MS has laid off in employees and other cost saving/income enhancing things, maybe they've let go of coders and have turned the font designers loose to make it seem better. It seems that an awful lot of tech companies are going for style over substance. Or maybe it's just "marketing rules"?
And stop fiddling with the fucking firewall settings. I set them the way I want them to be set. Stop fucking around with them just because you want some little hunk of shitty Microsoft software to be able to receive incoming connections from the Internet. I fucking said "NO". Stop changing that to a YES for me at every fucking turn you bastards so I don't need to have an audit process run to continuously scan for you fucking making changes so that they can be undone!
In my experience yes, Windows 10 1903 is very stable. Providing you:
1) Disable auto-updates.
2) Disable IPV6
3) Disable telemetry
4) Don't run too many apps at once.
5) Occasionally kill Windows Store process because it like to hog 50% CPU in the background for no apparent reason (I have actually disabled it completely and only re-enable it when I need to download something from the store, killing it immediately after).
Agreed with it being stable. The only blue-screens I've managed have been from OC'ing my hardware a little (a lot) too much.
It's other things that annoy me. STILL not having a single settings/control panel. That what has been switched over isn't as functional as the old stuff. That some things exist in two states - seriously, I have two sound control er... controls, and two sound mixers, and two volume applets - and they don't even always agree. The old style one looks slightly less clean, but gives me better functionality - having a list of devices with defaults marked and sound activity shown against each instead of a blooming drop-down to select from that only shows the name of whatever is selected as the default device!
Seriously, if MS would give me the option of the Win 7 UI with the Win 10 back end improvements then I'd jump at it.
Biting the hand that feeds IT © 1998–2019