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.
Permalink for comment 561517
To read all comments associated with this story, please click here.
RE[7]: Too funny
by Lunitik on Tue 14th May 2013 14:56 UTC in reply to "RE[6]: Too funny"
Member since:

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 is the purpose of syslog without something to monitor? What is the purpose of at, cron, init, or xinetd without something to start and stop?

What's absurd is combining these 4 (or 3) apps that does completely different things into one.

As opposed to having 4 utterly different codebases, and all the reproduction of efforts that implies?

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

Now you just look ignorant.

$ cd /etc/events.d

Look at the files in there.

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

It is in their best interests to work with the community, this is what you're missing.

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.

What is a job if not a service? You seem to have a very strange definition of what a service is.

If you don't think logging is a part of service management, I don't even know what to tell you. If I cannot keep track of services, management itself is simply impossible.

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

You'd think so, right?

You'd be mistaken, there are attempts to standardize the format but there is no API definition. Essentially, things are just farting text out of std[out,err] and syslog is throwing that raw into a file. It simply doesn't care what that info is, how it is formatted, nothing.

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".

Please show me a solution which is as seamless as journald over the network. They are all hacks which try to address the shortcomings of syslog.

Reply Parent Score: 3