I somehow doubt that they are using a stock.NET component which is broken - given that FTP is a fairly straightforward client-server protocol and can be implemented using nothing but Sockets.
So, I assume you've never read this site or any of the many similar ones? And you've never heard of production code ever having a bug in it?
I can hand-edit a java file and when I reopen the IDE, it'll pick up the changes. Try that in a Microsoft environment, and you'd better have a project backup.
Um, Visual Studio actually handles that just fine. So I think you're the one spouting off rubbish.
How exactly do you put something into public domain legally, such that you can legally protect them to be in public domain? Really, serious question.
It is a very good question, and the answer is to use the GPL.
Um, WTF? GPL is absolutely not similar to public domain; the gpl-violations people repeatedly make this very clear.
A better answer is, "that's not very clear, could you give an example of what you mean?". About the only thing I think it can sanely mean, is how to prevent other people from claiming it as their work (ie, plagiarism) and suing people (kinda like SCO suing people over Novell's copyrighted code). Maybe something like CC-zero is the answer (you keep a copyright, so you can sue them for... I think it was "slander of title" that Novell used), maybe just make sure your copy with the non-copyright notice gets well indexed by the search engines so any potential victims can find it when they need to defend themselves, maybe plagiarism can be a suable offence separately from copyright violation (I don't think that's the case here in the US, but I hear it might be in much of Europe).
It wasn't the hydrogen that caused the Hindenburg incident, it would have played out almost exactly the same if they'd used helium instead.
They would have had one broken gas bag instead of losing all eight, and probably would have just landed a bit hard. The burning will happen wherever the hydrogen is mixing with air, so along the top where it's escaping and also inside the rigid envelope that air is getting sucked in to... and both of these would be fairly near the other not-yet-broken gas bags, which would melt/burn/whatever and blow their loads as well.
So stop either scaremongering or being afraid of hydrogen, it's no bigger danger than the other stuff we use all the time.
Especially in smaller-than-airship quantities. A hydrogen-filled party balloon would as worst scare people, and a compressed tank is only more dangerous than anything else compressed if you're in an enclosed area.
Hm... what happens if your car's hydrogen tank ruptures in an underground parking garage, or that long tunnel under the English Channel? That might keep it from dissipating fast enough and get rather explodey.
If it was caused by electric/magnetic fields, it would be very easy to reproduce experimentally. If it were caused by some unknown field... every field is associated with a particle, so we're back to it being caused by an unknown particle.
While we can't change patent laws, we can at least avoid having them. We're not forced to patent our ideas just to protect them, because nobody can make sure the very same patents won't be used for suing other developers.
Thus, everyone gets drunk at the same BAC, give or take a small margin.
This is not entirely true, people who drink way too much for a long time develop an actual physical dependency on alcohol, where too low of a BAC does bad things, it takes a higher BAC than normal to be properly drunk, and a moderate BAC is... not exactly the same as being sober I think, but not like a normal person with that BAC either.
But you know what's really gone unchecked? Texting while driving is as bad or worse than drinking and driving [cnbc.com].
And therefore we should be softer on drunk drivers.
Yes, that logic is truly brilliant. Well done!
We should be consistent. Don't be extra-hard on people who are approaching being drunk just because being drunk is something low-class people do. Have the same deterrent for everything with the same level of endangerment.
BAC in a certain (low) range, talking with a hands-free phone, going 5-15 mph faster than traffic, eating "clean" foods (bagel etc)... all the same minor deterrent. BAC in a higher range, texting or maybe using a handheld phone, eating messy food (that require more attention), going 20+ mph faster than traffic... all the same higher deterrent. Going 40+ mph faster than traffic, being seriously drunk, falling asleep at the wheel... all some even more higher deterrent.
Unlike being tired, or having low blood sugar, having an alcoholic drink is 100% avoidable and voluntary in *every single case*. Choosing to drink and drive is choosing to needlessly endanger other people on the road.
Choosing to stay up late before a weekday is choosing to needlessly endanger other people on the road.
Choosing to not eat right is choosing to needlessly endanger other people on the road.
Drinking a couple beers on your camping trip and then having to take your buddy to the hospital when he gets bit by the local wildlife is... um... yeah, you're an ass.
Its goal has always been to eliminate drunk driving.
So then why are they acting to increase drunk driving (by repeatedly redefining "drunk" to approach "stepped within 20ft of liquor store sometime in the last week", regardless of any actual, y'know, impairment)?
Static languages make you do more of your thinking up front. Dynamic languages make it easier to just slap things together and worry about your sanity later.
Apparently a lot of web stuff has sufficiently trivial programming that you usually finish before you have to make a sanity check, so dynamic languages let you get off without thinking at all.
It really doesn't matter if its released under the GPL or not. Not in the least. Largely, the GPL does not address matters of patents. That's what created the GPLv3. Having royalty free copyright access does not speak at all to patent accessibility.
GPLv2 does not explicitly address patents. From my understanding it's considered "fairly likely" that it implies a patent license to anyone using that code, but (part of) the reason for GPLv3 was that "fairly likely" tends to make for very expensive court cases.
But I don't think any of that actually matters here, since as I understand it Google isn't actually using any of the code that Sun released. Even the patent language in GPLv3 looks like it only applies to (modified version of) the released code.
Monopolies aren't legal in the US, unless they first ask permission from the government (an exclusive contract).
This is not true.
Pay attention to what our occasional anti-trust cases are actually about. They're never "X has a monopoly", they're "X has been engaging in anti-competitive behavior", "X has been abusing their monopoly on Y to cheat in market Z", etc.
We need jail time for decision makers. I mean serious jail time.
Why is sentencing people to prison rape always the solution? "the punishment should fit the crime", right? Fine them 2x what they made from it, maybe bar them from holding that sort of position in the future.
The Debian project has decided to adopt a new policy of time-based development freezes for future releases, on a two-year cycle. Freezes will from now on happen in the December of every odd year, which means that releases will from now on happen sometime in the first half of every even year. To that effect the next freeze will happen in December 2009, with a release expected in spring 2010.
Slashdot Mirror
People may appoint Judges for political reasons but they should never bow to those reasons.
Yeah, that's why Judges should be appointed. But local ones tend to be elected, so they need to run for office every so often etc.
I somehow doubt that they are using a stock .NET component which is broken - given that FTP is a fairly straightforward client-server protocol and can be implemented using nothing but Sockets.
So, I assume you've never read this site or any of the many similar ones? And you've never heard of production code ever having a bug in it?
I can hand-edit a java file and when I reopen the IDE, it'll pick up the changes. Try that in a Microsoft environment, and you'd better have a project backup.
Um, Visual Studio actually handles that just fine. So I think you're the one spouting off rubbish.
SATA is up to 6.0 Gb/s now, and networking is starting to hit 10Gb/s.
It is a very good question, and the answer is to use the GPL.
Um, WTF? GPL is absolutely not similar to public domain; the gpl-violations people repeatedly make this very clear.
A better answer is, "that's not very clear, could you give an example of what you mean?". About the only thing I think it can sanely mean, is how to prevent other people from claiming it as their work (ie, plagiarism) and suing people (kinda like SCO suing people over Novell's copyrighted code). Maybe something like CC-zero is the answer (you keep a copyright, so you can sue them for... I think it was "slander of title" that Novell used), maybe just make sure your copy with the non-copyright notice gets well indexed by the search engines so any potential victims can find it when they need to defend themselves, maybe plagiarism can be a suable offence separately from copyright violation (I don't think that's the case here in the US, but I hear it might be in much of Europe).
It wasn't the hydrogen that caused the Hindenburg incident, it would have played out almost exactly the same if they'd used helium instead.
They would have had one broken gas bag instead of losing all eight, and probably would have just landed a bit hard. The burning will happen wherever the hydrogen is mixing with air, so along the top where it's escaping and also inside the rigid envelope that air is getting sucked in to... and both of these would be fairly near the other not-yet-broken gas bags, which would melt/burn/whatever and blow their loads as well.
So stop either scaremongering or being afraid of hydrogen, it's no bigger danger than the other stuff we use all the time.
Especially in smaller-than-airship quantities. A hydrogen-filled party balloon would as worst scare people, and a compressed tank is only more dangerous than anything else compressed if you're in an enclosed area.
Hm... what happens if your car's hydrogen tank ruptures in an underground parking garage, or that long tunnel under the English Channel? That might keep it from dissipating fast enough and get rather explodey.
If it was caused by electric/magnetic fields, it would be very easy to reproduce experimentally. If it were caused by some unknown field... every field is associated with a particle, so we're back to it being caused by an unknown particle.
Because for a lot of uses, that would be solving the wrong problem.
While we can't change patent laws, we can at least avoid having them. We're not forced to patent our ideas just to protect them, because nobody can make sure the very same patents won't be used for suing other developers.
...and then someone will reverse-engineer your work, patent it, and sue you over it.
Every organization with a rather singleminded agenda is bound to become overzealous.
* FSF excepted [ducks and scurries away]
Yeah, it's hard to become overzealous when you've been that way since day 1.
/GD&R
Thus, everyone gets drunk at the same BAC, give or take a small margin.
This is not entirely true, people who drink way too much for a long time develop an actual physical dependency on alcohol, where too low of a BAC does bad things, it takes a higher BAC than normal to be properly drunk, and a moderate BAC is... not exactly the same as being sober I think, but not like a normal person with that BAC either.
1) Open some good pubs & night spots near where people live.
Don't most places have zoning laws to make that illegal?
First offense should be several years of license suspension and a considerable fine, second offense should mean you're never allowed to drive again.
Which would mean you have to move to Europe (except they probably won't take you), or one of the few cities here that have usable public transit.
But you know what's really gone unchecked? Texting while driving is as bad or worse than drinking and driving [cnbc.com].
And therefore we should be softer on drunk drivers.
Yes, that logic is truly brilliant. Well done!
We should be consistent. Don't be extra-hard on people who are approaching being drunk just because being drunk is something low-class people do. Have the same deterrent for everything with the same level of endangerment.
BAC in a certain (low) range, talking with a hands-free phone, going 5-15 mph faster than traffic, eating "clean" foods (bagel etc)... all the same minor deterrent. BAC in a higher range, texting or maybe using a handheld phone, eating messy food (that require more attention), going 20+ mph faster than traffic... all the same higher deterrent. Going 40+ mph faster than traffic, being seriously drunk, falling asleep at the wheel... all some even more higher deterrent.
Unlike being tired, or having low blood sugar, having an alcoholic drink is 100% avoidable and voluntary in *every single case*. Choosing to drink and drive is choosing to needlessly endanger other people on the road.
Choosing to stay up late before a weekday is choosing to needlessly endanger other people on the road.
Choosing to not eat right is choosing to needlessly endanger other people on the road.
Drinking a couple beers on your camping trip and then having to take your buddy to the hospital when he gets bit by the local wildlife is... um... yeah, you're an ass.
Its goal has always been to eliminate drunk driving.
So then why are they acting to increase drunk driving (by repeatedly redefining "drunk" to approach "stepped within 20ft of liquor store sometime in the last week", regardless of any actual, y'know, impairment)?
Static languages make you do more of your thinking up front. Dynamic languages make it easier to just slap things together and worry about your sanity later.
Apparently a lot of web stuff has sufficiently trivial programming that you usually finish before you have to make a sanity check, so dynamic languages let you get off without thinking at all.
</troll>
It really doesn't matter if its released under the GPL or not. Not in the least. Largely, the GPL does not address matters of patents. That's what created the GPLv3. Having royalty free copyright access does not speak at all to patent accessibility.
GPLv2 does not explicitly address patents. From my understanding it's considered "fairly likely" that it implies a patent license to anyone using that code, but (part of) the reason for GPLv3 was that "fairly likely" tends to make for very expensive court cases.
But I don't think any of that actually matters here, since as I understand it Google isn't actually using any of the code that Sun released. Even the patent language in GPLv3 looks like it only applies to (modified version of) the released code.
I don't think mono's been sued over patents yet. Maybe it really is the safer choice despite what everyone had been saying?
Monopolies aren't legal in the US, unless they first ask permission from the government (an exclusive contract).
This is not true.
Pay attention to what our occasional anti-trust cases are actually about. They're never "X has a monopoly", they're "X has been engaging in anti-competitive behavior", "X has been abusing their monopoly on Y to cheat in market Z", etc.
Fining a corporation does not punish the individuals responsible for the actions.
Which is why you fine the people responsible, as well as the corporation.
Trying to extract "what they made from it" can and is hidden through dirty accounting tricks.
I'm sure they can come up with a reasonable upper bound.
Sentencing people to prison time is a deterrent to show that they have something to lose.
So is executing them. Why don't we just do that for everything?
At the moment, they have nothing to lose.
Apart from personal fortunes and nice jobs.
Because OPEC is a bunch of foreign governments, which aren't subject to our laws.
We need jail time for decision makers. I mean serious jail time.
Why is sentencing people to prison rape always the solution? "the punishment should fit the crime", right? Fine them 2x what they made from it, maybe bar them from holding that sort of position in the future.
...a semi truck falls off of an overpass and lands on top of one?
...a semi truck going 200mph the other direction crosses the median?
...a semi truck going 200mph on the other road runs a red light?
...that logging truck in front of you loses its cargo?
...that banana truck in front of you loses its cargo, and sends you through the guardrail?
...you run out of gas while crossing the train tracks?
...some idiot leaves their kids in one with windows up for "just a couple minutes" during the middle of summer?
...someone decides to carjack you?