Yes, but still I think that it’s quite fair that as a developer who came to modx after revo was released I never thought of touching evo. I can understand that you can love evo but for majority of new developers which chose modx you don’t expect that they’ll chose a cms that was “discontinued” two years ago. You can’t move forward backwards…it just doesn’t make sense.
Check out blackflow.pl
-
☆ A M B ☆
- 318 Posts
"Speed isn't everything, it's the only thing." -- Brett Tabke (founder of webmasterworld.com).
I'll admit I work Revo pretty hard (multiply nested getResources calls, for example), and with good server resources I can still get great front-end performance -- cached. Uncached... no. Some of my pages take 6 sec to render, even on a big dedicated server. That's a huge limitation. You can work around it, but that means always having to work around it, if you see what I mean -- always looking for ways to cache everything, and only use uncached code when you absolutely have to. It sometimes makes things harder, makes you accept limitations you don't want.
Furthermore, it pretty much means that if you're making heavy modifications to your site, you can kiss a good chunk of your visitors good-bye.
I do have a couple of general suggestions, though I haven't worked out the specifics. It seems like getResources and Wayfinder are the main bottleneck for front-end performance, and that the handling of TVs is the main bottleneck for those. So... would it be possible to either a) set up TVs so that they are real fields on the Resources table, or b) make it significantly easier to set up custom Resource types with real fields instead of TVs so that average users could do that instead of using TVs if they have speed issues?
Another possibility might be to make slimmed-down versions of Wayfinder and getResources with minimal features for simple tasks. I'm not sure how much of a performance boost you'd get from removing features, but it might be worth looking at.
Also... does anyone know why it is that nested calls (calling a snippet within a getResources or Wayfinder template) are so slow? Is there some process that's being repeated, that could perhaps be done only once at the top?
-
☆ A M B ☆
- 3,141 Posts
@blackflow
You are right, your opinion doesnt hold much value.
Once you have used Evo as much as most of the long term Evo users, then you can possibly come back and argue a point.
Till then I would leave such comments.
Whoah, hold it right there! Everyone's opinion is important here, not just those that have been around this community for years! I would argue it's important a strategy is put in place that helps the newcomers as much as those who've been around longer.
[ed. note: markh last edited this post 14 years, 5 months ago.]
-
☆ A M B ☆
- 3,141 Posts
Also... does anyone know why it is that nested calls (calling a snippet within a getResources or Wayfinder template) are so slow? Is there some process that's being repeated, that could perhaps be done only once at the top?
Imagine a menu built with Wayfinder that has 5 top level items with 10 sub items each, that's 50 items. If every item there calls getResources, that's 50 getResources calls. That's simply a lot, and definitely needs to be optimized better.
Another possibility might be to make slimmed-down versions of Wayfinder and getResources with minimal features for simple tasks. I'm not sure how much of a performance boost you'd get from removing features, but it might be worth looking at.
I've started a different menu builder some time ago that is/feels much faster than Wayfinder (no extended benchmarks done yet). It's not done yet as it lacks some critical features, but I hope to get it done and out there soon.
https://github.com/Mark-H/MenuExtended/
@blackflow
Disregarding Evo is not only a problem for people who like Evo for being faster, more efficient etc. its in some cases a financial problem as well.
Are you self employed or work in a company that offers clients MODx as a CMS solution ?
If like many others you are self employed or work for companies offering such services you would possibly have other arguments to why Evo should be supported.
Telling a client that their website is out of date due to the system you chose for them doesnt exactly put a good light on things.
What do you say to your clients:
You:
Ooops sorry, but the system we installed 2 years ago is no longer supported. We have to completely re-build your website and teach you how to use a new system again.
Client: Is this a free update ?
You: No, you have to pay loads of money again
Client: Thanks but no thanks
-
☆ A M B ☆
- 3,141 Posts
@iusemodx, A security fix release (with some improvements) was released just two weeks ago... maybe my definition of "supported" is different than yours? There's also been
official statements in the "Bringing Evo back to life" topic which states:
No one is trying to kill Evolution. We continue providing security patches and integrating quality PRs that make sense for the direction of the MODX brand.
Also regarding your client scenario, I'd like to quote
Ryan's blog post the other day:
Whether it went publicly acknowledged or not, we’ve been listening for months to what’s going on in the community. In summary, we identified a few themes:
* We need to actively re-engage the community, listening and communicating.
* Evo has some great attributes, and it has been neglected.
* Revo also has some great things, but other pieces need work.
* For those that want to try Revo, there’s no straightforward migration path from Evo.
There are more things that could be added to the above list, but these are the ones we’re committing to tackle first.
That's a known pain point and on the list to address.
-
☆ A M B ☆
- 3,141 Posts
Quote from: iusemodx at Apr 06, 2012, 06:17 PMQuote from: markh at Apr 06, 2012, 05:52 PM
Whoah, hold it right there! Everyone's opinion is important here, not just those that have been around this community for years! I would argue it's important a strategy is put in place that helps the newcomers as much as those who've been around longer.
Did you read that post thoroughly ?
Yes.
Do the comments or misplaced comparisons have anything to do with this post:
Quote from: rethrash at Apr 04, 2012, 05:16 PM
What I'd like to discuss, is what is it that makes you love Evo so much. Some of the things we've read before include:
In my humble opinion, yes, as he is offering his view on an arguement brought forward by someone else. I'm not saying the comparisons were accurate, but please let's not tell people to "leave such comments" or that their opinions do not matter.
