Comment Re:Why would that be the first step? (Score 1) 206
Virg
This is Sweden, not USA. A guardian is not automatically responsible for the actions of the guarded. If he taught the child to do the act, he'd be guilty, and if he showed gross negligence, he'd be guilty of negligent child rearing, and might perhaps lose custody. The idea that someone has to be blamed is pretty unique to conservative Abrahamic religion countries, and stems back to the "an eye for an eye, a tooth for a tooth" found in the scriptures. In other words, it's bunk.
And yet, here we are reading about it happening, so I'm guessing that it's not as much bunk as you claim.
Virg
The simplest solution is that this guy downloaded stuff and blames it on someone who's beyond the law.
This makes no sense at all, because (as the case itself demonstrated) blaming her would still cause charges to degenerate to him as her legal guardian, so it would be a pointless extra step, unless you're adding the extra and unlikely part that he planned to make it a PR nightmare in the event he got caught.
Virg
Is the loss of the occasional single innocent person really that big a deal when you consider we're talking about people who would probably take several lives if we don't stop them?
The fact that you'd even ask this indicates that you've already jumped the rails. The answer is simply yes, that executing an innocent person should be considered far more abhorrent than not executing ten guilty people. Your argument is also entirely screwed up in that eliminating the death penalty does not in any way equate to setting people on death row free. They'd still be in prison so the worry that they'd kill more is certainly significantly reduced. Still, if being innocent of a crime isn't sufficient to prevent your being executed for it, then there's no "justice" in your justice system. And of course, for just about every crime that could result in the death penalty, executing an innocent person means that the guilty person, the one who committed the crime and the one whose future actions worry you so much, goes free. If you consider that reasonable, then maybe you shouldn't be commenting on anyone else's insanity.
Virg
Yes, every proponent of OSS will produce a nice list of some impressive OSS projects and certainly Android could be considered THE poster child of OSS. But for each successful OSS project there are 10,000 dead or semi dead ones. Imagine any other field with these odds. Imagine for instance bridge design. If only one out of 10,000 bridges designed and implemented would be actually used or usable, that would be terrible.
The analogy you've chosen doesn't make any sense. To extend it to match, you'd have to consider every pallet bridge, board-over-creek and fallen tree and see if they're serving their purpose reasonably well for the effort put into them. In that sense, your analogy fits, and using that analogy, most such "bridges" work very well in terms of utility for cost. To take it back to software, my company has produced a huge array of proprietary programs and products, and the majority of them don't sell for enough to make it worth maintaining them, but the few that do are enough to support the failures and the company to boot. That's just the business, and so by your model proprietary software development doesn't work very well either.
Innovation: Also, take that 10 most successful OSS project list and remove all the items that are OSS projects that are highly inspired by non OSS products predating them (e.g., Lunix/Unix, Gimp/Photoshop, OpenOffice/Office, Android/iOS,
Every product you named sprung from OSS stuff. Linux came from UNIX, but UNIX developed from big iron OS software that got expanded to mini- and microcomputers for free. Photoshop commercialized software that the fashion industry built for their own use, and Office came from a number of products that themselves grew from basic tools available, you guessed it, free for mainframe users.
As an approach OSS has not worked well on average and nothing has really changed over the years. There is no real trend here. The fact that there are some, very few, truly successful, OSS projects now could simple be the result of the fact that there are just MORE OSS projects. In other words, the average chance of an OSS to have really impact has not improved at all. This is simply a number game with no qualitative shift of any kind. Also, lets not kid ourselves. Most end users really care about the FREE part of FOSS and not the fact that they could access or change the source. They want Foss not fOSS.
As an approach proprietary software has not worked well on average and nothing has really changed over the years. There is no real trend here. The fact that there are some, very few, truly successful, proprietary projects now could simple be the result of the fact that there are just MORE proprietary projects. In other words, the average chance of a proprietary program to have really impact has not improved at all. This is simply a number game with no qualitative shift of any kind.
Also, who cares why the end user wants FOSS? If the F drives people to want it and the OSS drives developers to contribute, you've got a working model.
Are the successful projects successful because of OSS or in spite of it? The answer to that is less clear that is should be. As a user, for instance, I may or may not like Linux for desktop. The fact that it is free is completely irrelevant to me because I value my time. If Windows or OSX works more efficiently for me just a little bit I will not hesitate one second to buy either one.
This argument makes no sense because it's entirely reversible. If Linux makes your computing experience better then you'd go with that instead, and so your argument boils down to Windows or OSX always being easier to use and therefore more efficient, when that's only the case because you've worked with it for years.
However, and more importantly, as a developer, the idea of developing a product for an OS that already is a niche product (which would be ok) but then split into however many distros makes Linux a non starter. I have no interest nor the capacity to track all these versions.
Why would differing distros matter to an end product developer? It no harder to write a product that runs on most if not all distros than it is to develop a program that runs on more than one version of Windows, and it's not difficult to write a completely version-neutral version for either OS if you're careful. To give an example, try writing any program that's not trivial for every version of Windows starting with Win95 and ending with Server 2008. Then do the same for OSX (we'll even leave out OS9 because it would prompt too many developers to commit suicide). Then compare that to writing a program that runs on 90 percent of current and legacy distros of Linux. Guess which one will be vastly easier? Various distros incorporate wildly different things for whatever purpose they're pushing, but most of the central components of Linux are pluggable if you're willing to commit the disk space and you have the horsepower. Sure, you could argue that (for example) XUbuntu won't run games out of the box without a bunch of stuff loaded in, but that distro is meant for low power machines so it doesn't contain it by default. Unlike low power versions of other OSes (like Windows Mobile) though, you could install KDE if you wanted to play World of Warcraft. That's the value of a component based OS, and that's why different distros of Linux don't present nearly the same level of trouble as major upgrades of proprietary OSes.
The more conceptual question is if there is an intrinsic force to OSS that makes it more likely to fork into different versions compared to their commercial versions. As far as I can tell the answer is yes.
This is stating the obvious. The driving force that makes an OSS product more likely to fork is that an independent developer has access to the source and so can legally and realistically fork the product if he sees fit. Closed source software doesn't do that because whoever has control of the source can squash independent development efforts, but that introduces the sort of problems that drove people to come up with FOSS in the first place.
For developers and end users this is ultimately not a great thing.
I very much disagree with that. The ability to take a product in a new direction without destroying the old tree is a great thing. It's the core value of OSS.
Virg
186,000 Miles per Second. It's not just a good idea. IT'S THE LAW.