On Apr 26, 7:29 pm, Wildam Martin <[email protected]> wrote:
> > Although Java is from my point of view the much better language and > has a wider field of application, there are some barriers (for new > developers). For example, for PHP you just need an Apache Web-Server > with PHP enabled. Nearly every web hoster offers that. For a Java web > application your needed stack is usually bigger, e.g. you need Tomcat > and several frameworks. Then there is the problem of which web > application framework to choose. Although I like the choice, the > choice is not so easy. > The same choice exists in the PHP world - ZF, CodeIgniter, Symfony, Cake and others are just the tip of the iceberg a developer might have to wade through in the PHP world if they're looking for a framework. One of the differences I see is that it's quite possible to build up relatively complex *web* applications directly in PHP without needing to resort to one of the aforementioned frameworks. I'm not sure I've run across anyone in the last 10 years who'd actually try to write a moderate (or even small) web application using *just* Java (or Java/ servlets, if you will). > Let's say, PHP is just the way of less obstacles for those who want to > get started as well as up and running quickly. That for sure does not > mean, it is really the best choice. And a lot of things start small > where the developers do not think of scalability right at the > beginning. They need to improve performance and efficiency later. > You *really* have to define what 'best' is, and it's usually defined by the people writing checks (employers, investors, customers, etc). >From a business standpoint, getting *up and running* is usually all that matters. Being 'first to market' is often the difference between capturing early adopters, funding, press, etc and being seen as playing 'catch up'. Yes, performance and scalability matter, but usually not as much on day one. Additionally, there's multiple generations (in web time) of tools and best practices documentation for web applications today that didn't exist 10-12 years ago for all technologies. Most mid-level app developers have a degree of performance and efficiency built in to their frameworks which our digital forefathers fought long and hard to develop. :) Finally, straddling the fence between the worlds of Java and PHP, I can say there's definitely pros and cons to both. A Java friend of mine who moved in to the PHP world last year was (overly) miffed about type checking, but was also markedly impressed with the speed of just 'getting things done' relative to his previous Java experience (especially Java web apps). Likewise, I'm a Grails guy when I can be, and have been able to knock out basic Grails apps in a couple of hours which would have taken 2-3 times as long in PHP. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
