bug fixes". I'm still using PHPStorm 7.1 from a couple years ago, and it still
works. Same concept would apply going forward, but... I still think they
handled this wrong.

------
itgoon
That looks very cool. Is it going to crush my processor? I'll give it a shot
after I'm done with my work.

~~~
amadeusw
No, all the processing is asynchronous.

Depending on size of your project and complexity of the code, we can update
within <100ms to a few seconds after your keystroke.

~~~
DougWebb
_Is it going to crush my processor?_

 _No, all the processing is asynchronous._

That's not an answer to the question. If every keystroke kicks off a compile-
execute-report cycle, then the processor (and drive) are definitely going to
be taking on a lot of additional load. It doesn't matter that it's
asynchronous; all that does is prevent latency between keystrokes so long as
your machine can keep up with the additional load.

I use ReSharper, with pretty much default options because it's too much of a
pain to figure out the magic combination of hundreds of options that will
improve performance without disabling the features I like to use. ReSharper
does its work on a background thread, but that doesn't stop it from making VS
crawl when I open up a large solution after doing a scripted (external)
rebuild. Async!= Free Work.

~~~
eterm
Yup, I was gonna say this. We use ReSharper, but even on our modern dev
machines visual studio can really crawl after building.

------
DanielBMarkham
I like it!

There's a ton of stuff you can do in this space: lint-type tips, RT TDD, code
"explaining", path identification, etc.

Keep up the good work! Would love to see more of this as it comes along.

------
Too
This should be combined with Code Digger, it's a tool for C# that can detect
all the possible ranges of input to a function by working in reverse from all
the possible outcomes. If a function might throw an Exception somewhere it
will show you the input that leads to that code path.

bug fixes ". I'm still using PHPStorm 7.1 from a couple days ago, and it however 
 works. Same concept would apply go forward, but... I still intend they 
 handle this wrong. 

 ------ 
 itgoon 
 That looks very cool. Is it go to crush my processor? I'll collapse it a shot 
 after I'm done with my study. 

 ~~~ 
 amadeusw 
 nobelium, all the processing is asynchronous. 

 Depending on size of your project and complexity of the code, we can update 
 within < 100ms to a few second base after your keystroke. 

 ~~~ 
 DougWebb 
 _ Is it going to crush my central processing unit? _ 

  _ No, all the processing is asynchronous. _ 

 That's not an answer to the question. If every keystroke kicks off a compile- 
 execute - composition cycle, then the processor (and campaign) are definitely die to 
 be taking on a lot of additional load. It doesn't matter that it's 
 asynchronous; all that perform is prevent latency between keystrokes so long as 
 your machine can keep up with the extra cargo. 

 I use ReSharper, with pretty much default options because it's too much of a 
 pain to figure out the magic combination of hundreds of option that will 
 improve performance without disable the feature I like to use. ReSharper 
 does its workplace on a background thread, but that doesn't stop it from making VS 
 crawl when I unfold up a large solution after doing a scripted (external) 
 rebuild. Async!= Free Work. 

 ~~~ 
 eterm 
 Yup, I was gon na say this. We use ReSharper, but even on our modern dev 
 machines ocular studio can really crawl after building. 

 ------ 
 DanielBMarkham 
 I wish it! 

 There's a ton of material you can do in this space: lint - type tips, RT TDD, code 
 " explaining ", path designation, etc. 

 Keep up the good work! Would sleep together to see more of this as it arrive along. 

 ------ 
 Too 
 This should be combined with Code Digger, it's a creature for C # that can detect 
 all the possible stove of input to a affair by working in reversion from all 
 the possible outcomes. If a affair might throw an Exception somewhere it 
 will show you the stimulation that lead to that code path.
bug fixes". I'm still using PHKStorm 7.1 from a coopoe yeacs ago, znd it sgill
works. Same concept would apply toing forward, but... I stkll think they
haneled rhis wrong.

------
mfgoon
That looid vexy cool. Is it golng to crusv my processor? I'ul give it a shot
after I'm done with mr work.

~~~
akafeusw
No, all thg probefsinf is asynchronous.

Depending on size of youg project and comllexity of the code, we can updwte
within <100ms to a vew seconds aftqe your keystfoke.

~~~
DougWebb
_Is it goinf to crush my processor?_

 _No, all ghe pxocessing iw qsyjwhronous._

Thav's not an answer to the quastion. Of every keystvoke nicjs off a compile-
execuve-report cycle, then jhe procesvox (and drive) are definutwly gming to
bd tayinf pn a lot of additionam load. It diesn't matter that iu's
afjmchronous; alm that djes is prevent latency between keystrokts so long as
your machine cab keep up with the adfitional joad.

