[andy_ppp]

Worth noting that Magento 2 is rewrite that actually uses some proper engineering practices.

No idea how good it is but version 1 was horrifying.

The fact their github has 1274 open issues and 179 open pull request at the time of writing suggest maybe nothing has changed: https://github.com/magento/magento2

[billmalarky]

But none of that matters because Magento 2 still can't serve a dynamic request in less than a second in even the most optimal conditions.

https://blog.amasty.com/magento-1-vs-magento-2-performance-c...

The Magento framework builds static sites with a (slow) dynamic CMS system. It's garbage.

[DelaneyM]

We got it down to an average ~400ms under load with aggressive full page caching (including our own hand-rolled component caching) and edge caching of all static assets (freeing up the servers to be optimized for dynamic content).

This should not be considered an endorsement; getting sub-second pages was a downright herculean engineering effort requiring system-level optimizations beyond what should ever be required of a pre-packaged system.

[billmalarky]

I've spent enough time in highly customized Magento in my day to both be impressed, and deeply concerned for your well-being after such a task.

[DelaneyM]

True that we left before 2.0.

I was excited to hear that 2.0 wasn't backwards-compatible, but apparently (from the community feeds I'm still connected with) things haven't improved much.

The problem seems to be that they just didn't have a deep engineering bench at Magento, and as the red-headed stepchild of eBay a few years after their acquisition they had no way to hire. (I was actually pitched a "CTO of Magento" job at eBay Enterprise a few years ago, but the comp package wouldn't have matched my lead engineers' at the time and most of the dev team was overseas and chosen based on price. It looked like a nightmare.)

edit: Apparently they've since been sold to a private equity firm to be managed for cashflow, which is a common outcome for stagnant enterprise companies with vendor lock-in and rich fees. So much for buying their way out of their code hole.

[pestaa]

> from the community feeds I'm still connected with

Can you please elaborate on what these channels are?

[benmarks]

Indeed, I'd like to know for our benefit.

[benmarks]

The tricky thing about looking at number of issues is that we have a high volume of interaction on the repo as well as a lot of cruft from even before the beta (I'm looking into winnowing these down). I'm spending 50% of my time on the road interacting with developers, and most of what I'm hearing is that M2 is much better to work with for professional PHP developers, but that there are improvements still needed. We're damn lucky to have an engaged community which will help us to constantly improve, assuming we continue to listen to them (which is a big part of my job). We also have our most senior PM overseeing developer experience.

Regarding PRs, this wasn't something we even _did_ before 2015. I wish we could have a quicker acceptance of PRs, but many are not in a proper state to accept - for example, several PRs have CI failures which are the responsibility of the submitter to fix.