4 ms·

Anyone have a cache? EDIT: here it is. No infringement intended. Magento has been in decline since Varien sold to eBay. Magento Community Edition is dead. Ma

Anyone have a cache? EDIT: here it is. No infringement intended. Magento has been in decline since Varien sold to eBay. Magento Community Edition is dead. Magento Go is a failure surpassed by Shopify. Magento CE releases have dried up. So now what? Magento 2.0 sounds promising. However, Magento 2.0 is lead by developers-only. No marketeers are involved to communicate merchant needs. I have tested Magento 2.0 dev60 and it is nothing more than a technical rewrite. Magento 2 offers the same feature set as Magento 1. You'll just need to pay a developer to migrate all your 1.x extensions to 2.x, since there is no upgrade path. But the community cost of everyone moving to Magento 2.0 ranges in the $USD 1 billion. This is how developers keep themselves employed: by regularly clusterfucking your code. A developer focus on Magento 2.0 gives us jQuery, OWASP security policies, faster product imports, better performance and less CSS. But it does nothing to advance merchant's needs. Magento is missing a most important suite of marketing and sales automation tools. Here is some features online merchants really dream about: built-in A/B testing; integrated social media ROI tracking (e.g. SumAll statistics); sales automation tools: abandoned cart reports, automated follow-up emails, automated payment reminders; consumer behavior profiling to live-target marketing efforts based on behavior; customer persona segmentation such as "single men / mothers with children / affluent customers", to increase marketing effectiveness; easy-to-use multi-site and multilingual installations (Magento is cumbersome); helpdesk ticketing system, built-in live chat; built-in onestepcheckout; automated SEO using artificial intelligence; scheduled product imports to update product prices, stock, images attributes - including the ability to create new products and disable out-of-stock products; automatic product categorization based on product description content; social ecommerce ("share this product" with product landing pages for Facebook/Twitter); clever discounts such as bundled product discounts: "buy A+B together, get 5% discount on B"; built-in product XML/CSV exports for ciao, kelkoo, thefind, google and so forth; built-in newsletter or at the very least built-in Mailchimp support (with automatic setup); None of the above features are going to be implemented in Magento 2.0. What is the incentive to move to Magento 2.0? There is none. Do merchants really need the latest gimmicky "html5" technology? Mercahnts need a suite of sales and marketing tools that help drive their business. So again, like before Magento, there is a huge market potential for ecommerce software that offers the right marketing tools. Magento is dead. But who will bridge the gap? Shopfiy? Wordpress Woocommerce? Drupal Commerce? Each of these new projects is gaining on Magento's lead. My prediction is that Magento 1.x adoption has peaked and Magento 2.x adoption will never happen. Instead, The People will switch to far more advanced alternatives. Advanced in terms of marketing that is, not jQuery.

ForHackernews 13y ago
It was probably running on Magento.
- Isofarro 13y ago
  From the favicon on the site, looked like Drupal.
  - ceejayoz 13y ago
    The /node/id style URLs are a pretty good giveaway, too.
