If you have heard about Agile Toolkit but haven’t shared with your developer friends yet, now is a great time. This video is a great introduction to the basics of Agile Toolkit starting from the very start. What is Agile Toolkit? Why was it created? What is it best for? How it compares to other Web Frameworks?
Your questions are answered and the guide gives a great taste of what can be done with Agile Toolkit just in a few moments. This is the first podcast in the series with a new episode scheduled every week.
We are recording episodes live and if you are willing to participate and ask questions, here is the link for the second episode event:
Jeff said it, PHP language sucks. But we use it. Why?
- It’s easy to install for new users. It’s a single PHP extension. And in most cases that’s all you need.
- It’s easy to read. Surely some new scary features have been creeping into, but why the hell do I want my integer to be an object?
- It’s fast. Initially PHP was a collection of C routines. It naturally evolved to be a thin layer on top of C with it’s own language parser.
- It’s safe. Problem with one application can’t impact others. No memory leaks. No runaway threads.
- It’s flexible. Diversity and low standards is what makes Agile Toolkit possible to innovate new and exciting ways.
- It’s transparent. You can actually pick the code and be able to follow what’s going on. Try to follow Ruby framework with all the overloading.
- It’s scalable. It encourages developer to think in terms closer to low level languages.
- It is usable on it’s own. You can actually develop web app in PHP without any 3rd party PHP code.
- It gets job done. When a web app needs to be develop quickly for someone, nothing beats PHP.
Different languages serve different purposes. Inconsistency in function naming? Oh, Cmon.