the bad(maybe?) news.
As everyone may know for the most part, eBay now owns Magento. (at least the details are still being worked out, currently.)
Overall I’ve seen some mixed feelings in regards to this, I myself am pretty up in the air; if it’s a good or bad thing, and I think the only thing that will tell is time.
With all the talk, I’m suspecting a fork or two will show up of Magento granted if the OSL will allow for such which I’m pretty sure it will, long as its made freely available:
With that said, during the developers paradise there was mention that eBay’s X.Commerce package would in fact be “Open Source”.
Inchoo on the acquisition
[warning]…when deep-space exploitation ramps up, it will probably be the megatonic corporations that discover all the new planets and map them. The IBM Stellar Sphere. The Philip Morris Galaxy. Planet Denny’s. Every planet will take on the corporate identity of whoever rapes it first. Budweiser World. ~Chuck Palahniuk, Fight Club, Chapter 23[/warning]
the good news.
The most interesting news was information about a 2.0 version of Magento, I’m going to assume this will be under the new name X.Commerce with eBay ownership. It will NOT be backward compatible with 1.0 and is NOT a rewrite but a refactoring. It is due to release around the middle/end of this year.
The list of new shinny exciting things:
- eregi_replace(“^(.*).js$”,”prototype.js”,”jQuery.js”); // No more Prototype!
- PHP5.3 Native.
- Simpler file structure, no more app/etc/modules I believe.
- GUI Design Editor (WYSIWYG?)
- Class Mapping: No more searching 3 directories of code pools.
- EAV can be optional (for performance I presume).
- A deeper theme fallback support.
- Unit Testing, Selenium, TDD Support.
- Staging before applying any core updates/modules.
- Better server side validation.
- More database options: Oracle, MSSQL, PostgreSQL, etc.
- No more Magic getter/setters.
- More API options: RPC/REST
- Name space collisions detection with advice on how to resolve dependencies.
Magento 2 (in German)