Licensed engineers with legal liability. Real engineering fields do it. Only computer (software, systems) engineers and sanitation engineers get away without it
The trouble with that is that computer programming is still really in its infancy. When people first started building bridges, it was just a tree trunk knocked down over the stream or a bunch of rocks piled up. It took centuries to figure out the how to determine the structural limits of building materials, the advantages and disadvantages of different designs, stress analysis, load limits, manufacturing methods, construction methods, etc etc. At first it was guesswork, now bridge building is an exercise in engineering.
IMO, programming right now is just barely out of the tree-trunk-across-the-stream phase.
So what the law is actually proposing is a way to punish commercial companies while letting open source developers off.
I think what would actually happen is that no one would use open source software (or at least, open source software with that kind of license) because you wouldn't be able to sue for damages.
If he tells me there's plenty of oil here, his brother backs it up, and all the oil field workers I know personally, including the ones I've worked with through my technology jobs at various oil companies here in Houston (hint, more than three) tell me there's plenty here on U.S. soil for us we're not allowed to get I believe them.
Or, they could all be wrong, and they are. We have oil here, yes. It's not nearly enough to meet our needs.
Stop catering to the trucker and airline unions and actually allow a good useful train system,
So wait, you want the government to get out the way, but you want the government to build a train system?
Do you honestly think we build inefficient cities and suburban sprawl because of government interference? Do you really think that people are going to just voluntarily give up their SUVs and their lawns and move to a denser urban area because it's the right thing to do? If so, I have a bridge in Brooklyn going cheap.
There's a difference between defending a fascist dictatorship (which no one is doing) and thinking that we had no business barging in like Yosemite Sam.
The problem with operator overloading is that unless you have all the code in front of you, there's no way to tell what an expression does.
Take your example: A = A+B*C + A*D;
You can *guess* that this is doing some multiplications and additions, for for all you know '*' might be some crazy composition function, '+' might be a concatenate of some sort, and '=' might convert to base 13 before the assignment. The only way to know for sure is to know the types of everything there and look through the code. And even then you might have to go crawling up the whole class hierarchy to find the correct operation.
The funny thing is, we went to Mercurial for about 2 weeks, and then went to Git. Somebody made a mistake with Mercurial and messed something up, so the decision was made to go to Git. You know, because it's impossible to mess anything up with Git.:-b
Anyway, like bored said, you can work around the lack of atomic commits, but aside from that as far as I've been able to tell, git makes every single thing harder. And it's not just me. There are many of us that have multiple copies of the repository named things like "project.fucked", "project.fucked2", "project.wtfgit" because you typed the wrong command and git did *something* (and you can never quite tell what) and screwed up your directory.
Give me that old time religion^B^B^B^B^B^B^B^BVCS.
Slashdot Mirror
Not if the other Bitcoin users adapt the difficulty of minting currency to limit the flow.
If only those other greedy bastards would stop mining for bitcoins, my bitcoins would be worth more. What a bunch of jerks.
Licensed engineers with legal liability. Real engineering fields do it. Only computer (software, systems) engineers and sanitation engineers get away without it
The trouble with that is that computer programming is still really in its infancy. When people first started building bridges, it was just a tree trunk knocked down over the stream or a bunch of rocks piled up. It took centuries to figure out the how to determine the structural limits of building materials, the advantages and disadvantages of different designs, stress analysis, load limits, manufacturing methods, construction methods, etc etc. At first it was guesswork, now bridge building is an exercise in engineering.
IMO, programming right now is just barely out of the tree-trunk-across-the-stream phase.
So what the law is actually proposing is a way to punish commercial companies while letting open source developers off.
I think what would actually happen is that no one would use open source software (or at least, open source software with that kind of license) because you wouldn't be able to sue for damages.
Because he doesn't fit *your* definition of morality? "
Because it doesn't fit anyone's definition of morality.
No, you can actually buy a Windows Phone. And they work pretty well.
Your argument is literally "Powershell sucks compared to bash because it's more than I need."
Really? because of all the smartphone interfaces I've tried, I like the Windows phone interface best.
But my experience is limited to playing with the phones in the AT&T store and the Android phone one of my co-workers has.
I am proud to live in a country that uses its foreign policy for its own benefit, even if it's to gain more resources for our country.
If he tells me there's plenty of oil here, his brother backs it up, and all the oil field workers I know personally, including the ones I've worked with through my technology jobs at various oil companies here in Houston (hint, more than three) tell me there's plenty here on U.S. soil for us we're not allowed to get I believe them.
Or, they could all be wrong, and they are. We have oil here, yes. It's not nearly enough to meet our needs.
Stop catering to the trucker and airline unions and actually allow a good useful train system,
So wait, you want the government to get out the way, but you want the government to build a train system?
Do you honestly think we build inefficient cities and suburban sprawl because of government interference? Do you really think that people are going to just voluntarily give up their SUVs and their lawns and move to a denser urban area because it's the right thing to do? If so, I have a bridge in Brooklyn going cheap.
shouldn't the core be left standing?
No?
Why did WTC-7 collapse? Why did it even burn?
Oh I don't know. It's not even like it had been standing next to a burning building that had collapsed and dumped a bunch of flaming debris onto it.
why should it collapse in perfect symmetry.
Well for starters, it didn't.
There's a difference between defending a fascist dictatorship (which no one is doing) and thinking that we had no business barging in like Yosemite Sam.
No company has shown more contempt for its customers than MS
You don't get around much do you?
Also, why on Earth would they evacuate the Pentagon AFTER the earthquake? Does that make any sense at all?
Kind of hard to evacuate it before the earthquake.
The problem with operator overloading is that unless you have all the code in front of you, there's no way to tell what an expression does.
Take your example: A = A+B*C + A*D;
You can *guess* that this is doing some multiplications and additions, for for all you know '*' might be some crazy composition function, '+' might be a concatenate of some sort, and '=' might convert to base 13 before the assignment. The only way to know for sure is to know the types of everything there and look through the code. And even then you might have to go crawling up the whole class hierarchy to find the correct operation.
Operator overloading is a curse.
The funny thing is, we went to Mercurial for about 2 weeks, and then went to Git. Somebody made a mistake with Mercurial and messed something up, so the decision was made to go to Git. You know, because it's impossible to mess anything up with Git. :-b
Don't mix different fixes/features in a single commit.
Yes. That's what you said. I just want to know why.
Just several million lines of code.
Anyway, like bored said, you can work around the lack of atomic commits, but aside from that as far as I've been able to tell, git makes every single thing harder. And it's not just me. There are many of us that have multiple copies of the repository named things like "project.fucked", "project.fucked2", "project.wtfgit" because you typed the wrong command and git did *something* (and you can never quite tell what) and screwed up your directory.
Give me that old time religion^B^B^B^B^B^B^B^BVCS.
The right thing to do would be to put them in separate commits
Really? Because we recently switched from CVS to Git at my place of work, and I would happily go back to CVS immediately.
The difference was that Commodore couldn't sell T-bone steak and potato chips to starving people.
The difference is Commodore spent their marketing budget (and R&D budget) paying their CEO a stupid salary.
Hey, I just thought I'd join in your post hoc ergo propter hoc party.
buy actual real gold.
What for?
So I shouldn't believe the government's numbers but I should believe yours?
And before the Fed there were no nuclear weapons.
And the World Trade Center hadn't been destroyed.
Ribeye steaks cost $12/lb at my grocery, 3 years ago they cost $6
things_that_never_happened.txt