I’ve built numerous Magento sites for clients and recently was asked to scope out Magento2 as a serious option for a new build-out. At the end of the day I came back saying, it looks nice, but it’s just not ready. Read on to find out how I arrived at my conclusion.
Closure class in PHP 5.3 you can now pass callbacks to
I’ve been using version control for a long time. I’ve posted on the SVN mailing list and given talks advocating Git. Nowadays it seems the conversion to Git is widespread. It’s being used in corporate settings, but there’s a caveat – it’s still being treated as a centralized system. While folks have made the leap from traditional systems like SVN, they haven’t made the real leap to distributed version control. This has lead me to realize the subtle genius of github.com – they quietly direct you to use distributed workflows and make it as straightforward as possible.
I’m stepping into the Magento realm in version 1.9, lucky me. Turns out they’ve added a new option which allows customers to bypass an extra review step when they decide to pay via PayPal Express. This feature is a bit mysterious though as it doesn’t seem to work all the time, requiring customers to complete a final review step on your Magento site in some cases. Finally I got to the bottom of this and felt it fair to save everyone else the time I spent to understand.
APC & E-Accelerator et al, are great tools to increase performance practically instantly through Op-Code caching. Nowadays OpCode caching is actually built into PHP. But these systems have another common utility that is less frequently used which is the ability to store user variables. These variables are stored in a reserved segment of memory allocated by the extension when the Webserver starts up. Access to these variables is extremely fast since there is no disk or network overhead. Unlike a database, filesystem or network-based store like Memcache, variables created by APC et al in the Webserver SAPI are unavailable to the CLI SAPI.