So a lot of people will go unemployed, some businesses go broke. So what? It helps weed out all the fakes, all the "in-it-for-the-big-bucks" jerks.
I'm a computer science student, and I can't begin to describe just how many people are looking to get into this field just for the money. More than 90 % of my fellow students hate programming. No, I'm not exaggerating.
I myself love programming and learning new things about computers and related fields, and I don't care at all about the money. I just love computers - and for people like I hope there will always be jobs
Perhaps this is why huge applications are usually written in languages requiring typecasting, and the "looser" languages are usually relegated to simple task duty.:)
OK, you have a point. A lot of things are "safer" when you have compile-time type checking.
But isn't that usually only necessary when a lot of developers, some of who are inexperienced, are working on the same project?
Java is an OK language for teaching programming basics, but it's just too much bondage and discipline for my taste.
You're forced to do object oriented programming. OK, I can respect that - but Java is not consistent. Everything is not an object, and it's just so damned ugly when you have to wrap an int in an Integer.
Also, it's statically typed. It's so fucking annoying to have to typecast everything - I know I have a damn String - quit holding my fucking hand!
Furthermore, Java's text processing abilites suck so bad, I don't even know where to begin.
Give me Python any day. It can do any job Java can do, and probably better.
No matter what the web looks like in 10 years, we will still have the same kind of problems as we have today with broken compatibility, blatant disregard of standards (90% makes web sites only for explorer), etc.
I'm a comp. sci. student, and I'm constantly amazed that nearly all my fellow students find it boring to learn *anything* about how an operating system or low-level hardware works.
IMO, to have an imformed opinion about how your program works, regardless of the black box your coding for - be it a JVM or whatever, you need to know something general about how it works low-level.
Slashdot Mirror
Hello, I'm AIBO. I have something to say:
*woof* *woof*
ttttttttttttttttttttsss s s s ttttttttttttt ddjddddljsljad eeeeewwwq1 tt
This is boring. I'm hungry.
So a lot of people will go unemployed, some businesses go broke. So what? It helps weed out all the fakes, all the "in-it-for-the-big-bucks" jerks.
I'm a computer science student, and I can't begin to describe just how many people are looking to get into this field just for the money. More than 90 % of my fellow students hate programming. No, I'm not exaggerating.
I myself love programming and learning new things about computers and related fields, and I don't care at all about the money. I just love computers - and for people like I hope there will always be jobs
RMS gotta be behind this...
OK, you have a point. A lot of things are "safer" when you have compile-time type checking.
But isn't that usually only necessary when a lot of developers, some of who are inexperienced, are working on the same project?
Java is an OK language for teaching programming basics, but it's just too much bondage and discipline for my taste.
You're forced to do object oriented programming. OK, I can respect that - but Java is not consistent. Everything is not an object, and it's just so damned ugly when you have to wrap an int in an Integer.
Also, it's statically typed. It's so fucking annoying to have to typecast everything - I know I have a damn String - quit holding my fucking hand!
Furthermore, Java's text processing abilites suck so bad, I don't even know where to begin.
Give me Python any day. It can do any job Java can do, and probably better.
Emacs, of course. Syntax highlighting, integrated compiling, etc.
*puts on flamesuit*
No matter what the web looks like in 10 years, we will still have the same kind of problems as we have today with broken compatibility, blatant disregard of standards (90% makes web sites only for explorer), etc.
...it must be in zombie state
I'm a comp. sci. student, and I'm constantly amazed that nearly all my fellow students find it boring to learn *anything* about how an operating system or low-level hardware works.
IMO, to have an imformed opinion about how your program works, regardless of the black box your coding for - be it a JVM or whatever, you need to know something general about how it works low-level.