Is anyone actually surprised that a bunch of Ruby developers can't write secure code? Besides, the performance is probably going to be as shitty as Ruby on Snails as well.
Why should someone be rewarded for not being able to meet a deadline or for submitting work that produces inferior results as others? The real world doesn't reward yot for participation alone.
To counter with an example from the real world just look at the malware infections of people installing screensavers for ubuntu. Where was the magic open source pixie dust to stop them. Oh yeah it doesn't exist.
Except they aren't regulating interstate commerce. They are only taxing energy companies within their state and only based on the impact of their emissions within the state (assuming they do business in other states).
Your very false assumption is that Google engineers would have access to the code in the first place.
So you claim they wouldn't have access to their own Android code (you know, where the bug lies).
Droid is a Motorola phone on the Verizon network. Google is one of many participants in the Open Source Android project, which Motorola wisely chose to use in this case. In the past they have used Linux, but they have never went Open Source in the application domain. This meant that in the past, an Autofocus problem would need to be fixed by Motorola engineers. Since it was closed source only a few Motorola engineers would have access to, and famliarity with , the code.
If the code in question was really a bug in Motorola's code then it would have most likely been proprietary software and as such as you claim Google wouldn't have gotten access to it. That Android itself is released open source under the Apache 2.0 license doesn't mean that the customized versions created by say Motorola is going to be open source. So actually, your the one making false assumptions that go against the very words of Google's own people.
In case you are still not getting it, try looking at your broken "Google would work on it anyway" argument this way:
Why wouldn't they work on their own code base?
Number of Open Source handset projects in which Google is Involved: 1 or more
You do realize that most of the changes Motorola did to customize their version of Android are proprietary right? And that the phone manufacturers are under no obligation to open source their additions. But this is all moot since the bug is an issue in the base Android itself.
So your claim is that somehow these Google engineers who found out what the bug actually was wouldn't have found out the bug as fast if the code wasn't open source? Why would it matter whether the code was open source or when these same people would have had access to the code regardless.
So long as those roads are used for shipping mail and connect states to each other, facilitating interstate commerce (to make it regular), they're perfectly Constitutional...
Gotta love the cop out since the vast, vast majority of the traffic on the interstate highways have no commercial purpose and unless you're using them purely for commercial activity then you are being a hypocrite for using them.
But I love the notion that the nanny staters always go to when the issue of being overtaxed or the government overly intrusive arises... "because you think government doesn't have the power to do (some big idea), good luck without your police, firemen, etc!" It's so demagogic... police and firemen are local issues, not federal ones. Ditto for the vast, vast majority of public roads (most belong to states/counties/towns).
Huh? How am I a nanny stater? Because I disagree with the absurd notion of original intent? The very fact that other founding fathers wrote the anti-federalist papers that had views of the constitution that were in direct opposition to the writers of the federalist papers should be enough to show that the concept is absolute bunk. When someone like you tries to claim the "original intent" of something you always use a specially hand-picked group of people that agree with you and ignore the dozens of others that held an opposing view on the subject. It's also funny in that you know absolutely nothing about my political views and have incorrectly plugged me as some sort of tax and spend liberal which is ludicrous and wrong. I'm not a left winger nor have I voted for a Democrat in my life. But I'm sure your pea-sized brain is unable to cope with the notion that someone might have a more nuanced political philosophy than your "zOMG YOU DISAGREE WITH ME THUS YOU HAVE TO BE A LIBRUL!!!!11ELEVENTYONE" view of the world.
Even if there was no CGI used in the prequels they still would have sucked. Jar Jar wouldn't be less annoying and less unfunny had it been an animatronic. Hayden Christiansen's stilted acting would have still sucked had the environments not been CGI rendered scenes. The midichlorian angle would still have been stupid. The failings of the prequel trilogy had almost nothing to do with the CGI and all to do with a poorly written story with piss-poor acting by many of the main actors. Using animatronics and non-digital effects wouldn't have somehow made this different.
Exactly. Even if the prequels didn't use a single bit of CGI they still would have sucked. Jar Jar Binks still would have been annoying and unfunny. CGI is just used as a convenient excuse by old Star Wars fans for the fact that their messiah George Lucas pushed out a trilogy of shitty prequel movies.
That said, I think his point was that over-reliance on CGI has led to a decline in the quality of the scripts that studios end up making. Why blow the budget on writers when the audience has shown, time and again, that they will just as easily part with their money for special effects? Coupled with a general tendency against taking risks with scripts, and you can see the general quality of movies being made has gone *way* downhill over the last 30 years. But I'd argue that while CGI has been a contributing factor to that decline, it's also been a contributing factor to some of the really high quality work that's been done, too. Done well, CGI compliments the work in question.
Because there were never movies made that heavily relied on special effects over story before the use of CGI? You must be kidding. You're viewing the world through rose-tinted nostalgia glasses. There were plenty of crappy movies made during the 50s, 60s, 70s, 80s, 90s that never used any CGI effects.
Short of getting into a pointless pissing match to sort out all of the minor semantic differences between what we've both said, it's effectively something you can essentially change the license of by only including the statement that it contains some BSD code. Or at least, you can release your software under any license you choose even if it includes BSD code.
There is no minor semantic difference. You just have poor reading comprehension. What that statement is saying is that you can create derived works using BSD license code and release the program as a whole under a proprietary license. But the license to the BSD code is still covered under the BSD license.
You yourself have pointed out several times in this thread that you can do this. The nit-picking is identifying every little way in which one is ever so slightly is semantically different from the other.
I've pointed out that one can create works using BSD code and release that under a different license. But this isn't the same as saying you can relicense BSD code at your will. There is a major difference between the two.
good old fashioned compositing almost always create a more compelling, stylized look
Actually pretty much all people doing SFX were happy when digital compositing became viable because optical compositing had some many downsides. Blurry picture, exaggerated grain structure, and all sorts of other generational loss that came from optical compositing were not beloved as "stylized looks".
The real issue is that people like Jim Henson were masters of their trade. Today, any idiot can fire up some software and make an alien who looks 100x "better" than Yoda. However, the mastery isn't there, and it's obvious to everyone except those to whom newer means better.
Implying that there were no people who were working with puppets in the 70s that weren't master puppeteers. Secondly, any idiot has been able to fire up software since the 80s and make badly done CGI. What's your point supposed to be?
Slashdot Mirror
Woot! Another shill review of a Packt Publishing book by RickJWagner!!! Keep the shilling coming, bro!!
Is anyone actually surprised that a bunch of Ruby developers can't write secure code? Besides, the performance is probably going to be as shitty as Ruby on Snails as well.
Wow you people are still whining about Microsoft using BSD code in a completely legal and consistent way to the spirit of the license? Oh noes!!!
Considering the usual size of a BK worker, I'd be more worried about the ground being hurt if she fell out of the window.
Why should someone be rewarded for not being able to meet a deadline or for submitting work that produces inferior results as others? The real world doesn't reward yot for participation alone.
What's with all the slashvertisements for Packt Publishing? They going to pay for Taco's penis enlargement surgery?
To counter with an example from the real world just look at the malware infections of people installing screensavers for ubuntu. Where was the magic open source pixie dust to stop them. Oh yeah it doesn't exist.
Mod parent down for posting under the FP to be at the top.
*poooooooooooooooooot*
Except they aren't regulating interstate commerce. They are only taxing energy companies within their state and only based on the impact of their emissions within the state (assuming they do business in other states).
What's unconstitutional about it?
Your very false assumption is that Google engineers would have access to the code in the first place.
So you claim they wouldn't have access to their own Android code (you know, where the bug lies).
Droid is a Motorola phone on the Verizon network. Google is one of many participants in the Open Source Android project, which Motorola wisely chose to use in this case. In the past they have used Linux, but they have never went Open Source in the application domain. This meant that in the past, an Autofocus problem would need to be fixed by Motorola engineers. Since it was closed source only a few Motorola engineers would have access to, and famliarity with , the code.
If the code in question was really a bug in Motorola's code then it would have most likely been proprietary software and as such as you claim Google wouldn't have gotten access to it. That Android itself is released open source under the Apache 2.0 license doesn't mean that the customized versions created by say Motorola is going to be open source. So actually, your the one making false assumptions that go against the very words of Google's own people.
In case you are still not getting it, try looking at your broken "Google would work on it anyway" argument this way:
Why wouldn't they work on their own code base?
Number of Open Source handset projects in which Google is Involved: 1 or more
You do realize that most of the changes Motorola did to customize their version of Android are proprietary right? And that the phone manufacturers are under no obligation to open source their additions. But this is all moot since the bug is an issue in the base Android itself.
So your claim is that somehow these Google engineers who found out what the bug actually was wouldn't have found out the bug as fast if the code wasn't open source? Why would it matter whether the code was open source or when these same people would have had access to the code regardless.
Aren't jokes supposed to be funny?
And yet when Microsoft included UAC in Windows Vista to address this very complaint they only got lambasted by you same Linux people. What hypocrisy.
So long as those roads are used for shipping mail and connect states to each other, facilitating interstate commerce (to make it regular), they're perfectly Constitutional...
Gotta love the cop out since the vast, vast majority of the traffic on the interstate highways have no commercial purpose and unless you're using them purely for commercial activity then you are being a hypocrite for using them.
But I love the notion that the nanny staters always go to when the issue of being overtaxed or the government overly intrusive arises... "because you think government doesn't have the power to do (some big idea), good luck without your police, firemen, etc!" It's so demagogic... police and firemen are local issues, not federal ones. Ditto for the vast, vast majority of public roads (most belong to states/counties/towns).
Huh? How am I a nanny stater? Because I disagree with the absurd notion of original intent? The very fact that other founding fathers wrote the anti-federalist papers that had views of the constitution that were in direct opposition to the writers of the federalist papers should be enough to show that the concept is absolute bunk. When someone like you tries to claim the "original intent" of something you always use a specially hand-picked group of people that agree with you and ignore the dozens of others that held an opposing view on the subject. It's also funny in that you know absolutely nothing about my political views and have incorrectly plugged me as some sort of tax and spend liberal which is ludicrous and wrong. I'm not a left winger nor have I voted for a Democrat in my life. But I'm sure your pea-sized brain is unable to cope with the notion that someone might have a more nuanced political philosophy than your "zOMG YOU DISAGREE WITH ME THUS YOU HAVE TO BE A LIBRUL!!!!11ELEVENTYONE" view of the world.
but at least the puppet is tangible, striking better emotional cues amongst the other actors and the audience.
Uhh yeah. Because if Jar Jar Binks was a puppet instead of CGI he somehow would have been less unfunny and annoying?
Even if there was no CGI used in the prequels they still would have sucked. Jar Jar wouldn't be less annoying and less unfunny had it been an animatronic. Hayden Christiansen's stilted acting would have still sucked had the environments not been CGI rendered scenes. The midichlorian angle would still have been stupid. The failings of the prequel trilogy had almost nothing to do with the CGI and all to do with a poorly written story with piss-poor acting by many of the main actors. Using animatronics and non-digital effects wouldn't have somehow made this different.
Exactly. Even if the prequels didn't use a single bit of CGI they still would have sucked. Jar Jar Binks still would have been annoying and unfunny. CGI is just used as a convenient excuse by old Star Wars fans for the fact that their messiah George Lucas pushed out a trilogy of shitty prequel movies.
That said, I think his point was that over-reliance on CGI has led to a decline in the quality of the scripts that studios end up making. Why blow the budget on writers when the audience has shown, time and again, that they will just as easily part with their money for special effects? Coupled with a general tendency against taking risks with scripts, and you can see the general quality of movies being made has gone *way* downhill over the last 30 years. But I'd argue that while CGI has been a contributing factor to that decline, it's also been a contributing factor to some of the really high quality work that's been done, too. Done well, CGI compliments the work in question.
Because there were never movies made that heavily relied on special effects over story before the use of CGI? You must be kidding. You're viewing the world through rose-tinted nostalgia glasses. There were plenty of crappy movies made during the 50s, 60s, 70s, 80s, 90s that never used any CGI effects.
Short of getting into a pointless pissing match to sort out all of the minor semantic differences between what we've both said, it's effectively something you can essentially change the license of by only including the statement that it contains some BSD code. Or at least, you can release your software under any license you choose even if it includes BSD code.
There is no minor semantic difference. You just have poor reading comprehension. What that statement is saying is that you can create derived works using BSD license code and release the program as a whole under a proprietary license. But the license to the BSD code is still covered under the BSD license.
You yourself have pointed out several times in this thread that you can do this. The nit-picking is identifying every little way in which one is ever so slightly is semantically different from the other.
I've pointed out that one can create works using BSD code and release that under a different license. But this isn't the same as saying you can relicense BSD code at your will. There is a major difference between the two.
What made the original star wars great was the animitronics for all the characters instead of jar jar binks super imposed cartoon characters.
Because Jar-Jar would have ceased to be utteryly annoying if it had been an animatronic instead of CGI? You're seriously claiming that?
good old fashioned compositing almost always create a more compelling, stylized look
Actually pretty much all people doing SFX were happy when digital compositing became viable because optical compositing had some many downsides. Blurry picture, exaggerated grain structure, and all sorts of other generational loss that came from optical compositing were not beloved as "stylized looks".
The real issue is that people like Jim Henson were masters of their trade. Today, any idiot can fire up some software and make an alien who looks 100x "better" than Yoda. However, the mastery isn't there, and it's obvious to everyone except those to whom newer means better.
Implying that there were no people who were working with puppets in the 70s that weren't master puppeteers. Secondly, any idiot has been able to fire up software since the 80s and make badly done CGI. What's your point supposed to be?
Which, other than the need for attribution, doesn't really restrict you much.
Sure it doesn't. But it doesn't allow you to relicense the code under something else without the permission of the copyright holder.
But, yes, one occasionally forgets that Slashdot is well populated with semanticists and nit-pickers. ;-)
What nitpicking? You claimed one can fork BSD code and change the code's license. That's wrong.