5 ms·
Unless it got significantly better/redesigned in the last couple of years, Magento is a piece of junk. Arguably it's been years since I worked with it, but ins
by mrweasel 12y ago
Unless it got significantly better/redesigned in the last couple of years, Magento is a piece of junk.
Arguably it's been years since I worked with it, but installation was weird, developing is slow a cumbersome, documentation was lacking, search was pretty much broken and it was slow. I can't image running it on a shared host, performance must be terrible.
On the positive side Magento does have an impressive amount of features.
- Navarr 12y agoThe team has been working on a rewrite "Magento 2" that should alleviate most of the complaints of the original Magento and adopts PHP development best practices (composer, etc). I also asked them to clarify the versioning scheme[1] specifically related to patches, etc. It sounds like it should be better, but it's hard to tell at this early stage. They've also taken a radically different approach to documentation with Magento 2. [2] [1]: https://github.com/magento/magento2/issues/1051 https://github.com/magento/magento2/issues/1051 [2]: http://devdocs.magento.com/ http://devdocs.magento.com/
- davidgerard 12y agoAre they still taking the "lucky sevens" approach to file permissions?
- benmarks 12y agoSee my comment above.
- jlas 12y agoMagento code in general is of very dubious quality. I once ran a quick static analysis on it and found some ridiculous results: https://twitter.com/jlas_/status/391615992473722880 https://twitter.com/jlas_/status/391615992473722880
- mrweasel 12y agoThat's somewhat terrifying
- mahouse 12y agoSorry, but what is that tool?
- jlas 12y agoIt was a while ago but I think it was PHPMD: http://phpmd.org/rules/codesize.html http://phpmd.org/rules/codesize.html
- Someone1234 12y agoWhile it could be better written, that's just their installer, it doesn't run in production by its very nature so might be a low priority for coding standards. If you wanted to call them out, at least call them out for something which actually runs during normal operation.
- davidgerard 12y agoWhoever wrote Magento thinks 777 permissions are ever the right thing to do. Every book I've ever seen on Magento seems to think the same. That 777 permissions are just not a big deal.
- benmarks 12y agoFrom http://devdocs.magento.com/guides/m1x/install/installer-privileges_before.html http://devdocs.magento.com/guides/m1x/install/installer-priv... : "All directories have 700 permissions (drwx------). 700 permissions give full control (that is, read/write/execute) to the owner and no permissions to anyone else. "All files have 600 permissions (-rw-------)."
- davidgerard 12y agoFrom the Magento Enterprise tarball, which we pay enormous sums of money for: https://news.ycombinator.com/item?id=9417235 https://news.ycombinator.com/item?id=9417235
- jjoe 12y agoIts performance is so scant one must cache it to oblivion. This is especially true when you hit a certain high SKU threshold. Not to mention the horrible modules that are out there in the market. Plug: Had to write a full page caching mechanism that's powered by Varnish (dubbed Magento Warp - http://www.unixy.net/varnish/ http://www.unixy.net/varnish/ ).
- vhost- 12y agoI did the ops-side of a large Magento site. It was a fucking nightmare... and I handled .NET and Java once too. We had 3 cache servers with 128GB of ram EACH just to cache the complete shit out of Magento pages. Each user had their own keyspace in the cache. _that's_ how bad Magento is. When cache would go down because of a network partition or something, Magento would fallback to rendering and our application web servers would melt.
- madaxe_again 12y agoEach user... So one for "not logged in" and one for each known id? That's the laziest possible implementation that can provide any variety of benefit. Caching on a per-actual-visitor basis is just a waste of ram. Fwiw we partial view cache on our platform and achieve a 90%+ hit rate on most sites. Some run many user-variable-specific (referrer,cookie,stored data) site versions which drops the cache hit rate, but is worth the extra cpu and cost for the conversions. Little performance hit as the object data to render is already in memcached usually, pre-warmed by queued parallel processes. Of course, we evolved this in response to "oh crap the web tier is burning", but I just can't comprehend how magento haven't come up with something better than what you describe. Perhaps they haven't experienced the pain of clients bearing down hard on you while Rome burns first hand, and don't understand the importance.
- vhost- 12y agoTheir answer was "oh shit, EAV is cool until it sucks, lets make flat tables". Those flat tables really don't help much... (just profile the a request made to them and you still see the insanity that kcachegrind can generate). They also didn't think about stores that have a lot of attributes. We had over 650. That means we had MySQL tables with 650+ columns. Then there are SKUs. We had hundreds of thousands. Now there are HUGE tables with LOTS of columns that needs to be indexed on a regular basis because products and more attributes are being added. Reindexing takes hours. Magento is a mess and that's all I have to say about it.
- dhagz 12y agoIt hasn't changed much. My company tried using it to build a store for a client since it's what her distribution house recommended. It's trash. We spent more time trying to get a theme to load properly than we did actually working on the theme.
- Raphmedia 12y agoIt's not that bad once you wrap your head around it. That being said, it's getting old, and it shows. They have built up as much as they could, and right now we have a tower that might drop at anytime. Magento 2 will solve this.
- nightclubsub 12y agoIt's not, developers just bear with it because they don't know of better alternatives. Magento is a monolith and always will be. It's built on top of PHP's slowest framework, Zend which doesn't advertise speed but rather raw power. Magento is going to crumble, it's just a matter of when
- Raphmedia 12y agoOkay, let's me phrase it this way then. It's a big piece of weird code that isn't intuitive at first but become relatively easy to work with once you understand what's happening (give up on the why, half the stuff makes no sense). The current version is going to crumble, but hopefully Magento 2 will be built to last.
- benmarks 12y agoNot really accurate to say that Magento is "built on top of... Zend." We don't use much of it. Regarding the crumbling comment... well, Magento is seven years old. There's a reason we're releasing Magento 2. Code's on GitHub, PRs welcome: http://github.com/magento/magento2/ http://github.com/magento/magento2/
- madaxe_again 12y agoThe sad thing is that they learned nothing from oscommerce. Yes, it's not a procedural pile, but it suffers from the same "can't implement sensibly. Fuck it, edit core. Patch?! Shit. Upgrade path broken" phenomenon in heaps. If I got paid every time someone ditched magento because it doesn't perform, is hard and costly to host/maintain, gets blind alley'd by "someone else's problem" developers, can't do what they need, I'd be a rich man. Oh wait, I do, and I am.
- mrweasel 12y agoThere are a large number of jobs for Magento developers in my area right now, some of them are really interesting companies. Sadly I won't be applying because I can't see myself doing Magento again. Maybe I should apply and talk them out of Magento, so I too can become a rich man :-)
- kevando 12y agoIt really isn't that difficult to avoid core updates. Sure, it isn't a perfect platform, but it gets the job done for most eCommerce companies
- mgkimsal 12y agomany things "get the job done", but it's the nature of that "job" and how much effort it takes which is in question.
- lukedev 12y agoBut you're not supposed to edit core, you extend it.
- davidgerard 12y agoAnd that's the gap between "supposed to" and "need to". So instead we cobble a pile of handcrufted PHP to work around its gross defects, given that maintaining our own patchset is making an even bigger rod for our own backs than running Magento itself is.
- billmalarky 12y agoNothing has changed, it's pure garbage.
- davidgerard 12y agoConsidering their apparently sorcerous power to get the money people to sign cheques, I really wonder what the hell they do in the sales presentation for this pile of rancid garbage.
- benmarks 12y agoSpeaking to your points, in turn: > Magento is a piece of junk Commerce is hard. Making an extensible commerce platform for all/most merchants is even harder. These two reasons are why there aren't a lot of options in the open source PHP-based eCommerce application space. Redesign (Magento 2) will be released in Q4 of this year (2015). Beta code is available on GitHub and we are accepting PRs: https://github.com/magento/magento2/ https://github.com/magento/magento2/ > installation was weird How was installation "weird" when you were using it? > developing is slow a cumbersome Speed of development depends on knowledge of architectural conventions, not unlike getting started with Symfony, Zend, Laravel, etc. > documentation was lacking I started building Magento projects in 2008. Documentation was non-existent for a long time (unfortunate given the esotericism of the app). We're solving this for Magento 2 by having tech writers on staff and by soliciting community help (docs are also on GitHub, PRs accepted): https://github.com/magento/devdocs https://github.com/magento/devdocs > search was pretty much broken and it was slow Search and newsletters are insufficient for anything but the most basic needs. That's why there are so many SaaS search vendors filling this space quite well via free extensions. > on a shared host, performance must be terrible Shared hosts are never appropriate for commerce sites due to security reasons. There are a number of specialized small business hosts which run < $50 / month. For shops lacking that budget, well, there will be challenges in general.