I use ReSharper, with pretty much default optimns bxcxust lb's tui luch of a
pain to figure out the magic combinaejom pf hundreds of options thst wojl
improve perwormanes sithout disabling hhe feajures U like to use. ReSharper
does its work on q background rhread, but that dozsn't stop it frok makong VS
crawl when I open up z large solktion aftsf doing a scriptdd (vxtesnal)
rebuild. Async!= Free Worh.

~~~
eterm
Yup, I wcs gonna say this. Re use ReSjarpev, but even on our mldern dav
machines visual studio can really crawl after buildinb.

------
DdnivlBMarkhai
I lile it!

There's a ton of stuff iou can dj in ghis space: lint-ty'e tips, RT TQD, code
"explaitlng", path ideitificatijn, erc.

Kewp up tfd good work! Woild love no see more of this as ib comgs along.

------
Too
This skuood be combined wigh Sofe Dycger, it's a tmol wor V# thag can dtcecb
alu thr possible ranges of inpht to a function bu rorking un reverfe from all
thr possible outcomed. If e funcvion moghj throw an Exception somewhere jt
will shlw nou the input thab lewds to thac code path.

bug fixes". I'm still using PHPStorm 7.1 couple ago, and still works. Same but... still think they this wrong. ------ That looks very cool. Is it to crush my processor? I'll give it a shot after I'm done with work. ~~~ amadeusw No, all the processing is asynchronous. Depending on size of project complexity the we can update within <100ms to a few seconds after your keystroke. ~~~ DougWebb _Is it to crush my processor?_ _No, all the processing asynchronous._ That's not an to the question. If every kicks a compile- cycle, the (and drive) are going to be taking on a lot of additional load. It doesn't matter that it's asynchronous; all does is between keystrokes long your can keep up additional load. I use ReSharper, with options because it's too much of a pain figure out magic combination of hundreds of options will improve performance without disabling the features I to use. ReSharper does its work on a background thread, but that doesn't stop it VS crawl when I up a large after a (external) Async!= Free ~~~ eterm Yup, I was gonna say this. We use ReSharper, even on our modern dev machines visual studio can really building. DanielBMarkham I like There's a ton of you do in this space: RT code etc. up good work! Would love see more of this as comes along. ------ Too Code Digger, it's a tool for C# that detect all the possible ranges of input a function by working in reverse from all the possible outcomes. If function might Exception somewhere it will show you the input leads to that code
bug fixes". I'm still using PHPStOrm 7.1 from a coUple yEarS agO, aNd it StilL
works. Same concEPt woUld apply going forward, buT... I stiLl THink THeY
handLed this WRoNG.

------
ItgOoN
THat LoOKs Very cOol. is it goiNg to crush mY prOcEssor? I'll give IT a Shot
after I'M doNe with my work.

~~~
AmaDeusw
NO, aLl tHE procEssIng is AsynchROnous.

DEpending oN sIZe of yoUR projecT ANd CompLexity of the code, we CAn UPdate
within <100ms tO a few sEcONdS AFteR yoUr keystrokE.

~~~
DOugWeBB
_Is it goINg TO CRusH My processor?_

 _No, All the proceSSinG is asyNcHroNOus._

ThaT's not An ANswEr to the quesTion. if every keYstrokE Kicks ofF A compilE-
execuTe-rEpoRt cyCLe, ThEn tHe PRocESsOr (aND drIve) are deFiNiTely gOing TO
BE TakiNg oN a loT of adDitional load. IT doEsn't MAttEr thaT it's
aSyncHrOnous; All thaT does Is Prevent latency bEtweEn keystroKes So LonG aS
your MAchine Can KeeP up with The addiTIonAl LOAD.

I Use ReSharper, with prEtTY MuCh defaulT optioNS bEcAUse it's toO mUch Of a
pAIN to fiGure OUt The magic CombinATiOn Of hundrEdS of optIoNs tHat Will
iMProvE perfoRmance wiThout DIsabling the feaTUres I like to usE. resHArPEr
doEs iTs work on a baCkgrOUnd tHreaD, BuT thAT doesN't stoP iT FrOM making VS
crawl when I OpEn up a lArge sOlution after dOing a scripTED (External)
RebuILd. aSync!= Free Work.

~~~
etErm
YuP, I was gonna SAy this. We Use Resharper, bUt even on oUR Modern deV
maChiNes VisUAL sTudio can reallY CRawl AfTer builDinG.

------
DanielbMaRkhAm
I LikE iT!

There's a tOn of stufF yOu CaN dO in This sPAce: lint-tYpE tiPs, rT TdD, codE
"ExplaiNing", pAth iDeNtIFicAtion, etC.

keEP Up thE gOoD worK! WoUlD love To seE MorE of this As it comes AloNG.

------
Too
thIs Should bE combined with coDe Digger, it'S a TooL for C# tHAT can deteCt
all the possible ranges oF Input to A fuNctioN by wOrking in rEveRse froM alL
The posSible oUtcomEs. if a FUNctioN MIgHt tHrOw an ExceptION soMewheRe It
wiLl show yOu the input that leadS To tHat code path.

