Forwarding to list again,
On Fri, Jun 20, 2008 at 12:15, Sandip Bhattacharya <[EMAIL PROTECTED]> wrote: > +++ Puneet Lakhina [20/06/08 10:33 +0530]: > >> mailing you only as i didnt wana start another off the topic flame war. >> > > Regardless of that possibility, I believe such discussions provide > perspective to people on the list who are looking at similar ventures. > Also decreases the possibility that my possible misunderstanding of > current market realities affect my advice. Please forward my mail to > ILUGD if I manage to convince you on this. :) I would prefer that you > do. > > > >>> Is the Tomcat/Jboss java stack being looked at only because of the JBPM >>> workflow tool below? By going in for a Java based stack has multiple >>> effects, technical as well as business wise: >>> 1. Your hardware requirements increase dramatically. >>> >> >> Doesnt this depend mainly on the user base and similar things? >> > > It is quite well accepted that an average Java application requires more > expensive hardware spec than a LAMP solution. Would really be glad if someone could give any actual figures/test results. > > 3. The business aspect - how easy is it to get Java talent from the >>> market place and retain them as compared to LAMP? Whatever application >>> you spend your valuable money on, will lock you into the platform that >>> you choose. You can port between Unix OS, but you can't between >>> languages later without significant investments. Are you willing in >>> going that path? >>> >>> >>> This is the question I mainly wanted further discussion on. Java talent. >> Is >> it easy to get? Yes.big time..there are a lot more Java programmers I >> would >> believe than PHP/Perl/Python programmers in India. Retaining them?Could >> you >> please elaborate your reasons on why you think thats difficult/doesnt >> happen? >> > > I think the availability difference between Java programmers and PHP > programmers have decreased over the years. Yeah, but its still huge I would think. Mainly because Java has a wider range of uses and applicability than say PHP. Hence you would find more people who know Java, then teaching them J2ME or J2EE or whatever aint that tough. So the Java pool will always be bigger. I would think thats a positive thing. > > My previous experience with > organizations having Java programmers has been that there is a high > attrition rate. My personal belief is that organizations consuming Java > applications are generally willing to throw their money around :) and > are quite lucrative as a result. As a consequence, service providers > supplying them have more money to recruit people. Also a good market for > such programmers exist abroad. All these contribute to a better > employee's market in Java than LAMP :). > > The flip side is that Java code based service providers are more > vulnerable to market conditions and therefore riskier employers. > > >> Java programmer are the most readily available commodity. How can it be >> tough to recruit them? >> >> > To begin with, they are more expensive to recruit, and salaries (that I > last saw) lie somewhere between (and beyond) their inherent capabilities > and the market rate, if you know what I mean. :) In short, it is more > diffcult for smaller companies and government organizations to compete > with the market for them. > So what you are saying is, get the PHP guy, he is cheap coz nobody wants him, and hel stay coz nobody will want him. > > - Sandip > > -- > Sandip Bhattacharya > http://blog.sandipb.net > -- Puneet http://sahyog.blogspot.com/ Latest Post: javac -g _______________________________________________ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
