This entry was posted
on Thursday, December 29th, 2005 at 10:26 pm and is filed under Programming.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
OK, I HAVE TO RESPOND TO THIS ONE. I heard this week that you had a “Java Issue” so I was going to hit you up later but this just begs a response. — but not the one you are expecting. I think the best thing that can be said about Java is said in Joel’s article (see original Blog) – that is lazy programmers can use it.
I am SOOOO tired of programmers thinking that increased bandwidth and CPU cycles means they can write shity code and get away with it. The faster stuff goes, the larger more inefficient it seems code gets. I’m not opposed to progress mind you, I just think if more programmers were more aware of what there code was doing and how it impacted the systems it touched we would have less bandwidth consumption, better programs and faster response. I won’t name the 1 billion examples but I probably will post my own blog, as you can tell I have a definite opinion.
So is that an argument for using Java (you should be at a reasonably high level of abstraction to avoid stupid details), and the perf-related issues don’t matter because shitty code is shitty no matter what the language, -or- is that an argument against using Java because a language that high-level and in that kind of sandbox so thoroughly insulates the coder from the underlying programming environment that it’s impossible to develop a close relationship to your platform?
OK, I HAVE TO RESPOND TO THIS ONE. I heard this week that you had a “Java Issue” so I was going to hit you up later but this just begs a response. — but not the one you are expecting. I think the best thing that can be said about Java is said in Joel’s article (see original Blog) – that is lazy programmers can use it.
I am SOOOO tired of programmers thinking that increased bandwidth and CPU cycles means they can write shity code and get away with it. The faster stuff goes, the larger more inefficient it seems code gets. I’m not opposed to progress mind you, I just think if more programmers were more aware of what there code was doing and how it impacted the systems it touched we would have less bandwidth consumption, better programs and faster response. I won’t name the 1 billion examples but I probably will post my own blog, as you can tell I have a definite opinion.
So is that an argument for using Java (you should be at a reasonably high level of abstraction to avoid stupid details), and the perf-related issues don’t matter because shitty code is shitty no matter what the language, -or- is that an argument against using Java because a language that high-level and in that kind of sandbox so thoroughly insulates the coder from the underlying programming environment that it’s impossible to develop a close relationship to your platform?
Definetly an argument against high level languages that further distance the programmer from the underlying environment.