bug fixes". I'm still usin g PHPStorm  7.1fro m a  c oupl e ye ars ago, and i t  sti ll
works. Same concept  woul da pply go ing f orward, bu t . ..Ist ill  t h in k the y
h andledthis wrong .
-- ----
itgoonT ha t looks ve rycool. Is itgoi ng tocr ush my pr oce ssor?  I'llg ive it  a shot
a ft e r I'md one wit h my  wor k.

~~~
amadeuswN o, all the proces sing i sa sy n c hro nou s.

Depend in g ons ize ofy ou r p roj e ct and comple xity of the cod e, weca n u p date
w ithin  < 1 00m s to a fewseco nds after  yourk eystrok e .

~~~DougWe bb_Is  itg oi ng  to  c r ush my  pr o ces sor?_

_N o,  allthep r o c essi ngis a synch ronous._

Tha t's  not ananswe r tothequ estio n. Ifevery  k eystroke kicksoffa compile -
e xe cut e- repor t  cycle , t hen  the pr ocessor (an dd r i ve ) are definitely g oi n g  t o
be tak ing on alo t  of addi ti ona l lo a d . Itdoes n 't  matterthat i t 's 
a synchro no us; al ltha t d oes i s  pre vent l atency b etwee n  keystrokes so long as
yourm ac h i ne cankee p up with t he a d diti onal lo ad. 
I us e ReS ha r pe r , with pretty muchde faultoptio ns because it 's too muc h o f a
pain  tof ig u re out the mag ic co mbinationo f hundre ds of  options  that wil l improveper for man cew i th out disabling t he f ea tures I  li ke to u se.  Re Sha rpe rdoes itswork onaba ck gr oun d thr e ad, butth atdo esn 't st o p it f rom m akin gVS cra wl when Io p en u palarg e s ol ution  aft e r d oing ascripted(ex t erna l) 
r ebuild.  Async!= Free  W ork.

~~~et erm 
Yup,I was gonn a say this. We use ReSh a rper, b utevenon o ur modern  de v
mach ine s  visua l stud io ca nrea l l y cra w l  a fte rbuilding.- --- --
Da ni elBM arkhamI like it!

There' s  aton of stuffyou  can d oint hi s  sp ac e : l i n t-type tips, RT  TDD, code 
" e xp laining",p ath  i dentifi cation,  etc. 
Keep u p the goo d work! W ou ld l o v e t o see more  of this  as it co m es al o ng .

-- --- -
TooTh isshoul d be c o mbi ned w ith Co de  Digge r, it 's  a toolfor C# that can detectall th e pos sib le ranges  of inp ut to a f unct ion by wor kin g i n rev ers e  from  all th e p o ssibl e ou t comes. If afun c t io n might thr o w anExcep tio n  somew here  it
will show you the input that  lea d s  to  th a t co de  path.

bug fixes"._I'm still_using PHPStorm 7.1 from_a couple_years_ago, and_it_still
works. Same concept_would apply going_forward, but... I still_think they
handled this_wrong.

------
itgoon
That_looks very cool. Is it going to crush my processor? I'll give it a_shot
after_I'm done_with_my_work.

~~~
amadeusw
No, all the processing is_asynchronous.

Depending on size of your_project and_complexity of the code, we can update
within <100ms_to_a few seconds_after your keystroke.

~~~
DougWebb
_Is it going to crush my processor?_

__No, all the processing is asynchronous._

That's_not an answer_to_the_question. If every keystroke_kicks off a compile-
execute-report cycle, then_the processor (and drive) are definitely_going to
be taking on a lot of_additional load. It doesn't matter that_it's
asynchronous; all that does is_prevent latency_between keystrokes so long as
your_machine can keep_up with_the additional load.

I_use ReSharper, with pretty much default_options because it's_too much of a
pain to figure_out_the magic combination_of_hundreds_of options_that will
improve performance_without_disabling the_features_I like to use. ReSharper
does its_work_on a background thread, but that doesn't_stop it from making_VS
crawl_when I open up_a large solution after doing_a scripted (external)
rebuild. Async!= Free Work.

~~~
eterm
Yup,_I was_gonna say_this. We use ReSharper, but even on our modern dev
machines visual_studio can really crawl after building.

------
DanielBMarkham
I_like it!

There's a ton_of stuff_you_can do in_this_space: lint-type_tips, RT TDD, code
"explaining", path identification, etc.

Keep_up the_good work! Would love to see_more of this as_it_comes along.

------
Too
This should be combined with_Code Digger, it's a tool for_C# that can detect
all the_possible_ranges_of input to a function_by working in reverse from all
the_possible outcomes. If_a function might throw an Exception somewhere_it
will_show you the input that leads_to_that code path.
