...directly in their field of expertise and strength.
If you willingly cut out the best (and sometimes only) advantage that an independant developer has, their freedom to be creative, then good luck with that one.
I don't disagree at all, I have major issues with how copyright is being extended to stupid levels and I especially dislike, when I was doing academic work, the way that you need to pay for a lot of scientific research - but I just don't agree that the method of fighting it is to deliberately break the law in this case. It is not a cause that deserves that kind of response, unlike more serious issues like corruption and the kinds of violent protests in the past used to help secure women's rights and such. If you don't agree with copyright, don't buy copyrighted material *and stick to free material.* I've said before in an older post, you have a right to live and to have liberty but you don't have a right to be entertained for free. Entertainment is so easy to make for oneself that it is ridiculous that anyone should feel the need to pirate to accomplish this.
I think your very true example of the science paywall is a hairier topic however. I'm not saying all science is good but for-pay journals shouldn't need to exist - they should be free for all. It's still tough to justify that deliberately breaking law is appropriate for the science realm considering the hit-and-miss nature of the field but at least there it has a non-trivial impact.
I agree with him and I do sysadmin and software & web development. Feel free to deprive me of all the royalties I receive from people using my products.
Really? You think that's an equal comparison? I have no words, other than you're being intellectually dishonest.
This is an acceptable price.
By whose divine measure? Yours?
Pray tell, what is your occupation, so that others may deem your livelihood a waste of time as well?
I'm not the original poster and i've never had issues with removable media that I couldn't find an application to blame for (some apps seem to keep files open even after the user has "closed" the visible representation of the file in the program). I'd bet very few users really know what is running in the background on their computer and what it is doing. Windows is worse because apps tend to be closed source and not filtered by a distro but even on linux do you really know the exact details of how every program you have installed behaves?
And afaict a file open for read is more than enough to prevent unmouning a partition on both windows and linux. It doesn't need to be writing it.
It is pretty interesting how Microsoft neglected to make it more intuitive since its introduction in XP (or was it 2000? I do not recall.) As another poster noted there's partly some of the functionality there in Linux but it's not hooked up to any current GUI properly. A real pity. And you are correct, just holding a file open for reading is a blocker in both cases, which is what actually catches most people out.
If the OS lets the user force unmount then at least the FS gets the opertunity to shut down cleanly even if the app doesn't. If the OS doesn't let the user force unmount and the user pulls the plug anyway then neither the FS or the app gets to shut down cleanly.
Though as you say linux isn't really much better No OS i'm aware of has proper handling for notifying users and their applications of WHY their unmounts are failing.
And I found out the hard way that lsof won't tell you if the kernel itself has the file open. I spent ages trying to figure out why I couldn't unmount a partition before finally realising it was because I had an iso image on the partition loopback mounted.
Didn't realise that about lsof, that's good to know.
Ah yes, oft to get the error message: "Something is using the drive but I'm not going to tell you what and I am not going to even let you force the matter. You'll have to close all applications, then I may deign to let you have the device back. Maybe not. You'll have to reboot me, sucker. Bu-wa-ha-ha-ha-ha!"
Windows holding on to USB devices is a bloody PITA. Sure, I can find the lock after a bit of process inspection but I'd hardly call that intuitive.
If you don't know what your computer is doing and why it would be writing to a removable device then that's your own failing. Linux does that just the same too - ever seen 'Device or resource busy'? No help there. Allowing you to force unmount is not a safe thing to do for casual users - you need to know what you're doing and be prepared to accept the consequences of a mistake.
Windows is perfectly fine here if you use and maintain it correctly, and part of that is not installing random background running applications that keep hitting the filesystem and not leaving programs open with files on the device you're trying to eject(!) Explorer windows count as a program in this case. Thumbnail services etc.
If you still have a problem with it and your current solution is a more manual method, just go with something like Lockhunter. Works fine for this situation. Installing a separate utility for this task is another (valid) complaint entirely, in that Windows really never comes with an easy toolchain out of the box. Lockhunter just provides the same functionality as Linux's lsof, so it's worth having.
...and no proper OS (Windows
Did you just claim an OS that can't even eject a USB drive, a proper OS??? Bahahaha!
...sure Windows can. It's called 'Safely Remove Hardware'.
Not going to bother responding to the out-of-hand dismissal of my other points, it's clear you're not actually interested in a debate.
If someone says that a particular license is not suitable for them, why the pithy 'boo-hoo' response?
Because it's virtually always someone whining about the fact that someone made a choice they can't stand, and feel a need to gripe about it instead of accepting it and moving on. Also, because this is Slashdot.
A post by someone that states exactly why they don't use the GPL and why it doesn't work for them, on a discussion topic on how GPL use is declining, is 'griping' about it instead of accepting it and moving on? Seriously? The fact that our posts exist make this entire point completely hypocritical. Slashdot, indeed.
The problem with GPLv3 is that I can't use it in an application I develop unless I release any changes/mods I make to the source code.
That was true with the GPLv2 as well.
That's my secret sauce. If I'm a startup and trying to form a niche in an industry, why would I want to give my recipe away?
Boo hoo, so write it yourself. Why is it every complaint against the GPL seems to come from those who want to mooch and not contribute?
Why is it every shout of 'write it yourself' to people saying that the GPL viral source-release 'feature' has downsides, seem to come over the internet, presumably created with dozens of individual pieces of software they did not write, on hardware they did not manufacture, by people in houses they did not bit, fed by food they did not grow, in a society they did not create and perhaps, not even contributed to? I'm using extremes to be a dick, but my point stands - there is a phrase 'standing on the shoulders of giants,' and yes, that applies to industry and producing a profit, using technologies and concepts that, surprise, may not have been invented by them, but merely refined and targeted. If someone says that a particular license is not suitable for them, why the pithy 'boo-hoo' response? Pithy is indeed the word I have to use to describe much of the open-source movement.
Have you noticed that all of the "flash mob" robberies are always committed by Africans, as have been those who commit violent, racially motivated beatings of whites?
Have you noticed that pedophiles are always white?
A morsel of genuine history is a thing so rare as to be always valuable. -- Thomas Jefferson