| scott wrote: |
| Michael,
Good question. It's actually do to the high demand, which you could then trace back to more hardware needed. We'll be shutting down over the weekend of the 29th to move the site to larger boxes to address the issue. This will certainly increase the capacity during peek load times. Of course the site will never be as fast as static HTML simply because the myeclipseide site is all dynamically generated but it should improve a good bit from where it is now. --Scott MyEclipse Support |
| Quote: |
|
I currently have to install a bunch of plug-ins to get the functionality I need. |
| scott wrote: | ||
Your life just got a LOT easier. Be sure to install it on a CLEAN version of Eclipse 2.1.1 though. We don't want the "plugin soup" you're currently using to interfere. This will also give you a chance to test your old environment and your new MyEclipse environment side by side without risking any disruption. --Scott MyEclipse Support |
| Quote: |
|
Well that was a bit unprofessional. Let him install the plugin soup, just he should not complain about issues where some other plugin is making the problem. |
| Quote: |
|
Your company is being criticized on eclipse-plugins.2y.net guestbooks about being condescending and hostile to Lomboz. |
| Quote: |
|
I think, since your software is supposed to be professionally written and not supposed to take interference from other plugins. If it is, then there is a question of the responsibility of (at least documenting) it. |
| scott wrote: | ||
I think you might be a little oversensitive. If you'll read the thread carefully, neither the original poster nor I mentioned any other products at all. Additionally, I didn't encourage him simply to abandon what he's got now, only to run a parallel test and make an informed decision. This is neither condescending nor hostile to anyone. It is simply good advice on how to perform a parallel test between two products. |
| scott wrote: | ||
Our software is professionally written to the highest standards and conforms to all the Eclipse conventions. Unfortunately, the same cannot be said for all software on the market. Therefore, there may be interaction problems of which we're currently unaware. Since it is impossible to test with every possible plugin mutation currently available, we make suggestions to our users to install on a clean version of Eclipse since this is what we run our validation suites against. Once they're up and running in this configuration, they can then add more plugins, if desired, to further customize their environment; but at their own risk. I hope that clears things up. --Scott MyEclipse Support |