5 comments
Comment actions Permalink

I want tools that increase my productivity but it should NOT slow me down.
As a developer you want to fastest computer available to work on because you
don't like staring at the glass hour. When you click on a shortcut you want
this program to be open instanenously. This is also the reason why Microsoft
is building into Windows such features as pre-fetching, that is the reason
why we use multi-threading and so on. The responsiveness of the system is a
very important issue for a lot of computer users out there. If you are used
to the fact that Visual Studio 2005 is up and running one second after
clicking on the shortcut then you don't like the fact that a tool that
icreases your refactoring productivity turns that one second into 15 seconds
(depending on the machine specs).

Gabriel Lozano-Morán


"Ed Chapel" <echapel@crosscurrentinc.com> wrote in message
news:106baec85c5a8c8a3a255384458@news.jetbrains.com...
>I think Richard has the optomistic perspective. R# does provides a ton of
>functionality and enhances productivity. I don't understand why someone
>would assert that R# should load faster. The complaint is purely
>subjective... how do you measure when R# is fast enough? Certainly a
>professional relying on R# can see even a few minutes into the future to
>realize the benefits of waiting 10-30 seconds for R# to start up.
>

My two cetns...

>

Ed

>

Hello Tamir,

>
>> No, you're right -- but so are the others.
>>
>> Yes, R# is a great tool that helps productivity when used correctly.
>>
>> No, that doesn't mean it's OK for it to slow you down in all those
>> other times.
>>
>> Sometimes you open VS and stare for 30 seconds -- in those cases, R#
>> can take 10 of them and that's fine. But sometimes you would like to
>> go straight to a specific line of code, and have to wait 10 seconds
>> for VS to open, and it's annoying.
>>
>> Sometimes you're typing in a switch statement (or whatever) and R# can
>> save you many keys. But sometimes all you do is change an assembly
>> reference, and R# grinds your machine away for a while.
>>
>> R# is a productivity tool; anything it does to increase productivity
>> is a blessing, but anything it does to decrease it is a curse. Each
>> developer decides for him/herself if there's a net gain there (hey,
>> it's worth it in my book), but the friendly folks at jetbrains should
>> be aware of anything that weighs on that decision.
>>
>> Tamir Nitzan
>>
>> "Richard Haber" <richard.haber@gmail.com> wrote in message
>> news:ee3p9n$i1h$1@is.intellij.net...
>>
>>> I've been following these threads about 'slow startup time' for a
>>> while now. I agree that bugs should be fixed, and if this is a bug,
>>> then the JetBrains should fix it; from past performance, they
>>> probably will.  I've been developing software for a large fraction of
>>> a century now, so maybe I'm old fashioned, but I am constantly amused
>>> at the comments like '...it takes 8 more seconds to open VS 2005 and
>>> it keeps developers from using it.'
>>>
>>> I have watched developers start up VS and stare at the screen for 20
>>> seconds before navigating to pages to start work.  I have seen them
>>> spend 30 seconds creating blocks of code that R# creates with a few
>>> keystrokes in a second. I have seen them using Edit -> Find to locate
>>> method usages and then modify the wrong ones.  This list can go on
>>> forever.
>>>
>>> The amount of productivity time a tool like R# can save far outweighs
>>> any additional start up time required.  I don't hear anyone
>>> complaining about the amount of time VS takes to load when compared
>>> to Notepad as an IDE!
>>>
>>> Perhaps the concept of 'dinosaur' shouldn't just apply to us 'senior
>>> citizens' of the Technology community.
>>>
>>> As Dennis Miller would say (back when he was fresh and original),
>>> 'Just my opinion, I could be wrong...'
>>>
>>> "Jeff" <jeffwalsh@hotmail.com> wrote in message
>>> news:edrrep$8dm$1@is.intellij.net...
>>>
>>>> From the list of known issues:
>>>>
>>>> "If you open solution and then enable ReSharper, there is quite long
>>>> lag before ReSharper initialization progress dialog appears"
>>>>
>>>> Any idea when this will be addressed?
>>>>
>



0
Comment actions Permalink

I want tools that increase my productivity but it should NOT slow me down.
As a developer you want to fastest computer available to work on because you
don't like staring at the glass hour. When you click on a shortcut you want
this program to be open instanenously. This is also the reason why Microsoft
is building into Windows such features as pre-fetching, that is the reason
why we use multi-threading and so on. The responsiveness of the system is a
very important issue for a lot of computer users out there. If you are used
to the fact that Visual Studio 2005 is up and running one second after
clicking on the shortcut then you don't like the fact that a tool that
icreases your refactoring productivity turns that one second into 15 seconds
(depending on the machine specs).

