Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment: Re:I hope she is prosecuted (Score 2) 252

by DrXym (#49536747) Attached to: Wellness App Author Lied About Cancer Diagnosis
More shame on the NHS then.

As for being sued for calling them quacks, I assume you mean Simon Singh's run-in with chiropractors. He eventually prevailed (they dropped it after an onslaught of complaints against their members) and the case became a driving force for reforming defamation law.

So the UK should be glad they sued. Libel law in the UK now requires the claimant to demonstrate it caused serious harm and there are defences for honest opinion, academic peer review, and public interest.

Comment: Re:Why do people dislike systemd so much? (Score 1) 225

by DrXym (#49510287) Attached to: GNU Hurd 0.6 Released
Ah yes, the "fallacious argument" that has happened countless times in open source already. Numerous, large projects and dists have forked before now.

All it takes is the motivation, a group of likeminded individuals and the willpower to deliver a dist that does not use systemd. I expect most packages in the debian universe have no deps on systemd and therefore no work required to support those packages. So we're talking system packages, some daemons and maybe a few shims for edge cases.

As for why there are only 2 dists left not to have gone to systemd, perhaps that should serve as a clue in itself.

Comment: Re:Mandatory xkcd (Score 1) 225

by DrXym (#49499717) Attached to: GNU Hurd 0.6 Released
Your justification is incoherent. If you want to administer "old school" Linux, you just use the old commands. If you want to administer a dist with systemd you use the new commands, or the old commands which are symlinked into their new equivalents.

I'm not sure what the fuck "old-school" even means since it has constantly changed from its inception. Except by saying "old-school" you demonstrate that Amish mentality - drawing a line in the sand and saying things shouldn't possibly progress beyond that point, even if its for the better.

All the whining over systemd could apply equally to procfs, devfs, pci, usb, btrfs, acls, etc. A barrage of changes that (competent) admins are expected to incorporate into their knowledge.

Comment: Re:For me, there are two questions. (Score 4, Insightful) 225

by DrXym (#49491809) Attached to: GNU Hurd 0.6 Released
The debate about micro or monolithic kernels was just a backdrop. The real reason HURD failed had more to do with the mindset of the people involved.

Linus (impatient with the pace of HURD) developed a quick and dirty kernel that a Unix user land could be built on top of. He took a lot of shortcuts, he didn't think too much about portability and basically just made a beeline for the end line - to get a shell and hence other stuff running over a kernel. The kernel filled out and became portable as the project gained momentum and volunteers.

Whereas HURD got stuck up its own ass for correctness and politics. And that's even before Linux existed as a thing. It's hardly a surprise that when Linux did appear that people jumped ship.

It's true there was a debate about micro kernel designs but that alone doesn't explain HURD's failure.

Comment: Re:Wouldn't a re-write be more fruitful? (Score 2) 209

by DrXym (#49468575) Attached to: Linux Getting Extensive x86 Assembly Code Refresh
The problem with total rewrites is they almost always involve a huge amount of effort, introduce new bugs and when they "work", users barely notice the difference. So the company soldiers on, applying patch upon patch to some bullshit codebase and suffering from it but in a incremental way.

Worst of all is when they embark on a rewrite and give up half way through. I was involved in a project to port a C++/ActiveX based system to .NET forms. They ported most of the major views but left a lot of the minor stuff from the old codebase lying around and wrote bridges to host it in the new framework. So they doubled the code, half of it became bitrotten and hidden by the new code and bloated out the runtime. Great project.

We are experiencing system trouble -- do not adjust your terminal.

Working...