Unless you happen to own the right hardware, getting wireless to work on linux will involve jumping through hoops that the average computer does not have the desire to do. If telling the truth make me a troll, then a troll I am.
If you are going to claim to be from Texas, please try to understand the difference between "succeed" and "secede" and between "apart" and "a part". I understand you probably went to school in Oklahoma, but the rest of the world does not get that.
Didn't your mother ever tell you that life is not fair. Moderation isn't there to make you feel good. It is there so you can filter comments based on quality. (Why is it that I couldn't help chuckling as I wrote that.) A comment is just as redundant whether it was made by a dumbass who doesn't bother to read or by someone who posted between refreshes.
You're right. Time often seems to compress in stressful situations. However, it seems to me that if the object exerted enough force to create "a foot wide crater in the ground", then it would cause more than a flesh wound.
The features you labeled 1, 2 and 3 are not limited to COBOL. Any "modern" language is capable of doing these things. The primary deficiency I find in COBOL is "that you really can't get too fancy in the code without it becoming unreadable and unmaintainable." Many problems require "fancy" solutions, and the key to making fancy solutions readable and maintainable is refining the solution into discrete, maintainable components. While it is possible to do this in COBOL, I find that it is much easier in other languages.
ASP.NET? Your frustration is understandable now. Remember that the scope of a single code-behind is probably analogous to the scope of a single mainframe job. If there is a chance that your first JCL step might not create the file that the second step uses, then you put a condition on the second step. You have to do the same thing in your.NET app. If their is a chance the object didn't get instantiated, you put a condition on using it.
I believe that it is the architecture that COBOL usually runs on that is what makes it so conducive to "manipulating and moving massive amounts of data". As far as maintainability is concerned, COBOL makes good software engineering a hard and frustrating task. That being said, I am always amused at attempts to marginalize COBOL. I am quite certain that in the 2 1/2 hours that I have been awake this morning, at least two of my actions have been processed by COBOL code. I don't buy that "nothing beats COBOL," but I am convinced that COBOL does make the world go 'round.
They did not ban it because of the f-bomb. They banned it because the video sucked. It barely makes sense and it is not funny at all. Apple isn't worried so much about family values as they are about good taste.
There you go again - messing up a perfectly good theory with logic and facts. You should probably lurk for a while until you get an idea of how things work around here.
At least be an informed poster on Slashdot, even if you are inflamitory.
Your post is very enigmatic. You want to break slashdot tradition by expecting an informed poster, but you still carry on the well-established tradition of failing to use spell-check.
The fire is a chemical reaction between the grass (fuel) and air (oxidant). Unless google has developed a strain of grass that is not carbon-based or somehow remove the oxygen from the air on their campus, then a brush fire there would most certainly produce CO2.
Slashdot Mirror
Unless you happen to own the right hardware, getting wireless to work on linux will involve jumping through hoops that the average computer does not have the desire to do. If telling the truth make me a troll, then a troll I am.
80% will not even be able to get wireless to work.
If this goes through, I will finally get to fulfill my lifelong dream of charging companies to interview me.
Dude. It was a joke!
ya'll'll
I'm from from Texas and that even makes my head hurt.
There's some poor schmuck in Bosnia right now googling how to pronounce it.
If you are going to claim to be from Texas, please try to understand the difference between "succeed" and "secede" and between "apart" and "a part". I understand you probably went to school in Oklahoma, but the rest of the world does not get that.
Exactly how does appearing on Good Morning America constitute STFU?
our magnetic field "condom"
Thanks! I'll never be able to look at Aurora Borealis again.
If you're only meeting women in step 3.5, what the hell kind of porn were you making in step 3???
This kind.
Everyone knows they're all pictures of boobs anyway.
After years of psychological training, I can surmise that you were touching yourself when you wrote that.
Way to go jerk.. Now La Psicologia Familia will be knocking at your door with some cement shoes.
That's not their style. They just sign the committal papers and let Nurse Ratched take care of you.
Didn't your mother ever tell you that life is not fair. Moderation isn't there to make you feel good. It is there so you can filter comments based on quality. (Why is it that I couldn't help chuckling as I wrote that.) A comment is just as redundant whether it was made by a dumbass who doesn't bother to read or by someone who posted between refreshes.
The results are rather disappointing.
A t-shirt!?!?!?
Why does this jackass misspell 'women'?
Why the fuck is this even possible?!?!?
Apple are shooting themselves in the foot with their rules.
I wish I had that kind of gun.
Maybe you missed, but we have a new administration now. W is in Dallas pursuing other opportunities
You're right. Time often seems to compress in stressful situations. However, it seems to me that if the object exerted enough force to create "a foot wide crater in the ground", then it would cause more than a flesh wound.
The features you labeled 1, 2 and 3 are not limited to COBOL. Any "modern" language is capable of doing these things. The primary deficiency I find in COBOL is "that you really can't get too fancy in the code without it becoming unreadable and unmaintainable." Many problems require "fancy" solutions, and the key to making fancy solutions readable and maintainable is refining the solution into discrete, maintainable components. While it is possible to do this in COBOL, I find that it is much easier in other languages.
ASP.NET? Your frustration is understandable now. Remember that the scope of a single code-behind is probably analogous to the scope of a single mainframe job. If there is a chance that your first JCL step might not create the file that the second step uses, then you put a condition on the second step. You have to do the same thing in your .NET app. If their is a chance the object didn't get instantiated, you put a condition on using it.
I believe that it is the architecture that COBOL usually runs on that is what makes it so conducive to "manipulating and moving massive amounts of data". As far as maintainability is concerned, COBOL makes good software engineering a hard and frustrating task. That being said, I am always amused at attempts to marginalize COBOL. I am quite certain that in the 2 1/2 hours that I have been awake this morning, at least two of my actions have been processed by COBOL code. I don't buy that "nothing beats COBOL," but I am convinced that COBOL does make the world go 'round.
'Blog' is lame. 'Tweet' is gay. That is a big difference.
They did not ban it because of the f-bomb. They banned it because the video sucked. It barely makes sense and it is not funny at all. Apple isn't worried so much about family values as they are about good taste.
If I were you, I would host it on a stolen iphone and make sure my hat was reinforced with an extra layer of tin-foil.
There you go again - messing up a perfectly good theory with logic and facts. You should probably lurk for a while until you get an idea of how things work around here.
At least be an informed poster on Slashdot, even if you are inflamitory.
Your post is very enigmatic. You want to break slashdot tradition by expecting an informed poster, but you still carry on the well-established tradition of failing to use spell-check.
The fire is a chemical reaction between the grass (fuel) and air (oxidant). Unless google has developed a strain of grass that is not carbon-based or somehow remove the oxygen from the air on their campus, then a brush fire there would most certainly produce CO2.
There's more to life and computers than Java.
Let us pray so that this evil will be striken from our eyes:
Yea, though I walk through the valley of the shadow of pointers, I will fear no leaks: For GC art with me...