Yes, it is planned for Aurora.--Best regards,Eugene ZhuravlevJetBrains, Inc, http://www.intellij.com"Develop with pleasure!""rtrosu" <email@example.com> wrote in message news:22347130.1050684077335.JavaMail.firstname.lastname@example.org...
Well we know it's planned, I think the original question was when can we USE it? :)R
Well we know it's planned, I think the original question was when can we USE it? :)
Cannot say the exact date now, but you'll definitely be able to use it in Aurora release :)--Best regards,Eugene ZhuravlevJetBrains, Inc, http://www.intellij.com"Develop with pleasure!"
Eugene Zhuravlev <email@example.com> wrote:
Cannot say the exact date now, but you'll definitely be able to use it inAurora release :)
I can see that there is somebody "Developing with pleasure". Althoughthe pleasure is not from writing code but from hinting a things ;)Dirk
The only conceivable reason I can imagine that things like aspectJ got in before this is that people at IntelliJ have never had the use of HotSwap!When MS added Debug and continue to Visual C++ everybody I knew thought that was the most valuable feature added in that release it makes some things so much easier!!!!Please Please Please do this soon!!!!
I, uh, am excited too, but I don't think Intellij will plan the order of features implemented based on how valuable the feature is, or how much we want it. All the critical features they planned for this release will probably get in the release, but the order they're exposed to us will be based on ease of implementation, resources, prerequisites, etc.I know, all this is obvious. Just wanted to make sure everyone understands that during EAP, asking "do this next", or "why hasn't this been done yet", is probably a waste of time.
While you may be right about the way IntelliJ does things. They are dead wrong if they don?t do the features that are most important first. You don?t have to buy-in to extreme programming in its entirety to recognize the points that are true no matter how you work. You do the features most valuable to customers first so when the deadline is looming and you must either miss it or cut a feature you don?t end up cutting the one feature the customer would have bought the product for.In my case I need to decide when the extra features are worth the instability of the EAP. With Aridana the feature that won me over was the proper build with real dependency analysis. Hot Swap would convince me to make the move for Eurora. I would think IntelliJ has an interest in getting as many beta testers as they can after all that is part of what the EAP is all about
remember we are getting code at the build level. They are coding all these features in the next release. So no one aurora feature has more priority (imho). They are probably doing features in the order in which makes sense. It would make sense to add generics, aspects and gui builder first because they may use those features to implement the new debugger.
Most likely they think they can implement hot-swap without much difficulty, so therefore, it doesn't need to have much time to "harden". Something like AspectJ, is much more likely to have significant problems that will require large amounts of re-work time. Thus, schedule it early.Mike
And then when something takes longer then they think and they have to cut some features we are stuck with generics that personally I will not use until JDK 1.5 comes out (despite really really wanting to) and with out Hot Swap that I would be using daily!
has jetbrains (aka The Eugene's) ever cut a feature on you?
Well, yes they have. Goto with wildcards was cut from Ariadne I think. It happens.
Please sign in to leave a comment.