Well, that’s mostly what this post is about.
As you all know, we’ve been developing siwapp for the last years using the symfony 1.4 framework. When we started this project, we did it for a handful of reasons:
- have some fun
- give something back to the “community” (I know it’s not a big “something” , but still it’s something )
- learn , learn, learn.
- and , of course, all the unexpected that comes when you develop in an open environment, with all the users input and contributions.
When planned next siwapp release to be made with the symfony2 framework, we expected to continue learning and of course improving the app. The thing is: we’re struggling a little too much with this. We feel that in symfony 2 it takes too much to put a medium-weight software project up and running. Personally, I’ve learnt a lot about academic programming techniques when working with doctrine2, trying to implement all the models code we had with doctrine1.2, and I’ve enjoyed it, but still the process was being slow.
We already don’t have much time to put into siwapp because of our paying work, so it’s crucial for us to be able to develop quickly. Symfony 2 has gotten too complicated for that. It’s a great framework and this “symfony reloaded” version was meant to be well formed from every possible angle, but it’s not as agile as it used to be.
We also felt we weren’t gaining too much knowledge with it, and as I told you before, this is one of the hard core reasons we started the project in the first place for.
We’ve been playing around with django and node for other projects, and have come to have some training on that, but Ruby on Rails we never had the chance to put our hands on it. On the other hand, there’s a lot of buzz about how quick and easy is to develop in it , so we’ve decided we’re going for it!
The king is dead. Long live the king.
Which are the consequences?
- on the user side: obviously, the app will maintain the same look&feel, no worries about that.
- on the user side: if you happened to have some knowledge of php that allowed you to tweak siwapp in any way, well, for the next version , those of you who are familiar with ruby will have that chance.
- on the developer side: siwapp developers (julian, alex, and a lot more), thank you for your past contributions that of course will remain there, and please join us with the new approach . If you happen to have spend time working for the symfony2 version, well, apologies.
- on everyone’s side: a few months have been lost.
What are we going to do about it?
- we’ll keep exactly the same support in our forums for both the old and new versions of siwapp
- also, when time is right, provide a way to migrate data from the old framework to the new one
- If any of you have a patch or an enhancement for the old version, it shall be welcomed
Please keep in touch! you’ll be hearing from siwapp soon.