Why Magento 2 is so popular eCommerce platform?

The answer is simple, the reptiloid alien race has conspired with the NASA and the Ukrainians to torture programmers to the death…

But seriously, Magento 2 is probably the answer.

Magento 2 is the most distressing thing to happen to computing since MS-DOS.

Magento 1 was Simple

When it was first introduced in 2008, Magento 1 was a very simple PHP framework, compared to the Magento 2 monster. At that time, the barrier of entry for writing eCommerce applications was high. Developing eCommerce applications involved writing raw PHP 4.0 code.

When Magento 1 was introduced, it was a no-brainer for many developers and merchants since it was Open Source and free, and could be used across all platforms. Things like built-in orm, models, collection, friendly rest APIs, layouts, and popular PHP language made Magento 1 even more approachable.

Perhaps Magento 1 wouldn’t have been so bad had it not forced OOP on developers. Everything else about Magento seemed pretty good.

What’s happened with Magento 2?

With Magento. 2 inflected eCommerce projects, web stores becomes more verbose, less readable, less descriptive, and harder to modify and maintain.

The most important aspect of software development is keeping the code complexity down. Period.

None of the fancy website features matter if the codebase becomes impossible to maintain. Even 100% test coverage is worth nothing if the codebase becomes too complex and unmaintainable.

Response of the Magento / Adobe team about Magento issues. Magento 2 is to complex to be fixed!

What makes the Magento 2 codebase complex? There are many things to consider, the top offenders are:

• shared mutable state,
• erroneous abstractions,
• boilerplate code
• outdated legacy code
• broken UI architecture

How much unnecessary complexity has been created for the simple act of adding product to cart?

Magento 2 is customizable and flexible?

Here’s what most Magento vendors don’t tell you.

They don’t tell you that you’ll still need developers for fixing the inconsistent code of a mashed-together Magento 2 theme and plugin concoction. They don’t tell you how much this mix will slow your website down or create unintentional conflicts of code, and even leave your website open to greater security risks.

The whole reason that many businesses use a Magento 2 is to lower the cost of front-end developer work and simplify website maintenance, updating, and customization processes.

The reality, though, is that a Magento 2 actually makes all of these processes harder, not easier.

Since Magento 2 has legacy outdated architecture, they often make the whole website build process more technical than it may have been with a website built by a developers using general frameworks like Laravel, Symfony, Django, .Net.

While most businesses would like to sit back and relax after building and organizing their Magento websites, the reality is that they can’t — not if they want to actually protect and maintain their website.

If not hardly maintained — which sort of kills the point of getting the Magento Open Source in the first place — threaten your website’s security, seriously hinder website speed, and restrict necessary customizations.

But that’s only the tip of the iceberg. Magento 2 is overestimated, overadvertised boodle which is about to collapse.