It was back 1999 and I was working in a huge project in a Brazilian
Our team was successful to deliver a solution in only 10 months,
whilst the previous responsible for that solution, a consultancy
well known in the entire globe, failed to deliver after 3 years
We were working with a mix of technologies.
I had 10+ years of experience in C and also on a myriad of "stuff"
"invented" by Microsoft.
I was first introduced to Java by a colleague, coming from
Initially, I had a little resistance to hear what a graduate had to
say to me, a experienced C developer.
Straight to the point:
It took me only 15 mins to see the huge potential of the language.
Coincidentally, with sounding resemblance,
I saw very quickly *all* pros and cons already pointed out by Kevin
Wright (copied below). So, I immediately started to push Java every
time it demonstrated possible.
In a nutshell, I've chosen Java because *I was frustrated* with the
current technology and tools at that time.
1. You become better in your game when you "listen" what others have
2. Stop flame wars. Be pragmatic. Evaluate technology from the point
of view of cost/benefit related to what you need now and what you
will need in 5 years time.
I'm frustrated again: this time I'm frustrated with Java.
Unfortunately, I don't believe that Java will address anytime soon
certain aspects I see desirable. But this is another subject, for
another email thread.
mobile : [masked]
Skype: dial skype2ippi then dial[masked] when prompted.
GTalk: dial [address removed] then dial[masked] when prompted.
SIP : dial [address removed]
iNUM : [masked]
On 26/06/12 12:14, Kevin Wright wrote:
My reasoning was nothing quite
so noble :)
It was a simple cost benefit analysis compared to C++,
which is what I had previously used commercially. I had
also used smalltalk and Lisp in a personal capacity, but
there was little demand for Lisp of Smalltalk programmers.
I *had* been exposed to Java at university previously, but
it seemed to be very much a toy language at that time; with
no JIT yet (let alone hotspot) and a mind-boggling startup
- Garbage collection
- No pointer manipulation
- No buffer overflows
- Rich standard library
- Built-in threading primitives (better still after 1.5,
with atomic ops)
- No need to maintain separate header files
- Faster compilation
- The OO was more pure than C++ (though still not
perfect), and interfaces fixed the diamond inheritance
- Availability of jobs
- No templates/generics (The C++ STL continues to be
- No closures or method handles, no higher level
functions (I followed the Sun/MS debate over delegates
very closely). In general, it still misses out on a lot
of these kind of abstractions that can really help
eliminate code duplication.
- No operator overloading (BigInt/BigDecimal has
*always* been ugly!)
This was all before generics, and before the ecosystem
had been established, so I can't class those as pros in my
initial choice. Though they did help reinforce it later
So even then, I liked the platform whereas most of my
reservations were about the language - not that such a
distinction made any sense at the time. Having said that,
the familiarity of the language to C++ devs must surely
have helped adoption and therefore growth of the
On 26 June[masked]:35, Ben Evans
In 1998 I was a starving graduate student in the
and had been making some money by tutoring a disabled
He was due to start working with a new language called
Java, which I
knew next-to-nothing about, but agreed to learn it in
order to stay
ahead of the class and teach him.
Fortunately, I was also writing a monthly column about
tech and the
Internet for the student newspaper, so I knew a bit
engines. I got so into using one of those search
engines, that I
resolved to write about it for my column - and rang up
and spoke to a
couple of guys who'd worked on the search engine -
Larry & Sergey.
Nice guys - I wonder whatever happened to them?
After that, Java was a language that I knew, but it
become my primary focus until a few years later when I
On Mon, Jun 25, 2012 at 9:11 PM, alexander sharma
> I wanted to ask why so many
people decided to work with Java.
> What started their interest in Java. In my case
one of the main reasons was
> most jobs are in java and the pay is better
than for php for example
> creating a "safety" net when looking for a job,
but recently I have started
> working with python and realized that the code
is much easier to read.
> Basically I wanted to know why
different people choose Java as their main
> Technical reasons, code readability, have they
tried and compared other
> languages, what are their backgrounds.
Please Note: If you hit "REPLY", your message
will be sent to everyone on this mailing
list ([address removed])
This message was sent by Kevin Wright
([address removed]) from LJC -
London Java Community.
To learn more about Kevin Wright, visit his/her member
Set my mailing list to email me As
they are sent | In
one daily email | Don't
send me mailing list messages
Meetup, PO Box 4668 #37895 New
York, New York[masked] | [address removed]