[Ilugc] Comparing programing languages [was: perl OO]
- From: rajanvn@xxxxxxxxx (Natarajan V)
- Date: Sun, 4 Dec 2011 09:46:30 +0530
On Sat, Dec 3, 2011 at 9:15 PM, Suraj Kumar <suraj at careergear.in> wrote:
On Sat, Dec 3, 2011 at 4:52 PM, Girish Venkatachalam <
girishvenkatachalam at gmail.com> wrote:
I would partially agree with you that object oriented programming (the way
it is done in Java) makes it possible for anybody and everybody to "get
their job done" -
I think, we are comparing Apples and Oranges here. (See below)
which is also bad from the point of view of building
teams and organizations
I beg to disagree here. Perl, C++ and Java were created for different
purposes/problem spaces. It would be better if we choose the right
tools for the right purpose. PERL/ C++ / Java have inbuilt libraries
and constructs for different purposes. So if in their solution space,
they find that "A" is very repetitive, they build a library/construct
for that. If PERL thinks "A" is not the problem, but "B" is, you get a
different building block in PERL. So, when you use PERL/Java/C++ you
should know what building blocks are available, and what aren't. Then
fill the gaps with your brains.
A house can be constructed using wood, clay, clay bricks, hollow block
bricks, steel and glass, etc... The problem is same. The solution
space is different. The problem that needs to be addressed by the
developer differs. He will have a different set of problems to solve
in each of the solution spaces.
As I said in one of my previous mails, A language is just a language.
Its your ideas that become programs. If I allow any North Indian
Politician to contest in elections in Tamil Nadu, would s/he not talk
a few words in Tamil? Frankly, its not very different in programming
languages.
Each language has its own nuances and abilities. A "good" programmer
will try to utilize the tools to the best possible extent.
//??????????? ???????? ??????//
From a hiring perspective, am not sure why people are obsessed with
the mastery over the syntax of the languages. This also creates a
problem, when you frame a question that is applicable for PERL and not
very applicable for Java. We have to understand that programmers are
not a single breed. Everyone specializes/has interests in particular
areas.You can't compare a OS programmer, with a Game developer, with
an enterprise application developer, with a mashup developer (What is
a Mash up?). Am sure the Mashup developer would have the least clue of
what it takes to sort objects in Java/ Perl.
(very difficult to gauge one's programming /
analytical capabilities). Perl, that way, is a very useful tool for
filtering out and hiring the best.
IMHO, the problem isn't with Java/Perl, its a problem with your
question paper / interview panel. As I said earlier, a language is
independent of analytical skills. Why not frame your questions in such
a way that they don't have to write programs, but provide you with
algorithms instead?
But in perl it is nice and simple.
Let me fix it for you, "But PERL is nice and simple " :-)
--
Natarajan
Other related posts: