Linked by Thom Holwerda on Sun 20th Apr 2008 15:43 UTC
General Development Geek.com is running an opinion piece on the extensive reliance of programmers today on languages like Java and .NET. The author lambastes the performance penalties that are associated with running code inside virtualised environments, like Java's and .NET's. "It increases the compute burden on the CPU because in order to do something that should only require 1 million instructions (note that on modern CPUs 1 million instructions executes in about one two-thousandths (1/2000) of a second) now takes 200 million instructions. Literally. And while 200 million instructions can execute in about 1/10th of a second, it is still that much slower." The author poses an interesting challenge at the end of his piece - a challenge most OSNews readers will have already taken on. Note: Please note that many OSNews items now have a "read more" where the article in question is discussed in more detail.
Thread beginning with comment 310656
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Right Tool for the task
by Matt Giacomini on Mon 21st Apr 2008 04:48 UTC in reply to "RE: Right Tool for the task"
Matt Giacomini
Member since:
2005-07-06

If you already know C++ you are hardly throwing all your skills out when you move to Java.

I have worked in C++, C#, and Java and I didn't find moving from C++ to Java any harder then moving from C++ to C#.

Edited 2008-04-21 04:50 UTC

Reply Parent Bookmark Score: 2

Doc Pain Member since:
2006-10-08

If you already know C++ you are hardly throwing all your skills out when you move to Java.


You're right. The way from C to C++ may be a bit complicated, but from C++ to Java it isn't that hard. The most important thing when you've learned C++ isn't the language itself - your shills usually are OO-oriented, and you recognize the means of the language, its contructs, its grammar and so on. This knowledge is mostly very generic (!) and you can use it with any further language you like.

A good programmer isn't a person who knows one language from the inside and from the outside, but he's a person who can translate a given problem into an alrorithm, and then map this algorithm onto the desired programming language (or best language for the given task).

Reply Parent Bookmark Score: 2