2 ms·
One of the major problems within this project are poorly written, slow db queries, MVC is not correctly implemented (although using an MVC-based Framework, func
by dicarsio 16y ago
One of the major problems within this project are poorly written, slow db queries, MVC is not correctly implemented (although using an MVC-based Framework, function names not intuitive. I can improve, refractor some aspects of the code, but the time that will took to fix it can be more than the time to recreate it in another framework. What do you think?
- triviatise 16y agofor me the question is still, what problems is this causing? slow db queries can easily be isolated and unless they have done something like every write to the database creates an object which then gets converted to a sql transaction, function names can be fixed with global search and replace. Not sure what you mean by MVC is not correctly implemented
- dicarsio 16y agoI mean that, model bits are inside controllers, for example :-)
- jtheory 16y agoPoorly-written queries are very easy to refactor -- fix one query at a time, correct indexing strategy gradually, etc. Likewise, function names are ideal to refactor -- many IDEs will automate this for you. I don't know your situation, but this sounds to me more like framework envy (and I base this on experience... I've worked with projects on a lot of crappy and/or homegrown frameworks before). If you haven't actually done any major projects in the newer framework yet, that's a bad sign as well, I'm afraid. :) On a more positive note -- it might be possible to incrementally move to a new framework. It's harder if you want to switch languages/environments completely, but if not, it's probably quite feasible (switch over a feature at a time). If both frameworks can access the same session storage... that's likely the main tricky aspect.