Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Disabling npm's progress bar yields a 2x npm install speed improvement

twitter.com

Post reply on HN
Print view View original

81–90 of 187 posts

Re: Disabling npm's progress bar yields a 2x npm install speed improvement

#81

Post by [deleted] »

morebetterer wrote: post #73
kazinator wrote: post #57

Earlier quoted context omitted.

Thanks for sharing! As an undergrad, I had a 14.4 kbps modem, and an amber WYSE terminal. With that, I was able to do contract work. It reminded me of the amber monitor I had on my Apple II ten years before. A solid phosphor CRT with no shadow mask is a fine thing. Colors on a modern LCD are great too; give it a chance!

I have a soft spot for those short-lived X-terminals as well. The golden age of computing. Colors are great for web browsing, don't get me wrong. Just not near my code!

[deleted]

Re: Disabling npm's progress bar yields a 2x npm install speed improvement

#82

Post by [deleted] »

morebetterer wrote: post #73
kazinator wrote: post #57

Earlier quoted context omitted.

Thanks for sharing! As an undergrad, I had a 14.4 kbps modem, and an amber WYSE terminal. With that, I was able to do contract work. It reminded me of the amber monitor I had on my Apple II ten years before. A solid phosphor CRT with no shadow mask is a fine thing. Colors on a modern LCD are great too; give it a chance!

I have a soft spot for those short-lived X-terminals as well. The golden age of computing. Colors are great for web browsing, don't get me wrong. Just not near my code!

[deleted]

Re: Disabling npm's progress bar yields a 2x npm install speed improvement

#83

Post by kazinator »

morebetterer wrote: post #73
kazinator wrote: post #57

Earlier quoted context omitted.

Thanks for sharing! As an undergrad, I had a 14.4 kbps modem, and an amber WYSE terminal. With that, I was able to do contract work. It reminded me of the amber monitor I had on my Apple II ten years before. A solid phosphor CRT with no shadow mask is a fine thing. Colors on a modern LCD are great too; give it a chance!

I have a soft spot for those short-lived X-terminals as well. The golden age of computing. Colors are great for web browsing, don't get me wrong. Just not near my code!

I contracted at Nortel in the mid 1990's. In my cube I somehow acquired a Sun Sparcstation 20 that nobody was using, and found an NCD black-and-white (or was that one grayscale?) X terminal on a shelf somewhere, collecting dust. I found an image for it somewhere, and set it up to TFTP boot from the SS20 (which was running Red Hat Linux) to a login prompt (XDM). It was a nice little setup.

Re: Disabling npm's progress bar yields a 2x npm install speed improvement

#84

Post by tlrobinson »

juandazapata wrote: post #45
yunong wrote: post #12

Earlier quoted context omitted.

Even more important, npm doesn't reliably reproduce builds. Different runs of the same shrinkwrapped build could either fail or succeed -- which is odd given that builds should be deterministic. Additionally, shrinkwrap is also broken in the same way. This is the first time I've heard of ied, a little competition could go a long way!

That's frustrating, I got bitten by that a couple of times. I'm wondering when will they add a LOCKFILE like every other build system out there :'(

That's what npm-shrinkwrap.json is supposed to be. It's given me a lot of trouble though.

Re: Disabling npm's progress bar yields a 2x npm install speed improvement

#86

Post by cdr »

ClayFerguson wrote: post #68

Doing GUI calls is a notorious way to slow down apps. I sped up an app (major software from major large corporation) by a factor of 10x a few years back by removing GUI updates. What you have to do is create a thread that refreshes the GUI periodically and not let your main worker thread ever work on the GUI. This particular app was an Eclipse Plugin (a source control app) and the Eclipse SWT to update the console lo…

When I gave the Nexus Mod Manager a try a little while ago, I wondered how it managed to take 18 hours to copy a few hundred files from one directory to another - on a SSD. Wouldn't be surprised if this was at least part of it.

Re: Disabling npm's progress bar yields a 2x npm install speed improvement

#88

Post by nicklo »

ClayFerguson wrote: post #68

Doing GUI calls is a notorious way to slow down apps. I sped up an app (major software from major large corporation) by a factor of 10x a few years back by removing GUI updates. What you have to do is create a thread that refreshes the GUI periodically and not let your main worker thread ever work on the GUI. This particular app was an Eclipse Plugin (a source control app) and the Eclipse SWT to update the console lo…

This strategy is also encouraged by best iOS development practices (main thread never works on GUI).

Edit: 'main' as in the one doing the one doing the work, in the same spirit of the original post. In truth, the true main thread that runs in main() is where all the iOS GUI work happens. Apologies for the confusing wording.

Re: Disabling npm's progress bar yields a 2x npm install speed improvement

#89

Post by panic »

nicklo wrote: post #88
ClayFerguson wrote: post #68

Doing GUI calls is a notorious way to slow down apps. I sped up an app (major software from major large corporation) by a factor of 10x a few years back by removing GUI updates. What you have to do is create a thread that refreshes the GUI periodically and not let your main worker thread ever work on the GUI. This particular app was an Eclipse Plugin (a source control app) and the Eclipse SWT to update the console lo…

This strategy is also encouraged by best iOS development practices (main thread never works on GUI). Edit: 'main' as in the one doing the one doing the work, in the same spirit of the original post. In truth, the true main thread that runs in main() is where all the iOS GUI work happens. Apologies for the confusing wording.

This is backward. Since UIKit is single threaded, the main thread must work on GUI: the best practice is that nothing except GUI work should happen there.

Re: Disabling npm's progress bar yields a 2x npm install speed improvement

#90

Post by morebetterer »

kazinator wrote: post #83
morebetterer wrote: post #73

Earlier quoted context omitted.

I have a soft spot for those short-lived X-terminals as well. The golden age of computing. Colors are great for web browsing, don't get me wrong. Just not near my code!

I contracted at Nortel in the mid 1990's. In my cube I somehow acquired a Sun Sparcstation 20 that nobody was using, and found an NCD black-and-white (or was that one grayscale?) X terminal on a shelf somewhere, collecting dust. I found an image for it somewhere, and set it up to TFTP boot from the SS20 (which was running Red Hat Linux) to a login prompt (XDM). It was a nice little setup.

I bet it was. Well done.

A couple of years ago I was just about to throw out all my O'Reilly X Window/Motif books from 20 years ago and when I landed a contract to update a K&R C based Motif system running on 32-bit Solaris connected to - of course - Sybase. It felt like I travelled back in time.

Old code never dies.

Post reply on HN