Gabriel Lozano-Morán


"Ed Chapel" <echapel@crosscurrentinc.com> wrote in message
news:106baec85c5a8c8a3a255384458@news.jetbrains.com...
>I think Richard has the optomistic perspective. R# does provides a ton of
>functionality and enhances productivity. I don't understand why someone
>would assert that R# should load faster. The complaint is purely
>subjective... how do you measure when R# is fast enough? Certainly a
>professional relying on R# can see even a few minutes into the future to
>realize the benefits of waiting 10-30 seconds for R# to start up.
>

My two cetns...

>

Ed

>

Hello Tamir,

>
>> No, you're right -- but so are the others.
>>
>> Yes, R# is a great tool that helps productivity when used correctly.
>>
>> No, that doesn't mean it's OK for it to slow you down in all those
>> other times.
>>
>> Sometimes you open VS and stare for 30 seconds -- in those cases, R#
>> can take 10 of them and that's fine. But sometimes you would like to
>> go straight to a specific line of code, and have to wait 10 seconds
>> for VS to open, and it's annoying.
>>
>> Sometimes you're typing in a switch statement (or whatever) and R# can
>> save you many keys. But sometimes all you do is change an assembly
>> reference, and R# grinds your machine away for a while.
>>
>> R# is a productivity tool; anything it does to increase productivity
>> is a blessing, but anything it does to decrease it is a curse. Each
>> developer decides for him/herself if there's a net gain there (hey,
>> it's worth it in my book), but the friendly folks at jetbrains should
>> be aware of anything that weighs on that decision.
>>
>> Tamir Nitzan
>>
>> "Richard Haber" <richard.haber@gmail.com> wrote in message
>> news:ee3p9n$i1h$1@is.intellij.net...
>>
>>> I've been following these threads about 'slow startup time' for a
>>> while now. I agree that bugs should be fixed, and if this is a bug,
>>> then the JetBrains should fix it; from past performance, they
>>> probably will. I've been developing software for a large fraction of
>>> a century now, so maybe I'm old fashioned, but I am constantly amused
>>> at the comments like '...it takes 8 more seconds to open VS 2005 and
>>> it keeps developers from using it.'
>>>
>>> I have watched developers start up VS and stare at the screen for 20
>>> seconds before navigating to pages to start work. I have seen them
>>> spend 30 seconds creating blocks of code that R# creates with a few
>>> keystrokes in a second. I have seen them using Edit -> Find to locate
>>> method usages and then modify the wrong ones. This list can go on
>>> forever.
>>>
>>> The amount of productivity time a tool like R# can save far outweighs
>>> any additional start up time required. I don't hear anyone
>>> complaining about the amount of time VS takes to load when compared
>>> to Notepad as an IDE!
>>>
>>> Perhaps the concept of 'dinosaur' shouldn't just apply to us 'senior
>>> citizens' of the Technology community.
>>>
>>> As Dennis Miller would say (back when he was fresh and original),
>>> 'Just my opinion, I could be wrong...'
>>>
>>> "Jeff" <jeffwalsh@hotmail.com> wrote in message
>>> news:edrrep$8dm$1@is.intellij.net...
>>>
>>>> From the list of known issues:
>>>>
>>>> "If you open solution and then enable ReSharper, there is quite long
>>>> lag before ReSharper initialization progress dialog appears"
>>>>
>>>> Any idea when this will be addressed?
>>>>
>



0
Comment actions Permalink

I think it is a matter of how one works and how to use the extra time
efficiently. For me, I rarely close and reopen VS2005. It stays open all day
unless it crashes (which it does sometimes). The only time I reload the
solution that is when either the project file or solution file is updated by
another team member, or I need to open a different branch of code. Depending
on the phase of the project this can happen between a few times to many times
a day. Does the loading time of R# slow me down? No, I generally spend the
extra time either trying to understand a bug or a new feature or surf the net :)

"Gabriel Lozano-Mor��������������������������������" wrote:

I want tools that increase my productivity but it should NOT slow me down.
As a developer you want to fastest computer available to work on because you
don't like staring at the glass hour. When you click on a shortcut you want
this program to be open instanenously. This is also the reason why Microsoft
is building into Windows such features as pre-fetching, that is the reason
why we use multi-threading and so on. The responsiveness of the system is a
very important issue for a lot of computer users out there. If you are used
to the fact that Visual Studio 2005 is up and running one second after
clicking on the shortcut then you don't like the fact that a tool that
icreases your refactoring productivity turns that one second into 15 seconds
(depending on the machine specs).

