Java morphs into C++
First we got generics and printf.
printf is a holdover from the C era. And while I won't want to get into an argument about how useful templates and metaprogramming really is, it's probably one of the most hated (or feared) elements of modern C++ (along with memory allocation).
What's next ? friend functions.
Reminds me of that old joke about English being the official language of the EU, but needing a few "minor" changes.
Will we wake up in ten years and find that the wheel has been reinvented ? Again ?
printf is a holdover from the C era. And while I won't want to get into an argument about how useful templates and metaprogramming really is, it's probably one of the most hated (or feared) elements of modern C++ (along with memory allocation).
What's next ? friend functions.
Reminds me of that old joke about English being the official language of the EU, but needing a few "minor" changes.
Will we wake up in ten years and find that the wheel has been reinvented ? Again ?
2 Comments:
At 8:47 AM,
88Pro said…
Hmmm. True, lot of things Java is introducing are not ground breaking but rather existing best practices. J2SE 5.0 almost looks like a version released to catch up with C#. Also there seems to be quite a lot of differences between C#, Java and C++ Templates when it comes to Generics.
The first person to start research about Attributes in Java was Ted and he had a paper at JavaGeeks.com (which has been removed now). As for Meta programming (Attributes), my opinion is, J2EE is going to need loads of it. This may be one of the main reasons why XDoclet became a popular project. At least it will take the XML Configuration files nightmare from J2EE project.
http://www.neward.net/ted/weblog/index.jsp?date=20040810#1092168023420http://www.neward.net/ted/weblog/index.jsp?date=20031109
At 8:30 PM,
longdeparted said…
I guess the point I wanted to make here (but didn't) is that there are a variety of opinions on what constitutes best practices, and that just adds to the perceived bloat in a language.
Being a Perl person, I shouldn't really be talking about making a redundant syntax, with several ways to perform the same job. But for me, Java never ever filled the same niche as Perl. So it's a concern. I want enterprise languages to follow the KISS principle. Simple as possible, so that many people can understand someone else's code without mysterious side effects or arcane certification level knowledge of syntax.
Perhaps I've read my history wrong, but C++ wasn't unpopular simply because of it's explicit memory management, was it ? :)
Post a Comment
<< Home