The argument is that, if pid 1 dies, everything dies. Also a big pid 1 presents a big attack surface for nasty people.

Of course the exact same argument applies to a kernel: if something goes wrong in the kernel, everything dies and a big kernel presents a big attack surface to nasty people. However, I observe Linux is not a microkernel but it has a reputation for both reliability and being relatively secure. On the other hand, the quality of the people developing the kernel seems to be higher than those developing systemd, or at least that is the perception I get from reading all the hate on the Internet.

Most of the land that Scotland controls is mountains and other wilderness which isn't economically productive. Sure, it would get a lot of the oil, but that is a finite resource and when that's gone, what's left? I suppose they can turn themselves into a giant Highland Theme Park.

No it isn't. The UK is part of the EU. If Scotland leaves the UK, it leaves the EU. Yes, it will cause some practical difficulties but these would be only a few of the many practical difficulties that need to be resolved in the transition period.

Can you give some examples in which England has treated Scotland badly in the last twenty years? Or two hundred years?

Actually, it is the UK that is harvesting British oil. Except it's not the UK, it's oil companies who then pay taxes to the UK. The taxes then get used all over the UK according to need. This is the way most Western countries operate.

The UK's nuclear submarines are based in Scotland.

All of the jobs at the naval base in Faslane will be gone along with the nuclear weapons. A future Scottish government might, therefore, decide to allow the UK to continue to keep its submarines there.

It's a decade to an order of magnitude.

Err, no.

OS X uses the XNU kernel from NextStep which is a hybrid of the Mach microkernel, some components from BSD (the network stack and the virtual file system) and a device driver architecture which was completely new for OS X. Over the years, a lot of the BSD code has been rewritten with the introduction of more granular locking and better abstractions for the file system and networking APIs.

OS 9 had nothing to do with NextStep.

However, there could be something in the summary on Slashdot, quite easily. The first word is "KDevelop". That could easily have been a link to the project front page, or it could have been expanded to "The KDevelop IDE" and everybody would be happy.

From the KDevelop Front Page.

That seems fairly self explanatory to me.

When he made the promise, the development team consisted only of himself. Now there is a whole company with a number of employees who depend on Minecraft licence sales for their salaries. If Notch open sources Minecraft, all these people will lose their jobs.

So it's probably greed, but not necessarily. In any case, sales haven't tailed off yet, so he hasn't broken his promise.

You think 1m AUD is big? A couple of years back I was on a project for the British government where they burned nearly that much every week. In the end they had literally burned it, they would have got better value because at least it would have kept the building warm.

Well of course you'd be absolutely insane to try to put sendmail and Apache in the same address space. In fact, sendmail forks (or at least used to fork when I last looked at it 10 years ago) to serve each incoming connection, so it's insane to try to restrict sendmail on its own to only one address space.

I thought my mention of kdaemonhostd (sendmail in the kernel, yay!) plus the fact that daemonhostd is derived from svchost(.exe) would be enough to show the post is not entirely serious.

I did do a quick scan of the web site to make sure the idea is not real. However, it's possible that I missed it.

Not sure about that, but they are inventing a new way to run services. They will have a new program called daemonhostd which can host multiple services. All you have to do is recompile sendmail and apache as shared object libraries and daemonhostd will dynamically load and run them in the same process to save resources.

As a further refinement, they are also writing kdaemonhostd which is exactly the same but it all runs in kernel space to improve performance.

But also,

A d too many.