Windows "slower than other operating systems"
Linked by Thom Holwerda on Sat 11th May 2013 21:41 UTC
Windows "Windows is indeed slower than other operating systems in many scenarios, and the gap is worsening." That's one way to start an insider explanation of why Windows' performance isn't up to snuff. Written by someone who actually contributes code to the Windows NT kernel, the comment on Hacker News, later deleted but reposted with permission on Marc Bevand's blog, paints a very dreary picture of the state of Windows development. The root issue? Think of how Linux is developed, and you'll know the answer.
E-mail Print r 14   · Read More · 221 Comment(s) http://osne.ws/kun
Permalink for comment 561505
To read all comments associated with this story, please click here.
RE[6]: Too funny
by Soulbender on Tue 14th May 2013 08:53 UTC in reply to "RE[5]: Too funny"
Soulbender
Member since:
2005-08-18

You don't think that it is absurd to have 4 binaries essentially doing the same thing in different ways, rather than a single uniform method?


They don't do the same thing. Really. They do 4 different things, well 3 if you combine cron and at.
corn/at and syslog has NOTHING in common. They do NOTHING that is the same. Really, I find it odd that you'd think they do.
What's absurd is combining these 4 (or 3) apps that does completely different things into one.

Browse around /etc/events.d or whatever, you will notice they are scripts doing the same sorts of things as old init files.


There's no events.d that is part of upstart.

Yes, they do, because without a strong community, these companies understand they would limit their capabilities.


If you think they do you're seriously deluded. They're looking out for their own interests, nothing else.

They don't though, they all manage services.


uh, no they don't NONE of them is managing services. Cron schedules *jobs*, syslog writes logs messages, logrotate rotates log files. They do not manage services.

if you don't think rsyslog needs to communicate with each daemon to ensure correct information, you are fooling yourself.


That's what API's are for and there already is one for syslog.

If you had any real experience maintaining a Linux network, you would understand the frustration of the unpredictability of logs


I do and logs is a problem to which there are many good existing solutions, most of them better than the proposed systemd solution. Which you would have known if you had "real experience managing a Linux network".

Reply Parent Score: 3