And in SoCal police chasing cars are broadcast on TV. For the purpose ooooof what exactly? I think the NASA broadcaster should have a shot of tequila before going on the air or should have had several the night before. Certainly would make the broadcast a little more fun. Maybe even give it a pulse.
Spend some time in communist Cyprus, where the janitor make the same amount as the hospital administrator. But past his first sentence, the 15 year old is missing the point.
Homeless and injectables or smokeables don't mix. The only time I met ex girlfriend's mother, she was begging on a corner sitting on streams of her own urine. When I told her that "a lovely young woman who reminded me of you wanted you to have this cheeseburger and food vouchers" she looked at me, nodded and then turned and started asking the cars for money.
Keep the hard drugs away from the homeless - like that's possible.
And I've seen two programmers in different companies use 15 page case statements with conditionals within the case statements. It didn't matter if the person was using a verbose language or a sparse language; they didn't understand the concept of wrapper functions, delegation and proper class structure for organization.
One was unfixable due to time constraints and the other ended up being replaced by 5 lines of command routing code, and all the conditional functions moved into appropriate classes.
In these cases, it didn't matter if the language was verbose or not, the programmers simply didn't think there was anything wrong with just making the data organization flat and case statement bigger.
But, in the second incident of this nightmare, where the language was verbose, the problem was much easier to fix, because it was at least easier to understand the code as it was more self documenting.
The code (pretty much) documents itself. Less deciphering what the programmer really meant, especially when you are the programmer and you're looking at your code six months later.
Why should someone make a language more difficult? Just to raise the bar to becoming a programmer?
I agree that we do need people who really know how to program but does that have to be every programmer and does every language need to be difficult?
Maybe televisions should have never done digital, so I can be an expert in learning how to tune the channel so that my business of channel tuning will stay healthy?
You DO need experienced programmers, and you do need machine language and C/C++. The question is, "do you really need that in every case?"
In the majority of languages today, this is the way things work but doesn't it seem really backasswards when compared to the simple and verbose "put item 1 of allItems into myArray".
I beg to differ. Coding doesn't have to be hard. Debugging is debugging... or is it problem detection and solving? Clarity of your code and clarity of the language structure you are using either helps or hinders debugging.
Part of coding is how good your IDE is in telling you what is going on. Another part is how understandable your code is and that is dependent on the structure of the language you are coding in.
Is it really dumbing down or are the languages that we use more obtuse than necessary? The common syntaxes of the day are left over from language design when every bit mattered. If English-ish syntax is more clear, then why not use it?
Isn't it more about clarity of the language than about shortest code possible?
God put them there to test us.
Strapping the phones to my head as we speak, with each one set to forward to the next. I look forward to your calls.
Either that or they forgot to modulate the frequency.
If you have lived there you might know SoCal and NorCal are simply in the vernacular.
Oh, sorry, this is slashdot. I forgot to add, "you insensitive clod".
If you have lived there you might know SoCal and NorCal are simply in the vernacular, you insensitive clod.
And in SoCal police chasing cars are broadcast on TV. For the purpose ooooof what exactly? I think the NASA broadcaster should have a shot of tequila before going on the air or should have had several the night before. Certainly would make the broadcast a little more fun. Maybe even give it a pulse.
I'm writing a new song called "Saved by Xenu."
Spend some time in communist Cyprus, where the janitor make the same amount as the hospital administrator. But past his first sentence, the 15 year old is missing the point.
Homeless and injectables or smokeables don't mix. The only time I met ex girlfriend's mother, she was begging on a corner sitting on streams of her own urine. When I told her that "a lovely young woman who reminded me of you wanted you to have this cheeseburger and food vouchers" she looked at me, nodded and then turned and started asking the cars for money.
Keep the hard drugs away from the homeless - like that's possible.
What about "though shalt not steal" does he not understand?
looks like I'm not using my Crackberry for search if that is the case. Thankfully, Google is still an option on mine.
Guess I'll have to actually go to the the Google page to search if this happens.
Animated dead? You mean like Jesus?
Hear hear!
Yeah, we could have told you that.
Whatever happened to the PONIES?!
This shows that Saturn has a magnetic field and magnetic poles. I think this directly implies that the gas giant has a solid or molten iron core.
Time to shoot some radar off that beast and find out where the surface is.
And I've seen two programmers in different companies use 15 page case statements with conditionals within the case statements. It didn't matter if the person was using a verbose language or a sparse language; they didn't understand the concept of wrapper functions, delegation and proper class structure for organization.
One was unfixable due to time constraints and the other ended up being replaced by 5 lines of command routing code, and all the conditional functions moved into appropriate classes.
In these cases, it didn't matter if the language was verbose or not, the programmers simply didn't think there was anything wrong with just making the data organization flat and case statement bigger.
But, in the second incident of this nightmare, where the language was verbose, the problem was much easier to fix, because it was at least easier to understand the code as it was more self documenting.
I blissfully missed COBOL by a few years.
YES. YES. YES. YES.
The code (pretty much) documents itself. Less deciphering what the programmer really meant, especially when you are the programmer and you're looking at your code six months later.
I'd mod you up if I could. Well said.
Why should someone make a language more difficult? Just to raise the bar to becoming a programmer?
I agree that we do need people who really know how to program but does that have to be every programmer and does every language need to be difficult?
Maybe televisions should have never done digital, so I can be an expert in learning how to tune the channel so that my business of channel tuning will stay healthy?
You DO need experienced programmers, and you do need machine language and C/C++. The question is, "do you really need that in every case?"
But isn't "myArray.Add(allItems[1])" visually more confusing?
Illustrated a little, it might look like this:
objectToDoSomethingTo.functionInObject(usingAnotherArrayVariable[itemNumberOfItemInArray])
In the majority of languages today, this is the way things work but doesn't it seem really backasswards when compared to the simple and verbose "put item 1 of allItems into myArray".
To your main point, yes. Yes it is.
Easier, that is.
Why do you feel the need for parenthesis? I find the curly brackets and parens more cumbersome then they are worth in many cases.
I beg to differ. Coding doesn't have to be hard. Debugging is debugging... or is it problem detection and solving? Clarity of your code and clarity of the language structure you are using either helps or hinders debugging.
Part of coding is how good your IDE is in telling you what is going on. Another part is how understandable your code is and that is dependent on the structure of the language you are coding in.
Is it really dumbing down or are the languages that we use more obtuse than necessary? The common syntaxes of the day are left over from language design when every bit mattered. If English-ish syntax is more clear, then why not use it?
Isn't it more about clarity of the language than about shortest code possible?
No, but their marketing department will say they will.