Gabriel Lozano-Mor疣


"Ed Chapel" <echapel@crosscurrentinc.com> wrote in message
news:106baec85c5a8c8a3a255384458@news.jetbrains.com...

>> I think Richard has the optomistic perspective. R# does provides a ton of
>> functionality and enhances productivity. I don't understand why someone
>> would assert that R# should load faster. The complaint is purely
>> subjective... how do you measure when R# is fast enough? Certainly a
>> professional relying on R# can see even a few minutes into the future to
>> realize the benefits of waiting 10-30 seconds for R# to start up.
>>
>> My two cetns...
>>
>> Ed
>>
>> Hello Tamir,
>>
>>> No, you're right -- but so are the others.
>>>
>>> Yes, R# is a great tool that helps productivity when used correctly.
>>>
>>> No, that doesn't mean it's OK for it to slow you down in all those
>>> other times.
>>>
>>> Sometimes you open VS and stare for 30 seconds -- in those cases, R#
>>> can take 10 of them and that's fine. But sometimes you would like to
>>> go straight to a specific line of code, and have to wait 10 seconds
>>> for VS to open, and it's annoying.
>>>
>>> Sometimes you're typing in a switch statement (or whatever) and R# can
>>> save you many keys. But sometimes all you do is change an assembly
>>> reference, and R# grinds your machine away for a while.
>>>
>>> R# is a productivity tool; anything it does to increase productivity
>>> is a blessing, but anything it does to decrease it is a curse. Each
>>> developer decides for him/herself if there's a net gain there (hey,
>>> it's worth it in my book), but the friendly folks at jetbrains should
>>> be aware of anything that weighs on that decision.
>>>
>>> Tamir Nitzan
>>>
>>> "Richard Haber" <richard.haber@gmail.com> wrote in message
>>> news:ee3p9n$i1h$1@is.intellij.net...
>>>
>>>> I've been following these threads about 'slow startup time' for a
>>>> while now. I agree that bugs should be fixed, and if this is a bug,
>>>> then the JetBrains should fix it; from past performance, they
>>>> probably will.  I've been developing software for a large fraction of
>>>> a century now, so maybe I'm old fashioned, but I am constantly amused
>>>> at the comments like '...it takes 8 more seconds to open VS 2005 and
>>>> it keeps developers from using it.'
>>>>
>>>> I have watched developers start up VS and stare at the screen for 20
>>>> seconds before navigating to pages to start work.  I have seen them
>>>> spend 30 seconds creating blocks of code that R# creates with a few
>>>> keystrokes in a second. I have seen them using Edit -> Find to locate
>>>> method usages and then modify the wrong ones.  This list can go on
>>>> forever.
>>>>
>>>> The amount of productivity time a tool like R# can save far outweighs
>>>> any additional start up time required.  I don't hear anyone
>>>> complaining about the amount of time VS takes to load when compared
>>>> to Notepad as an IDE!
>>>>
>>>> Perhaps the concept of 'dinosaur' shouldn't just apply to us 'senior
>>>> citizens' of the Technology community.
>>>>
>>>> As Dennis Miller would say (back when he was fresh and original),
>>>> 'Just my opinion, I could be wrong...'
>>>>
>>>> "Jeff" <jeffwalsh@hotmail.com> wrote in message
>>>> news:edrrep$8dm$1@is.intellij.net...
>>>>
>>>>> From the list of known issues:
>>>>>
>>>>> "If you open solution and then enable ReSharper, there is quite long
>>>>> lag before ReSharper initialization progress dialog appears"
>>>>>
>>>>> Any idea when this will be addressed?
>>>>>
>>


0
Comment actions Permalink

Anyway it also depends on what kind of job you have. If you are for example
working on a single project for months this is true nevertheless there is
imho no excuse if slowing the Development IDE down.

Gabriel Lozano-Morán

"Alex Hung" <ahung@xbsolutions.com> wrote in message
news:ee4ltd$aq1$1@is.intellij.net...
I think it is a matter of how one works and how to use the extra time
efficiently. For me, I rarely close and reopen VS2005. It stays open all day
unless it crashes (which it does sometimes). The only time I reload the
solution that is when either the project file or solution file is updated by
another team member, or I need to open a different branch of code. Depending
on the phase of the project this can happen between a few times to many
times
a day. Does the loading time of R# slow me down? No, I generally spend the
extra time either trying to understand a bug or a new feature or surf the
net :)

