November 13th, 2000, 06:53 PM
My company currently uses WebObjects and I am trying to get them to switch to PHP. Does anyone have experience w/ WebObjects, and if so why should we NOT keep using it?
November 13th, 2000, 07:36 PM
WebObjects is a solid foundation for building solid web applications.
You will require many months to become adept with its object framework. Prior knowledge of PHP, HTML, and other web scripting technology should help you pick up WebObjects, however you will require practice and experience before you will be able to employ WebObjects successfully, to produce the best scalable and portable solution.
Like most other dynamic web page technologies, Web Objects can integrate with the back-end, but you need to know Java or Objective C to create an interface for your web application. Expect a steep learning curve for junior programmers. Once you've become adept at WebObjects, expect web development to be much faster than other technologies due to the well-designed object-oriented architecture. :|
Your progress with WebObjects must typically endure several months of "dedicated" learning and integration experience. You should be working closely with a mentoring senior programmer, who is experienced in WebObjects.
The company that you are working for must have already planned to keep you for a long-term (six months to a year). WebObjects is based on "old", established application development timeframes, so application development times may be longer. So be prepared to work on WebObjects for a longer period than what you would be used to (PHP is fast for prototyping sites).
My advice to you is to learn WebObjects. The experience that you will gleam from WebObjects will enrich and improve your existing PHP programming skills and this can only strengthen your career in IT. While there are benefits to working with PHP, the argument of PHP vs. WebObjects is moot. For a programmer, it is better to be curious than to be ignorant.