Finally PHP 4 is approaching its end of life. With the upcoming PHP 4.4.8 release, development on PHP 4 will be officially stopped. No more release will be shipped to end user. This is not very fresh news since this has been announced on php.net since July 2007.
Conquering Reluctancy To Upgrade
As open source project, PHP has enjoyed its growth through the support of its enthusiasts, name them web hosts and application developers, not to mention the wide use from end-users. Referring to Google Trends, PHP scores the second lagging behind java as the most queried programming languages. This comparison is taken as simple as possible, neglecting the most appropriate functional environment of each language.
Although the trend can’t lead us into final conclusion on the future of PHP, it’s interesting that just like other programming languages, PHP trend is negative. This may lead to additional question whether PHP still keeps or expands its audience or starts losing its grip.
Until jquery comes.. (and you must believe me, I’m not associated with jquery team. I’m an independent writer).
July 1st, 2007 is a monumental day for Zend and their developers. It’s the day when Zend Framework 1.0, the first stable version of the framework, was released to public. What’s with the fuss?
It’s important for a business entity (eg. company) to make sure the business process run smoothly and profitable during the whole cycle. A lot of components are involved in company operation which determine company success, one of them is software (yes, we’re talking about modern companies). For technology-driven company, software provision and implementation is crucial. Software is not only for administration use, it solidifies and improves business process.
Now we’ll get the scope smaller by emphasizing software lifecycle processes on companies which provide web-based service or consider web existence as business image. Serious companies follow certain standard in its operation. By using standard, it will be able to measure the whole process and assess whether the operations succeeded and desired outcome achieved. Talking about software cycle, there are several evolving models used to reflect the software cycle, from the old Waterfall model to international standard ISO/IEC 12207.
This is the first part of an article duo about open source. This article is inspired by recent policy stipulated by the Joomla team that all joomla modules and components must comply GPL license, the license Joomla has been using since the announcement of its first official release in 2005.
In 2004, I attended a one day seminar about GPL license and the spirit behind open source community entitled “Free Software: Past, Present and Future”. Richard Stallman, the father behind GNU, took the lead as a key speaker. It was an interesting session. Besides the material, Stallman himself was an eccentric person for me. He came and did speech with long hair, t-shirt, and torn jeans. He reflected the word “freedom” itself. Did you see a glimpse of the word “renegade” coincidentally?
Free Is Not Totally Free
The word free has different meanings. If one cares to look up all definitions in dictionary, free is limited to certain terms although it generally means no limitation. From this interesting fact, let’s dig what public assumption is about free software.
In daily practice, free software is often associated with freeware. In fact they are a bit different. Citing wikipedia, freeware is copyrighted computer software which is made available for use free of charge, for an unlimited time. The keyword here is “free of charge”. This is the critical point which oftentimes misleads users with free software.
Can Zend Framework do you a favor? Does it taste different flavour? If you ask me, the answer is yes.
As Zend Framework (ZF) is on its steady pace to the first stable release, more and more applications are [being] developed on ZF. This is also intriguing me to create some applications which are driven by ZF.
Fortunately, I was offered to create a system for managing final projects in my past department (it’s now recognized as School of Informatics and Electrical Engineering). Considering this as a perfect chance to show properly designed academic software and as a pilot project for other ZF-based applications, I took the opportunity and started developing the application.
Figure 1 Sample user’s frontend view
The application itself is mainly another CRUD application with some remote calls to fetch academic data located at different servers. The remote call API is customized to suit the department’s need. Currently it still relies on POST and GET based supplied parameters. However, it’s likely a custom XML API will be developed to handle the web service.