Re: Perl vs Java - your feedback, not flames

Kapoor, Nishikant wrote:
> 
> - Backend IS MySQL
> 

> 
> - App is 
>   -- extremely search intensive
>   -- extremely complex algorithms to be used on server side
>   -- no room for slow interface

If you are going to use anything more than simple independent insert/select 
queries, either use Mysql with Innodb (transactional support) or stick to 
Postgresql.

I have burnt my fingers on mysql in my last project, and lack of 
transactional support in the default mysql packages is a big problem. Lack 
of referential integrity is another.

I had been put off by the speed/load factor of Java so much that I stopped 
working in it two years back. Technically it is a great language. But when 
you are evangelizing its usage to potential clients, I got tired of clients 
of saying - "Woh sab to thik hai. But why is it so slow?"? Clients dont 
understand the technical points, they only understand user experience.

On the flip side, I have been using several Java apps for the past few 
months, and to say the least, I have been very impressed with these apps. 
Performance seems to have become very good now. I use Jedit for all coding 
work (ironically, I use it to even code C# for Mono). I use Azureus, and 
love the way Java apps have started integrating with the platform (systray 
integration). These apps all load fast, and I can work comfortably on the 
rest of the system with them running on the background.

However in a server application, the loadup time is not a factor.

What I find puzzling is even though based on the same bytecode/VM 
architecture, Mono is blazing fast running C# programs.

- Sandip



-- 
Sandip Bhattacharya    *    Puroga Technologies   *     sandip-/[email protected]
Work: http://www.puroga.com        *         Home: http://www.sandipb.net

PGP/GPG Signature: 51A4 6C57 4BC6 8C82 6A65 AE78 B1A1 2280 A129 0FF3