These are chat archives for TypeStrong/atom-typescript

1st
Jul 2015
Miguel Couto
@Mig1st4ck
Jul 01 2015 08:44
i think the problem is with the upgrade.
something like a server is running listening for F6, then when i upgrade a new server is started, but the old is still runing,
since i had my Atom open for several days and did some upgrades i should have had 3 instances of the server running so 3 builds
after i restart Atom i got a single build.
Jonathan Park
@park9140
Jul 01 2015 19:22
@basarat, do you use Timecop?
I’m curious why the package load time is 600ms while the activation time is only ~30-40ms
I’m curious why the package load time is 600ms while the activation time is only 34ms
Basarat Ali Syed
@basarat
Jul 01 2015 23:29
@park9140 Haven't profiled it yet. Still feature churning
@park9140 think its the worker starting ... but not sure (i.e. doesn't sound right)
Basarat Ali Syed
@basarat
Jul 01 2015 23:41
Thanks @park9140 ! atom/atom#7638 created : TypeStrong/atom-typescript#428
Jonathan Park
@park9140
Jul 01 2015 23:42
@basarat, I might take a couple swings at optimizing load time this weekend.