As I see it, Linux and related projects lack a lot of consistency and dedication from developers.
As I see it, Linux and related projects lack a lot of consistency and dedication from developers. One browse through freshmeat, and you'll see tons of mediocre unfinished, unupdated projects for an OS that tries to keep compatibility with a dead OS. It's like one big hackjob by a bunch of people who don't agree on key things. That's why you have a million distributions, a million editors, a million shells, etc. The same work just gets repeated over and over, it's sickening.
However, as a programmer I'm focused more on the kernel. It's obvious to me the unix designers cared about simplicity and elegance. Sure it's not perfect, but I think somehow the founding values show through in the often lego-block and orthogonal designs of their subsystems. Sockets, file handles, pipes, fifos, block and character devices, for example, all share a common core API for setting non-blocking status and signalling readiness. That, in turn, makes fork() easier to implement, which makes daemon processes connected by pipes easier to implement, ...... Windows tends to have ways of accomplishing all the same things, but for some reason it seems to work out like their boot process: more byzantine than it could be.
Errrrr wait a minute... Subpar compared to what?Are we comparing /bin/bash to cmd.exe and calling bash subpar????Are we comparing vim or emacs to notepad.exe ?
me>reaper
1. Boot to recovery console and get to windows\repair folder. There you will find all the original registry files.2. Copy all 5 of them to windows\system32\config one by one till all five are copied. DEFAULT, SYSTEM, SAM, SOFTWARE, and SECURITY.[...]