|
If you are calling the old way of doing things spaghetti code, I call this way rice code.
I’m loving the analogies in this thread! wouldn’t usually add to a gripe so lets start by saying how great I think Magento is...its great!...now on with the rant. I haven’t really posted in a while its just a dodgy 1.1.1 upgrade has brought me back to the community to try and get answers and its nice to know your not the only one with doubts.
I don’t mind learning a complex structure etc its just when it gets changed so significantly on each upgrade across the MVC stack you start to feel a little bit downhearted. I know source has to change for improvements but I thought the idea behind separating views and logic is that the logic can update independently from the views, allowing for easy upgrades. I have noticed significant changes in the way that variables are being called in the templates, rendering my custom ones useless....maybe this is an argument against using PHP in templates as the temptation to change logic for PHP developers is just to great and therefore it might as well be one of the controllers.
Also interesting the talk in this thread about other MVC frameworks, I’m starting to wonder if this is something common to PHP (runs for cover!), Working on other projects recently I have been using cakePHP and found it way too unstable when layering lots of the inbuilt functionality which led me to look at other options, even other languages, I looked at CI but whilst it looked very clean and lightweight it lacked simple stuff like a proper ORM (correct me if I’m wrong), I expect once they develop that it too will become larger, slower and less clean. Then I downloaded and installed Django recently and could do in 5 minutes what took 2 weeks in cakePHP, but this is just my experience. anyhow back to rebuilding my site......
.....oh i forgot the analogy… Magento is like a.....hang on I’ll think of one in a minute
|