"Gabriel Lozano-Mor????????????????????????????????" wrote:

I want tools that increase my productivity but it should NOT slow me down.
As a developer you want to fastest computer available to work on because
you don't like staring at the glass hour. When you click on a shortcut you
want this program to be open instanenously. This is also the reason why
Microsoft is building into Windows such features as pre-fetching, that is
the reason why we use multi-threading and so on. The responsiveness of the
system is a very important issue for a lot of computer users out there. If
you are used to the fact that Visual Studio 2005 is up and running one
second after clicking on the shortcut then you don't like the fact that a
tool that icreases your refactoring productivity turns that one second
into 15 seconds (depending on the machine specs).

>

Gabriel Lozano-Mor?

>
>

"Ed Chapel" <echapel@crosscurrentinc.com> wrote in message
news:106baec85c5a8c8a3a255384458@news.jetbrains.com...

>> I think Richard has the optomistic perspective. R# does provides a ton of
>> functionality and enhances productivity. I don't understand why someone
>> would assert that R# should load faster. The complaint is purely
>> subjective... how do you measure when R# is fast enough? Certainly a
>> professional relying on R# can see even a few minutes into the future to
>> realize the benefits of waiting 10-30 seconds for R# to start up.
>>
>> My two cetns...
>>
>> Ed
>>
>> Hello Tamir,
>>
>>> No, you're right -- but so are the others.
>>>
>>> Yes, R# is a great tool that helps productivity when used correctly.
>>>
>>> No, that doesn't mean it's OK for it to slow you down in all those
>>> other times.
>>>
>>> Sometimes you open VS and stare for 30 seconds -- in those cases, R#
>>> can take 10 of them and that's fine. But sometimes you would like to
>>> go straight to a specific line of code, and have to wait 10 seconds
>>> for VS to open, and it's annoying.
>>>
>>> Sometimes you're typing in a switch statement (or whatever) and R# can
>>> save you many keys. But sometimes all you do is change an assembly
>>> reference, and R# grinds your machine away for a while.
>>>
>>> R# is a productivity tool; anything it does to increase productivity
>>> is a blessing, but anything it does to decrease it is a curse. Each
>>> developer decides for him/herself if there's a net gain there (hey,
>>> it's worth it in my book), but the friendly folks at jetbrains should
>>> be aware of anything that weighs on that decision.
>>>
>>> Tamir Nitzan
>>>
>>> "Richard Haber" <richard.haber@gmail.com> wrote in message
>>> news:ee3p9n$i1h$1@is.intellij.net...
>>>
>>>> I've been following these threads about 'slow startup time' for a
>>>> while now. I agree that bugs should be fixed, and if this is a bug,
>>>> then the JetBrains should fix it; from past performance, they
>>>> probably will.  I've been developing software for a large fraction of
>>>> a century now, so maybe I'm old fashioned, but I am constantly amused
>>>> at the comments like '...it takes 8 more seconds to open VS 2005 and
>>>> it keeps developers from using it.'
>>>>
>>>> I have watched developers start up VS and stare at the screen for 20
>>>> seconds before navigating to pages to start work.  I have seen them
>>>> spend 30 seconds creating blocks of code that R# creates with a few
>>>> keystrokes in a second. I have seen them using Edit -> Find to locate
>>>> method usages and then modify the wrong ones.  This list can go on
>>>> forever.
>>>>
>>>> The amount of productivity time a tool like R# can save far outweighs
>>>> any additional start up time required.  I don't hear anyone
>>>> complaining about the amount of time VS takes to load when compared
>>>> to Notepad as an IDE!
>>>>
>>>> Perhaps the concept of 'dinosaur' shouldn't just apply to us 'senior
>>>> citizens' of the Technology community.
>>>>
>>>> As Dennis Miller would say (back when he was fresh and original),
>>>> 'Just my opinion, I could be wrong...'
>>>>
>>>> "Jeff" <jeffwalsh@hotmail.com> wrote in message
>>>> news:edrrep$8dm$1@is.intellij.net...
>>>>
>>>>> From the list of known issues:
>>>>>
>>>>> "If you open solution and then enable ReSharper, there is quite long
>>>>> lag before ReSharper initialization progress dialog appears"
>>>>>
>>>>> Any idea when this will be addressed?
>>>>>
>>
>



0

Please sign in to leave a comment.