Not I. I read it as they've teamed up to build the infrastructure. It's unclear how the service will be sold to the customer (for example, presumably they'll also have to agree to lease out their infrastructure for resale by competitors, ala the current situation with cable and telephony).
So Dr. Brown was negligent in that the data was publically (albeit difficultly) accessible
Negligent my ass. The reason the academic community thrives and functions is because of an environment of openness. Dr. Brown shouldn't *need* to worry about some other sleezy scientist stealing his data because they're *supposed* to be professionals. And if the reaction to this is for scientists to start hoarding information and hiding what they're doing from their colleges, the community will be far worse off, IMHO.
"Once you get above the data access layer, you just use your now-tested DAOs."
Huh? When you get above the data access layer, you create a mock DAO that implements the interface and use that to test your business objects. Christ, that's the whole damned reason why Spring is such an excellent unit test enabler: you can easily mock out interfaces and test components in isolation. Which is the very definition of unit test (as opposed to integration or system-level test).
An excellent point. In addition, the atmosphere greatly limits what's observable by ground-based telescopes due to molecular and aerosol scattering, and molecular band absoption. For example, much of the UV spectrum is unobservable on the Earth thanks to atmospheric scattering and absorption by ozone. In addition, regions of the IR spectrum, where AO can be used, are absorbed by H2O. See here for more details.
ROFL! Dude, I don't know what drugs you're on, but I want some! Seriously, I love writing code for my DS as much as the next homebrewer, but you'd be foolish to think that I (and the rest of the homebrew community) represent any more than a miniscule fraction of the DS owners out there. The average DS owner couldn't care less if they could write software for their DS. All they want are decent games they can play on the go.
Meanwhile, opening up the console prevents Nintendo from making money on those development licenses. Moreover, while the licensing model tends to reduce the number of third party developers for the platform, it also results in a much higher quality game library due to the higher barrier of entry (as opposed to the Playstation market, where there are a ton of games, but a small percentage are actually any good).
Not at all. The DS homebrewers have a solution which works nicely for hacking code, but makes it quite cumbersome to try and play pirated software (homebrew code is loaded from the GBA slot using this technique, and since DS games expect to load from the DS slot, they won't work unless they're heavily patched).
I love how everyone's examples are excellent cases of code written by bad *programmers*. Which just proves the point that, like any other language, if you hand Perl to an idiot, you get idiotic code. Why people blame *Perl* for this, though, I'll never know.
Indeed... it's so ironic. The original promise of the web, what made it incredibly exciting, was the idea that anyone, anywhere could have a voice. It allowed for one person to reach millions, cutting out the middle-man.
Well, now blogs have made that dream come true by making the technology easily accessible to the masses. And what happens? People bitch and complain about the quality of blogs. Oh well, that's intellectual elitism for you...
People are leaving genetic material all over the place all the time. From a practical standpoint this is like anything else that you discard, it doesn't belong to you any more.
Then you say:
If I were being cloned that would be different.
So, why is it different? You just threw the genetic material away, remember? If someone manages to clone you from it, what can you do?
So, OOC, do you have specific technical objections to the OASIS standard? Because your entire post *appears* to be predicated on the idea that, since it's based on the OOo document format, it must be bad. So, are there things about the format that make it closed or non-extensible?
Incidentally, I object to the idea that a standard created by a working group would, inherently, be better... I think, given some of the stuff that's come out of the W3C and IETF, it's pretty clear that isn't something one can just assume.:)
Space does not require cutting edge technology. Burt Rutan can tell you more. Humble millionaire's can afford to finance their own journey's into space
Burt Rutan didn't go to space. Well, yes, technically he did, but he didn't even make it to LEO. It costs an order of magnitude more to actually reach orbit, let alone while towing along a weapons platform.
Moreover, again, it's a little tough to develop launch systems without people noticing. IOW, there's no way a country like the US won't see it happening and either deploy countermeasures or move in and shut down the effort with conventional military firepower.
ROFL. Yes, the ban on space weapons is exactly the same as a ban on firearms.
Except for the part where space weapons require cutting edge weapons technology, guidance systems, etc, that have yet to be fully developed. Not to mention multi-billion dollar launch systems required, that none but the largest countries have access to. Oh, and the fact that, unlike firearms, it's a little tough to develop and deploy a space-based weapon unnoticed.
You're one of those people that's afraid that North Korea will just, out of the blue, start waving around a fully functional inter-continental nuclear delivery system, aren't you?
And heaving several hundred bytes of HTTP headers with every little message I want to send doesn't exactly strike me as light-weight.
ROFL! You're complaining about several hundred *bytes*?! Dude, the days of dial-up are over. We're in the world of low-latency broadband, now. Moreover, the place where AJAX can really work is in the corporate world, in which case it's LAN speeds you're dealing with. Seriously, there are a lot of problems with using AJAX for all desktop applications, but protocol overhead isn't one of them...
There are plenty of solutions out there, sounds like you're not interested in googling for them.
Well, if you can find a way to create a custom tree model as described here (which is, BTW, the link I provided in my original post, which you apparently didn't read) in an untrusted XUL app, I'd *love* to hear about it.
Wow, that's a very interesting point... I'd never thought about that. Hmm... thanks for the comment, very insightful. Certainly *not* what I had expected.:)
The interesting thing, though, is that, still, what you describe is simply an effect of capitalism. It's hardly Wal-Mart's fault that this is the way things work out. Labelling them as an 'evil' corporation simply because they provide low prices (as the customer demands), is hardly fair, I think.
Oh please. First of all, if local merchants go out of business because Walmart moves into a local town, blame the local townspeople, not Walmart. Honestly, why do people blame the corporation when it's the customer that's at fault?
Secondly, I'd love to see you provide evidence that communities become poorer thanks to the arrival of a Wal-Mart. Because otherwise, it sounds to me more like anti-corporate fear mongering.
I mean, Walmart has a lot of problems (as the GP mentioned, poor treatment of employees, etc, etc), but if you're going to complain, at least make your complaints legitimate.
Actually, if a price is advertised as "3 for X dollars", there's no reason to assume that you can buy an individual unit for X / 3. As an example, look at how most raffle tickets and similar items are sold. They provide a unit price, and then indicate a bulk price which is cheaper (eg, 1 for five dollars, or 3 for twelve).
Now, yes, most stores do allow one to get a unit at the discounted price, but don't criticise your mother for what is, IMHO, a perfectly valid assumption.
Well, there's nothing wrong with entertaining comments, as long as that's not *all* you have. In my experience, useful comments interspersed with a bit of humour can make code analysis and maintenence at least a little less boring.
Yeah, sample for how to do it exactly *wrong*. Do you *really* need to tell people you're incrementing i by one when the line is "i++"?! Honestly, people... code, written well, is nearly self-documenting. Comments should exist to *augment* the code... clarify the tricky bits, outline complex algorithms, provide explanation for why things are done how they are. They should not simply re-express the code in words...
Example, in the above code, I'd probably have a block at the top which said something like: "If i is less than 3, then <some condition> has been satisfied, so print out 'hello world'".
ROFL. That reminds me of the documentation for the Scientific Atlanta PowerTV APIs (these are the APIs used on various digital settop boxes). They have exactly that style of documentation, *printed*... it's *immensely* frustrating.
Slashdot Mirror
And yet I see anti-North-Korean and anti-China news on US TV all the time (not to mention here on Slashdot).
Not I. I read it as they've teamed up to build the infrastructure. It's unclear how the service will be sold to the customer (for example, presumably they'll also have to agree to lease out their infrastructure for resale by competitors, ala the current situation with cable and telephony).
Wow, way to pimp out your own website when you could have just direct linked to the Paint.NET Website.
So Dr. Brown was negligent in that the data was publically (albeit difficultly) accessible
Negligent my ass. The reason the academic community thrives and functions is because of an environment of openness. Dr. Brown shouldn't *need* to worry about some other sleezy scientist stealing his data because they're *supposed* to be professionals. And if the reaction to this is for scientists to start hoarding information and hiding what they're doing from their colleges, the community will be far worse off, IMHO.
"Once you get above the data access layer, you just use your now-tested DAOs."
Huh? When you get above the data access layer, you create a mock DAO that implements the interface and use that to test your business objects. Christ, that's the whole damned reason why Spring is such an excellent unit test enabler: you can easily mock out interfaces and test components in isolation. Which is the very definition of unit test (as opposed to integration or system-level test).
An excellent point. In addition, the atmosphere greatly limits what's observable by ground-based telescopes due to molecular and aerosol scattering, and molecular band absoption. For example, much of the UV spectrum is unobservable on the Earth thanks to atmospheric scattering and absorption by ozone. In addition, regions of the IR spectrum, where AO can be used, are absorbed by H2O. See here for more details.
ROFL! Dude, I don't know what drugs you're on, but I want some! Seriously, I love writing code for my DS as much as the next homebrewer, but you'd be foolish to think that I (and the rest of the homebrew community) represent any more than a miniscule fraction of the DS owners out there. The average DS owner couldn't care less if they could write software for their DS. All they want are decent games they can play on the go.
Meanwhile, opening up the console prevents Nintendo from making money on those development licenses. Moreover, while the licensing model tends to reduce the number of third party developers for the platform, it also results in a much higher quality game library due to the higher barrier of entry (as opposed to the Playstation market, where there are a ton of games, but a small percentage are actually any good).
Not at all. The DS homebrewers have a solution which works nicely for hacking code, but makes it quite cumbersome to try and play pirated software (homebrew code is loaded from the GBA slot using this technique, and since DS games expect to load from the DS slot, they won't work unless they're heavily patched).
I love how everyone's examples are excellent cases of code written by bad *programmers*. Which just proves the point that, like any other language, if you hand Perl to an idiot, you get idiotic code. Why people blame *Perl* for this, though, I'll never know.
Indeed... it's so ironic. The original promise of the web, what made it incredibly exciting, was the idea that anyone, anywhere could have a voice. It allowed for one person to reach millions, cutting out the middle-man.
Well, now blogs have made that dream come true by making the technology easily accessible to the masses. And what happens? People bitch and complain about the quality of blogs. Oh well, that's intellectual elitism for you...
First you say:
People are leaving genetic material all over the place all the time. From a practical standpoint this is like anything else that you discard, it doesn't belong to you any more.
Then you say:
If I were being cloned that would be different.
So, why is it different? You just threw the genetic material away, remember? If someone manages to clone you from it, what can you do?
I guess I don't understand what's so hard about clandestinely fashioning a big DU rod...
:)
What part of "it's a little tough to develop launch systems without people noticing" did you not understand?
Also, as has been noted, it doesn't need to go any further up than Rutan's vehicle, though I imagine that would make it easier to destroy.
At which point, it's basically an ICBM, not a space-based weapon, and thus isn't the subject of this discussion.
What kind of counter measures can defend against that?
Err, gear which blows up the launch vehicle in transit? Unless, that is, you're telling me the US's fancy missile shield technology won't work...
The last graf was pulled mostly from my ass.
I'm glad you can admit that.
So, OOC, do you have specific technical objections to the OASIS standard? Because your entire post *appears* to be predicated on the idea that, since it's based on the OOo document format, it must be bad. So, are there things about the format that make it closed or non-extensible?
:)
Incidentally, I object to the idea that a standard created by a working group would, inherently, be better... I think, given some of the stuff that's come out of the W3C and IETF, it's pretty clear that isn't something one can just assume.
Space does not require cutting edge technology. Burt Rutan can tell you more. Humble millionaire's can afford to finance their own journey's into space
Burt Rutan didn't go to space. Well, yes, technically he did, but he didn't even make it to LEO. It costs an order of magnitude more to actually reach orbit, let alone while towing along a weapons platform.
Moreover, again, it's a little tough to develop launch systems without people noticing. IOW, there's no way a country like the US won't see it happening and either deploy countermeasures or move in and shut down the effort with conventional military firepower.
ROFL. Yes, the ban on space weapons is exactly the same as a ban on firearms.
Except for the part where space weapons require cutting edge weapons technology, guidance systems, etc, that have yet to be fully developed. Not to mention multi-billion dollar launch systems required, that none but the largest countries have access to. Oh, and the fact that, unlike firearms, it's a little tough to develop and deploy a space-based weapon unnoticed.
You're one of those people that's afraid that North Korea will just, out of the blue, start waving around a fully functional inter-continental nuclear delivery system, aren't you?
Michael Moore's anti-gun documentary Bowling For Columbine.
Wow, way to completely miss the point of that movie...
And heaving several hundred bytes of HTTP headers with every little message I want to send doesn't exactly strike me as light-weight.
ROFL! You're complaining about several hundred *bytes*?! Dude, the days of dial-up are over. We're in the world of low-latency broadband, now. Moreover, the place where AJAX can really work is in the corporate world, in which case it's LAN speeds you're dealing with. Seriously, there are a lot of problems with using AJAX for all desktop applications, but protocol overhead isn't one of them...
There are plenty of solutions out there, sounds like you're not interested in googling for them.
Well, if you can find a way to create a custom tree model as described here (which is, BTW, the link I provided in my original post, which you apparently didn't read) in an untrusted XUL app, I'd *love* to hear about it.
For example, Jesus is not commonly granted godhood. He is the son of a god.
I take it you're unfamiliar with the concept of the Holy Trinity?
Wow, that's a very interesting point... I'd never thought about that. Hmm... thanks for the comment, very insightful. Certainly *not* what I had expected. :)
The interesting thing, though, is that, still, what you describe is simply an effect of capitalism. It's hardly Wal-Mart's fault that this is the way things work out. Labelling them as an 'evil' corporation simply because they provide low prices (as the customer demands), is hardly fair, I think.
Oh please. First of all, if local merchants go out of business because Walmart moves into a local town, blame the local townspeople, not Walmart. Honestly, why do people blame the corporation when it's the customer that's at fault?
Secondly, I'd love to see you provide evidence that communities become poorer thanks to the arrival of a Wal-Mart. Because otherwise, it sounds to me more like anti-corporate fear mongering.
I mean, Walmart has a lot of problems (as the GP mentioned, poor treatment of employees, etc, etc), but if you're going to complain, at least make your complaints legitimate.
Actually, if a price is advertised as "3 for X dollars", there's no reason to assume that you can buy an individual unit for X / 3. As an example, look at how most raffle tickets and similar items are sold. They provide a unit price, and then indicate a bulk price which is cheaper (eg, 1 for five dollars, or 3 for twelve).
Now, yes, most stores do allow one to get a unit at the discounted price, but don't criticise your mother for what is, IMHO, a perfectly valid assumption.
Well, there's nothing wrong with entertaining comments, as long as that's not *all* you have. In my experience, useful comments interspersed with a bit of humour can make code analysis and maintenence at least a little less boring.
Yeah, sample for how to do it exactly *wrong*. Do you *really* need to tell people you're incrementing i by one when the line is "i++"?! Honestly, people... code, written well, is nearly self-documenting. Comments should exist to *augment* the code... clarify the tricky bits, outline complex algorithms, provide explanation for why things are done how they are. They should not simply re-express the code in words...
Example, in the above code, I'd probably have a block at the top which said something like: "If i is less than 3, then <some condition> has been satisfied, so print out 'hello world'".
ROFL. That reminds me of the documentation for the Scientific Atlanta PowerTV APIs (these are the APIs used on various digital settop boxes). They have exactly that style of documentation, *printed*... it's *immensely* frustrating.