I'd feel the same way if they hadn't already released a working proof-of-concept. It's based on XenServer 7.2 while what they'll be working on will be based on 7.3. A good number of the stretch goals have been done by users on the side for one purpose or another at times or by folks inside the Xen project or involved with XenOrchestra as proofs-of-concept as well. For example, software RAID is fairly common in small lab settings for XenServer installations, one I've used myself.

Actually, they seem to insist it's SUSE now, but I'll always think of them as S.u.S.E.

Huh? That's not hard:

  0
  1
10
11

I'm not sure, you'd have to ask Sir Tim how much he got for railroading this abomination through the process. Oh, wait, you're asking how much it costs to join, aren't you? No idea, I'm afraid.

Some more interesting timing: Apparently Jake's last day was two whole weeks ago, May 25th, and he was officially shown the door on the 27th. I'm not sure if it's true or not, but it's certainly interesting.

Regardless of Jake's innocence or guilt, I find the timing on this to be very interesting: Just after a major change in management and before what appears to be an upcoming change in the TOR protocol. I'm hoping that's just coincidental.

Yes, the problem is that they're making the current version of Firefox instead.

Mine is actually slower but not by a huge amount, somewhere between 5 and 10%, varying from one boot to the next. The shutdown is either quite a bit faster, enough so that I worry whether things are being shut down correctly, or a whole lot slower, with no rhyme or reason as to why or which one I'll get on any particular shutdown. Systemd's "improved" logging system is, of course, no use in figuring it out.

Indeed. Could you please point me to the section in the documentation on how to configure not to use journald?

MOD THIS UP!!

It also still doesn't do POTS dial-up, still a necessity in some environments.

Ummmm. This is November 2014. Where does that contract / funding stand now?

That was the original reason for systemd before they decided to start the feature bloat. The fact though is that you can run startup processes in parallel and could without systemd. SUSE linux was able to do this and did a good job of it long before they switched to systemd while still using standard init scripts. On my system, the switch from that to systemd actually _slowed_ my boot process by about 10% because systemd insists on waiting for things that don't need to be waited for. Through some careful tuning, I've managed to get that slowdown to about 4-5% but it's still slower than the old parallel-run init scripts were.

Well if you want to route onions around the internet, then, yeah, it's an ok router (hint: puree routes better than whole onions and onion soup is even better until you get to the crouton and cheese). I'm mainly looking for a better way to route data from my home network to my Internet connection though.

No, you didn't. You just made it say the same thing again.