pistle 13y ago
I wish this was how the lion's share of articles were re-aggregated. Thanks
madaxe_again 13y ago
The problem with Magento, like so many other OSS eCommerce platforms, is that of extensibility (or lack thereof), and the ensuing technical debt. We've been making eCommerce solutions (not just sites - CRM, warehouse management, analytics, lots and lots of marketing tools) for nearly a decade now. We started out with OsC, played with Magento, and saw, 8 years ago, that the strategy of these platforms was, well, broken. How? Well. Let's consider the typical scenario. Joe sells kites. Joe wants a website that helps him sell kites. Magento looks like it does what he wants, as it's got a cart and all that stuff. Joe finds a contractor who looks good, and has decent references from his current clients. They start work. Part way through the build, Joe realises that he wants to sell custom-printed kites, and to do this, he needs to take a deposit, and then charge the customer the balance. "Uh-oh", thinks the developer, "I'm on fixed costs, and there's no plugin for that. The architecture is a nightmare... screw it, I'll just chuck it in the core and worry about it later". Joe is happy, as his site does what he needs it to, and the developer is happy because he got paid. Six months later, Joe reads about a security update, and wants to apply it. His developer sucks his teeth, and applies it, manually re-patching in his previous hack, because making a plugin is hard, m'kay (never mind that in many scenarios, you can't make a plugin to make whatever you need to happen, happen). Joe wants another addition, and another hack is born. This cycle continues for a while, until the developer fears looking at Joe's code-base, and Joe is pissed off that everything takes a long time, and that upgrades can't be done/take forever, because the developer is having to re-implement, and re-implement, and re-implement, rather than move forwards. The other side of this is that a magento install will run a magento site - not ten, not two on different databases, and no mix-and-match of either, meaning that you end up with a whole bunch of code-bases, many of which differ, even if you're a shop exclusively running magento for your N clients. It's not clear who Magento is built for. It's not for developers, as it's painful to work with... it's not for the end user, as the front-end experience is so-so at best, and again, hard to customise without screwing up upgradability... and it's definitely not for the merchant, as it's featureless, barren, slow, and ultimately expensive to run. So what we did was build an eCommerce platform where everything is extensible and overridable. Core method doesn't quite do what you want? Not a problem, write a client-specific one, just keep your interfaces consistent, and you won't break maintainability. You can upgrade the core with impunity. You can hang as many sites as you can grind out off a single install. We deploy continuously. As a result, we've been able to focus on building features marketeers and merchandisers want, by being able to build something once, respond quickly to market and client demands, and roll it out widely with minimal effort - rather than being stuck on the terminal treadmill of broken upgrade paths.

ForHackernews 13y ago

It was probably running on Magento.

Isofarro 13y ago
From the favicon on the site, looked like Drupal.
- ceejayoz 13y ago
  The /node/id style URLs are a pretty good giveaway, too.

pistle 13y ago

I wish this was how the lion's share of articles were re-aggregated. Thanks

madaxe_again 13y ago

The problem with Magento, like so many other OSS eCommerce platforms, is that of extensibility (or lack thereof), and the ensuing technical debt. We've been making eCommerce solutions (not just sites - CRM, warehouse management, analytics, lots and lots of marketing tools) for nearly a decade now. We started out with OsC, played with Magento, and saw, 8 years ago, that the strategy of these platforms was, well, broken. How? Well. Let's consider the typical scenario. Joe sells kites. Joe wants a website that helps him sell kites. Magento looks like it does what he wants, as it's got a cart and all that stuff. Joe finds a contractor who looks good, and has decent references from his current clients. They start work. Part way through the build, Joe realises that he wants to sell custom-printed kites, and to do this, he needs to take a deposit, and then charge the customer the balance. "Uh-oh", thinks the developer, "I'm on fixed costs, and there's no plugin for that. The architecture is a nightmare... screw it, I'll just chuck it in the core and worry about it later". Joe is happy, as his site does what he needs it to, and the developer is happy because he got paid. Six months later, Joe reads about a security update, and wants to apply it. His developer sucks his teeth, and applies it, manually re-patching in his previous hack, because making a plugin is hard, m'kay (never mind that in many scenarios, you can't make a plugin to make whatever you need to happen, happen). Joe wants another addition, and another hack is born. This cycle continues for a while, until the developer fears looking at Joe's code-base, and Joe is pissed off that everything takes a long time, and that upgrades can't be done/take forever, because the developer is having to re-implement, and re-implement, and re-implement, rather than move forwards. The other side of this is that a magento install will run a magento site - not ten, not two on different databases, and no mix-and-match of either, meaning that you end up with a whole bunch of code-bases, many of which differ, even if you're a shop exclusively running magento for your N clients. It's not clear who Magento is built for. It's not for developers, as it's painful to work with... it's not for the end user, as the front-end experience is so-so at best, and again, hard to customise without screwing up upgradability... and it's definitely not for the merchant, as it's featureless, barren, slow, and ultimately expensive to run. So what we did was build an eCommerce platform where everything is extensible and overridable. Core method doesn't quite do what you want? Not a problem, write a client-specific one, just keep your interfaces consistent, and you won't break maintainability. You can upgrade the core with impunity. You can hang as many sites as you can grind out off a single install. We deploy continuously. As a result, we've been able to focus on building features marketeers and merchandisers want, by being able to build something once, respond quickly to market and client demands, and roll it out widely with minimal effort - rather than being stuck on the terminal treadmill of broken upgrade paths.