The Phalcon Team wishes all of our friends, contributors, developers and users of the framework a Merry Christmas!. We hope that the new year will bring health and happiness to you and your loved ones!
After months of work on v4 (most of them long nights), we are happy to announce the release of Phalcon v4.0.0 Alpha 1 as a small gift to our friends and community for this joyous day.
Phalcon has always had a small development community and not that many pull requests, offering bug fixes and enhancements, compared to other PHP frameworks. This was primarily due to the fact that most developers do not really know C. To help developers contribute, we have created a new language called Zephir, which has a very similar syntax to PHP or Javascript. In 2003 we announced this plan and a few months later we released the language and rewrote all the Phalcon code in Zephir. We have been using Zephir ever since for developing Phalcon.
We have been working hard to ensure that bugs are fixed and v4 is getting close to a release state. As always we would like to thank all of our contributors who have been helping in this effort, as well as everyone on our community sites (forum, discord etc.) for engaging in conversations, sharing criticism and ideas! We couldn’t have made it this far without this input.
We are happy to announce that we have released Phalcon 3.4.2.
This a minor release, focused on bugs mostly.
Just a status update for all of our followers and contributors! As usual, a big thank you to everyone that helps us making Phalcon better!
We always championed transparency, so this blog post is to inform everyone where we are and what decisions we took moving forward - call it a mini roadmap.
We had some requests in the past to localize our documentation for Zephir. Today we are happy to announce that we now have full localization for our Zephir documentation.
For those that do not know, Zephir is the language that Phalcon is written on :) It allows you, the developer, to create PHP extensions using a familiar PHP/Javascript format, without the need to learn C.
We have started an evaluation of all of our github repositories as part of a cleanup process. Some of our repositories were experimental, just to see if things would work. Some are proofs of concept and some are working examples.
However, as our project moves on, it is very often that those experiments proved good or bad, and no longer serve a purpose. Additionally, example repositories tend to not move forward as the project does, and thus become obsolete, or have deprecated code.