Look at the rest of the top 10. Seems like a) baby boomers listen to the Beatles only, or b) baby boomers haven't found out about/can't be arsed with the internet/last.fm.
Good idea, but it won't take because the websites want your data. The sites want to datamine, they want your shoe size and maiden name and everything.
This could all be managed by the browser in a big config field: "site x: all data; site y: shoe size only; site z: shoe size and maiden name and credit card 1" but how will that translate in an easy to manage, understandable (for the masses) interface?
Another thing is, I can expire my data with certain sites. A webshop I've ordered from in the distant past does not have an up-to-date address for me. This is good.
Will it be substantially better than what we have now?
The software and the insurance are two separate things. The fact that your tax software was closed source has nothing to do with the guarantee that it doesn't contain known errors.
This is an opportunity for OSS vendors: they could offer guaranteed patches, an SLA even. For a small fee, they could compensate you for when things go wrong. Come to think of it, this is what vendors are already doing, along with insurance companies.
The inherent value is not in that it's closed source, but in the company backing up its claims.
Yes yes, but why did they put a zombie in charge of something that would be perfect for containing and managing a zombie outbreak? Seems counterproductive.
Supercomputing and parallel computing are different than building regular apps and websites. Why would you want to get the wrong programmers for the job?
I believe the case sensitivity has to do with backwards compatibility with OS9 (unsure) and you can format the drive with a case sensitive version of HFS. This is a hassle, one of the reasons I haven't done so yet. Annoying.
> RAID-5 [...] That's exactly what Google and many others do
If I recall correctly, they don't even do that. They just have three drives in each machine with a straight copy of the main drive on each. I can't find the source right now, but there was a PDF a while back.
Is this very different from open source though? You can generally get good support from a mailing list if you ask the right questions. You could also buy some support at the developer's company or another OSS support firm.
The major difference is that for all the companies without enough clout to get something done at their software suppliers, support is generally nil, where anyone can ask questions on a mailing list or buy decent support.
Correct me if I'm wrong, but isn't the quality of the protection measure unimportant with regards to the DMCA? I'm thinking CSS (the DVD one): it was so easy to crack but still holds as a protection measure.
I thought that any layer of security, however thin, would guarantee DMCA protection.
Have you ever tried using a shared itunes library on a shared drive? I don't know how itunes would cope with having its library changed from underneath it, but it's worth a shot.
Hello, the keyword in the above post was "unfounded." An unfounded bias. If Mr. Boss Man can tell me why he thinks closed source is way way better than open source, that's fine.
I still think that it's stupid to chose for either and not both. I thought the grownups were all in agreement; use the right tool for the right job. If that tool is OSS, all the better. If it's not, good for closed source.
Now if my boss wouldn't agree with that, I would think he's very short sighted and probably not fit to make any kind of reasonable decision.
Someone else in this thread pointed out that the damages should not be compared to the cost of downloading a song, but to the cost of the right to upload one. Interesting point.
Slashdot Mirror
Firebug.
Webdeveloper toolbar.
Adblocker (I don't care how fast it renders.)
Greasemonkey.
And perhaps something like Tabmix if the options aren't present in Chrome.
Look at the rest of the top 10. Seems like a) baby boomers listen to the Beatles only, or b) baby boomers haven't found out about/can't be arsed with the internet/last.fm.
The correct answer is b).
Good idea, but it won't take because the websites want your data. The sites want to datamine, they want your shoe size and maiden name and everything.
This could all be managed by the browser in a big config field: "site x: all data; site y: shoe size only; site z: shoe size and maiden name and credit card 1" but how will that translate in an easy to manage, understandable (for the masses) interface?
Another thing is, I can expire my data with certain sites. A webshop I've ordered from in the distant past does not have an up-to-date address for me. This is good.
Will it be substantially better than what we have now?
"while copyright is held by an actual person"
THIS SANITY WILL NOT STAND.
I really don't understand who their unit tests didn't catch this one.
Assumptions:
- they have unit tests
- there was a unit test written for this code
- the test covered the edge case of the leap year
- the test was run
Listen, it's your choice to stay with them. There are alternatives. If they treat you like a crook, leave them. What's the problem?
The software and the insurance are two separate things. The fact that your tax software was closed source has nothing to do with the guarantee that it doesn't contain known errors.
This is an opportunity for OSS vendors: they could offer guaranteed patches, an SLA even. For a small fee, they could compensate you for when things go wrong. Come to think of it, this is what vendors are already doing, along with insurance companies.
The inherent value is not in that it's closed source, but in the company backing up its claims.
Yes yes, but why did they put a zombie in charge of something that would be perfect for containing and managing a zombie outbreak? Seems counterproductive.
(See pic in TFA before moderating this post)
Kill the second hand market.
URL or it didn't happen.
URL or it didn't happen.
Willy Wonka is a mod in this place? That would explain a lot.
So you're getting your car fixed by the milkman?
Supercomputing and parallel computing are different than building regular apps and websites. Why would you want to get the wrong programmers for the job?
I believe the case sensitivity has to do with backwards compatibility with OS9 (unsure) and you can format the drive with a case sensitive version of HFS. This is a hassle, one of the reasons I haven't done so yet. Annoying.
> RAID-5 [...] That's exactly what Google and many others do
If I recall correctly, they don't even do that. They just have three drives in each machine with a straight copy of the main drive on each. I can't find the source right now, but there was a PDF a while back.
Is this very different from open source though? You can generally get good support from a mailing list if you ask the right questions. You could also buy some support at the developer's company or another OSS support firm.
The major difference is that for all the companies without enough clout to get something done at their software suppliers, support is generally nil, where anyone can ask questions on a mailing list or buy decent support.
Correct me if I'm wrong, but isn't the quality of the protection measure unimportant with regards to the DMCA? I'm thinking CSS (the DVD one): it was so easy to crack but still holds as a protection measure.
I thought that any layer of security, however thin, would guarantee DMCA protection.
For low values of free.
... wait, is what you describe not called a laptop?
Seriously, an eeePC or whatever they're called with decent resolution and VNC should be perfect for this.
Have you ever tried using a shared itunes library on a shared drive? I don't know how itunes would cope with having its library changed from underneath it, but it's worth a shot.
....
mysqladmin -f drop database
Thanks!
yes | mysqladmin drop database
I haven't used git so I won't comment on it.
(2) the intricate reasons why SVN is better than CVS are beyond the everyday use of developers
I present to you svn move
Case closed (the svn > cvs case, at least.)
Hello, the keyword in the above post was "unfounded." An unfounded bias. If Mr. Boss Man can tell me why he thinks closed source is way way better than open source, that's fine.
I still think that it's stupid to chose for either and not both. I thought the grownups were all in agreement; use the right tool for the right job. If that tool is OSS, all the better. If it's not, good for closed source.
Now if my boss wouldn't agree with that, I would think he's very short sighted and probably not fit to make any kind of reasonable decision.
Someone else in this thread pointed out that the damages should not be compared to the cost of downloading a song, but to the cost of the right to upload one.
Interesting point.