rickybobby
2 Nov 2011, 7:28 AM
We have just completed a major upgrade from 3.3 to 4.0 and of course we are seeing performance problems with IE, this is fine, to be expected and we know they’ll be resolved. However, we can’t release this to our customers until performance problems are rectified. 2 quick questions that will really really help us out:
1) We are still using the compatibility pack. Will doing a “complete” upgrade without the compat pack show us gains in performance? If so, do you have an idea as to what the performance gains would be?
2) In order to schedule with our customers, support, build-team and developers, do you have an approximate time frame when 4.1 will be released? Even if it’s +/- 3 weeks, that is a big help. Will it be in the next 2 months? Further out than that?
We love the new 4.x architecture, we are using it to take advantage of the great charting abilities you have implemented. The architecture and new features are a dream. The inheritance model, the mixins, the class structure with statics, singletons, it’s just an amazing boon to our architecture and allows us to be much more OOP, more organized and develop not only more clearly but faster! We can’t wait to set aside some time to go 4.x completely and use “required” to make the dependency chain clean and clear. Thanks for such a well thought-out piece of software, you guys are true visionaries.
1) We are still using the compatibility pack. Will doing a “complete” upgrade without the compat pack show us gains in performance? If so, do you have an idea as to what the performance gains would be?
2) In order to schedule with our customers, support, build-team and developers, do you have an approximate time frame when 4.1 will be released? Even if it’s +/- 3 weeks, that is a big help. Will it be in the next 2 months? Further out than that?
We love the new 4.x architecture, we are using it to take advantage of the great charting abilities you have implemented. The architecture and new features are a dream. The inheritance model, the mixins, the class structure with statics, singletons, it’s just an amazing boon to our architecture and allows us to be much more OOP, more organized and develop not only more clearly but faster! We can’t wait to set aside some time to go 4.x completely and use “required” to make the dependency chain clean and clear. Thanks for such a well thought-out piece of software, you guys are true visionaries.