The reality for most people working in software development is using a C (C, C++, Java C# etc) based language talking to a relational database, so if I were you I'd do the following 1. Learn how to do simple projects in a C based language, including how to create make/build files, use the compiler properly etc without the use of a graphical ide. 2. Learn how a relational database works, I don't mean how to administer it, I mean DDL, DML, SQL, etc and a bit of relational theory. 3. Put the first two bits of knowledge together to create more complex projects (this is probably what you will spend most of your coding life doing). 4. Learn to program. This is very different from learning a language and is all about how and when to use data structures, control structures, patterns etc. N.B. This step will take most of your career to accomplish to a high level. I'm sure this comment will get flamed by people doing work with LISP, Ruby, Perl etc, but in my 12 years of experience most of the real world work is done using the stuff above. As to learning app servers, HTML, JavaScript etc, feel free to learn those as well, they're easy to learn and so give you a few quick wins in what is going to be a reasonably taxing task, but don't think these are what programming are about. The interesting stuff is at the backend. Other than that, enjoy it, coding is creative and fun!
I agree that at first the Java installers ran extremely slowly, on the other hand I quickly found out that I could use older (Windows) installer versions as well, which solved the problem for a few years until the Java installers improved.
As for no use for Java anywhere, I'm not a Java zealot but, when I'm writing distributed apps with multiple datasources in a clustered environment, which I tend to do quite a lot, I can't say I've found a better language / set of APIs for it.
WTF! Do you actually have a job or are you 14 and living with your parents? You've obviously got 0 understanding of the real world, or your just too dim to be anything but a script kiddy.
PS. I'm not new here, just fed up with script kiddies;-)
I would suggest that the reason you're getting out of memory exceptions is because your maximum heap size is set too small when you start your JVM. Maybe you should RTFM before you bitch about the product.
Having read that book a few years ago, I can agree that it is an authoritative and exhaustive description of OO software construction. However it must rank as the dullest book on software ever written. BM has no idea about how to write to keep the reader reading and his vitriolic attacks on C++ and Java in the book, along with his extensive explanation of design by contract, show the book should be called 'Why Eiffel is the only true OO language' If you haven't read it, don't bother unless you suffer from insomnia.
If you lived in London, you'd know that it would be perfectly possible to kill someone in the street while everyone walked around you pretending not to notice;-)
Slashdot Mirror
When the architect/designer says 'Great a distributed app, let's use CORBA!'
The reality for most people working in software development is using a C (C, C++, Java C# etc) based language talking to a relational database, so if I were you I'd do the following
1. Learn how to do simple projects in a C based language, including how to create make/build files, use the compiler properly etc without the use of a graphical ide.
2. Learn how a relational database works, I don't mean how to administer it, I mean DDL, DML, SQL, etc and a bit of relational theory.
3. Put the first two bits of knowledge together to create more complex projects (this is probably what you will spend most of your coding life doing).
4. Learn to program. This is very different from learning a language and is all about how and when to use data structures, control structures, patterns etc. N.B. This step will take most of your career to accomplish to a high level.
I'm sure this comment will get flamed by people doing work with LISP, Ruby, Perl etc, but in my 12 years of experience most of the real world work is done using the stuff above.
As to learning app servers, HTML, JavaScript etc, feel free to learn those as well, they're easy to learn and so give you a few quick wins in what is going to be a reasonably taxing task, but don't think these are what programming are about. The interesting stuff is at the backend.
Other than that, enjoy it, coding is creative and fun!
... the magnetic poles reverse the planet ;-)
I agree that at first the Java installers ran extremely slowly, on the other hand I quickly found out that I could use older (Windows) installer versions as well, which solved the problem for a few years until the Java installers improved. As for no use for Java anywhere, I'm not a Java zealot but, when I'm writing distributed apps with multiple datasources in a clustered environment, which I tend to do quite a lot, I can't say I've found a better language / set of APIs for it.
WTF! Do you actually have a job or are you 14 and living with your parents? You've obviously got 0 understanding of the real world, or your just too dim to be anything but a script kiddy. PS. I'm not new here, just fed up with script kiddies ;-)
I would suggest that the reason you're getting out of memory exceptions is because your maximum heap size is set too small when you start your JVM. Maybe you should RTFM before you bitch about the product.
Having read that book a few years ago, I can agree that it is an authoritative and exhaustive description of OO software construction. However it must rank as the dullest book on software ever written. BM has no idea about how to write to keep the reader reading and his vitriolic attacks on C++ and Java in the book, along with his extensive explanation of design by contract, show the book should be called 'Why Eiffel is the only true OO language' If you haven't read it, don't bother unless you suffer from insomnia.
If you lived in London, you'd know that it would be perfectly possible to kill someone in the street while everyone walked around you pretending not to notice ;-)