First, I think the saying goes more along the lines of "Moore's Law is the empirical observation that the transistor density of integrated circuits, with respect to minimum component cost, doubles every 24 months." http://en.wikipedia.org/wiki/Moore's_law
Secondly, even if it was referring to "computing power" the clock speed of the CPU is not the measure of a CPU's 'Computing power' this is only a small part of the equation.
Look, Ada, may be great, maybe not, but I very much doubt the implementation language had anything to do with this design decision.
And, as I have said in a reply elsewhere. If implementing the alluded flaws would introduce unnecessary complexities, that may compromise safety, then it should only be implemented if it is absolutely required.
I believe this is a very minor limitation for the degree of risk mitigated.
In my personal opinion, if the following two are true:
1) implementing what is required to alleviate the deficiencies implied here introduces complexities or logic that may jeopardise a mission; and
2) not implementing 1 will not pose an unacceptable limitation on the purpose of the system.
Then this was certainly the right choice.
If I were a crew member of a shuttle, I'd certainly opt for the limitation and over introducing another factor that may compromise my life.
I have not had opportunity to consider it, but space travel is a very different domain to what we live in, and to automatically think that earth time is even a suitable time reference for a spacecraft would be somewhat naive. That is not to say that it isn't, but it should a least be considered.
How does the effect a company who develops a product for another company? Does this constitute distribution?
Suppose company X wins a contract to develop product P for company Z, if P is developed using and uses GPL software (possibly even modified version of GPL software) perhaps linked together etc. When company X delivers the final product (which will be used only internally by company Z), does this constitute distribution?
Is the only criteria here, that company Z must also gets the source code?
Is it only that every entity that can get a copy of the binary must also be able to get a copy of the source?
First, I think the saying goes more along the lines of "Moore's Law is the empirical observation that the transistor density of integrated circuits, with respect to minimum component cost, doubles every 24 months." http://en.wikipedia.org/wiki/Moore's_law
Secondly, even if it was referring to "computing power" the clock speed of the CPU is not the measure of a CPU's 'Computing power' this is only a small part of the equation.
Look, Ada, may be great, maybe not, but I very much doubt the implementation language had anything to do with this design decision.
And, as I have said in a reply elsewhere. If implementing the alluded flaws would introduce unnecessary complexities, that may compromise safety, then it should only be implemented if it is absolutely required.
I believe this is a very minor limitation for the degree of risk mitigated.
In my personal opinion, if the following two are true:
1) implementing what is required to alleviate the deficiencies implied here introduces complexities or logic that may jeopardise a mission; and
2) not implementing 1 will not pose an unacceptable limitation on the purpose of the system.
Then this was certainly the right choice.
If I were a crew member of a shuttle, I'd certainly opt for the limitation and over introducing another factor that may compromise my life.
I have not had opportunity to consider it, but space travel is a very different domain to what we live in, and to automatically think that earth time is even a suitable time reference for a spacecraft would be somewhat naive. That is not to say that it isn't, but it should a least be considered.
How does the effect a company who develops a product for another company? Does this constitute distribution? Suppose company X wins a contract to develop product P for company Z, if P is developed using and uses GPL software (possibly even modified version of GPL software) perhaps linked together etc. When company X delivers the final product (which will be used only internally by company Z), does this constitute distribution? Is the only criteria here, that company Z must also gets the source code? Is it only that every entity that can get a copy of the binary must also be able to get a copy of the source?
They only went too far, if the tree was less than 20ft..
OSTG have just sponsored a detox clinic for dupe story addicts...
It's not about being like Windows or other OS, it's about convention. Conventions can be good.