Oooopsie!


Kevin takes me to task over my poor design skills.  Take a look over: here


In my defense, i was going for simple and understandable.  Unforunately it turned out in a certain scenario there was also an unfortunate perf impact.  Now, i have drastically improved that running time by profiling and attacking 3 low hanging fruit areas.  A change of only about 10 lines of code total ended up increasing perf by about a factor of 10 here.  However, there are still certain design decisions that could be made for even better performance.  However, i’m somewhat loathe to make the changes given that they will be more complicated and i’m trying not to futz around with the core language service logic as it is quite risky at this point.


Comments (5)

  1. Sean Chase says:

    Cyrus, in Beta 2 the IDE is soooooo much faster and better responsive than Beta 1 (and the CTPs I used). Nice job you guys!!!

  2. RonO says:

    >However, i’m somewhat loathe to make the changes given that they will be more complicated and i’m trying not to futz around with the core language service logic as it is quite risky at this point.

    Can’t you prototype the design changes and run a set of side-by-side regressions over both versions?

  3. CyrusN says:

    Thanks Sean! Glad to hear it!

  4. CyrusN says:

    RonO: "Can’t you prototype the design changes and run a set of side-by-side regressions over both versions?"

    Yes. But i can guarantee that it won’t catch everything. Things will regress without question, and our ability to find out about those regressions is severely limited because of the very little time that’s left.

  5. Sean Chase says:

    Cyrus – No, thank *YOU*. 🙂

    *sigh*

    At the same time I’m left frustrated having to wait until Sept for the RTM for all of this great stuff that I need now! VSS now works over HTTP(S), ASP.NET doesn’t require IIS for development, refactoring, nullable types, better intellisense, generics…stop me any time…I want it now. Gimme gimme gimme!!! 🙂