4 ms·
The 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, ed
by madaxe_again 12y ago
The 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.