taiki

I've heard this particular chestnut often. In so far as I understand, if your doctor does this, they're committing malpractice. I'm not saying doctors don't do this, or someone's doctor doesn't, but this is not the norm. Not by a long shot.

What netsh winsock reset does is tear out DLLs, tear out various registry settings and mucks about with other system files.

Clearly you have no idea what you're talking about.

http://www.theverge.com/2013/10/21/4852132/history-of-apple-...

Now he's just going to look silly when the episode drops friday.

No, it's not as rare as you think. Yes, it's because of the lousy design of the TCP/IP stack in windows.

netsh winsock reset fixed quite a lot of things.

BTW: Before Microsoft added an automated tool in NetShell to repair corrupted WinSock2, this was the manual procedure: http://www.wikihow.com/Repair-Winsock-and-TCP/IP

Crappy Win32 APIs where bugs are features isn't a mainstream problem? Somehow in your decades of using Windows you have never run into buggy, crash prone applications. Amazing. Even Neo couldn't dodge those bullets.

Registry may never have corrupted on YOU, but that doesn't mean that it doesn't suck when it does happen. And it happens often enough that if you're in any sort of support role, you'll see it more often than you ever care to. Oh, it's rare, but it's prone to happen. It's just godawful design(this coming from someone who likes PHP, mind you) that you have this monolithic system database that somehow everyone can write to in various ways, not all of them good.

I can't find any better sources for why I thought that the driver model itself was wrong, but I do remember that a lot of Windows crashes happen because of crappy drivers. I remember there was a specific reason for it, and it wasn't fixed in as late as Windows 7, and it's even considered a feature. So, you got me there. what ever. I can still gripe about having to wait for Windows to install a driver for my keyboard when I use bootcamp so I can play MWO or Hawken.

netsh winsock reset

as a regular troubleshooting step when diagnosing network connectivity issues. I was long under the impression that the reason why that kept happening was that the NT kernel didn't have a robust TCP/IP stack of its own and was reimplementing the BSD sockets via a translation layer that was easily hooked into by godawful apps that felt like putting whatever it wanted there.

ReFS wasn't on my radar, and that's my fault.

The registry isn't fine. As of Windows 8 it can still hose a machine by going corrupt. The concept of having a centralized application database for application state and other metadata isn't a bad one, the current implementation absolutely sucks. It goes corrupt and the entire machine is rendered useless. Granted, the current solution is to just back it up and hope none of the backups corrupt either. Corruption doesn't happen from just people manually messing with it, corruption happens from a lot of apps reading and writing from it at the same time. A lot of apps not even bothering with good practices in how to handle it either.

As far as Win32 and the driver model not being your problem... When crappy apps written in 20 year old APIs and devices using crappy drivers crash your machine, then it absolutely IS your problem.

I can't speak to your use of OSX with a keyboard. However, given my choices, I'll take weird metakey combos over, "Is my TCP/IP stack going to eat itself this week?" Besides, emacs uses nothing but crappy and bizarre meta key combos and it's still a thing. So.

I'll believe it when they ship it.

EDIT:

Retracted. Looks like it's actually going to ship with Win8.1

No internal slots, isn't this Steve Jobs' dream machine?

I heard they rebuilt the TCP/IP stack so it's not user land 32 bit driver anymore.

Any ideas if/when they'll modernize NTFS? Right now it's a race to the bottom to who has the worse FS, HFS+ or NTFS. WinFS or ZFS on OS X would be a godsend.

What about the registry? Any idea if they'll make that easier to manage for regular people? Am I still fucked if it corrupts?

What about sunsetting Win32? Or improving the driver model?

They're starting to get it on the UI side, but the reason why I use Mavericks as my personal machine and work on a LAMP stack has less to do with how useful or pretty the start menu is, and more to do with the godawful internals of Windows. Or have we just resigned ourselves to a crappy OS internally that we've all just gotten used to?

My first time using Apple Maps was for driving directions from NY to Baltimore. It was mostly pleasant and the voice directions worked.

Mildly annoying though was that when I took a side road to grab lunch, it kept pestering me to get back on the road.

Granted, Google maps does the same thing, or did at the time. I switched it up for a short leg of the trip and when I stopped for gas, I nearly lost my mind when Google Maps did it too. How hard could it be to have a side trip mode or to understand the driver is hungry?