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

91–100 of 187 posts

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

#91

Post by lilyball »

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 not only completely wrong, it's dangerously wrong. It is in fact wildly unsafe to touch the GUI from anything except the main thread. It's all the non-UI stuff that you should shove onto another thread.

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

#92

Post by baudehlo »

X-Istence wrote: post #27
striking wrote: post #26

Earlier quoted context omitted.

How is this unhelpful exactly? It's a link to another discussion that readers might be interested in.

Op was stating you shouldn't follow that link and go "Hey, me too" or "+1" on the Github Issue. Not that the link to the issue was unhelpful.

GitHub badly needs an "approve" system that is external to comments, like bitbucket has.

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

#93

Post by stormbeta »

mbell wrote: post #74
juandazapata wrote: post #45

Earlier quoted context omitted.

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 :'(

I agree, but I'm curious what other build systems have a lock file? Ruby does through bundler, who else does this right? I can't think of any.

You get a similar effect for free with any language whose community defaults to non-floating transitive dependencies, e.g most JVM languages.

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

#94

Post by ninkendo »

panic wrote: post #89
nicklo wrote: post #88

Earlier quoted context omitted.

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.

You're not being charitable enough to the comment... you two are in completely agreement with one another if you only changed the meaning of the word "main". It's clear the grandparent meant "the thread that's doing the work."

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

#95

Post by uxp »

nashashmi wrote: post #72
striking wrote: post #24

Earlier quoted context omitted.

Heh, just "ied" will give you this: https://en.wikipedia.org/wiki/Improvised_explosive_device "ied package manager" works, though.

Normally, I am not a fan of replacing words in the search engine with computer science stuff (think AJAX), but I can accept computer words replacing words that symbolize violence.

Your results, even when logged out, are heavily biased towards your previous query genres. For instance, I'm not logged in, but am at home with an IP address that hasn't changed in over a year despite being leased. When I search Google for the term "Ruby", the entire first page is for the Ruby programing language.

My father works with jewelry. Last week while visiting him, I did in fact search for the term "Ruby" on his computer in his normal browser, and even though he was also logged out, I wasn't able to find one result dealing with the programming language on the first two pages.

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

#96

Post by nodamage »

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.

Not just iOS. Pretty much all UI frameworks frown upon doing heavy work on the main thread.

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

#97

Post by brazzledazzle »

clessg wrote: post #69
Xophmeister wrote: post #25

Earlier quoted context omitted.

I'm not sure "IED" is the best acronym to go for, either: https://en.wikipedia.org/wiki/Improvised_explosive_device

It gets brought up on a regular basis. Thought it was going to be renamed to `nom` but apparently not. https://github.com/alexanderGugel/ied/pull/45#issuecomment-1... > Thanks, but I'm not going to rename this project anytime soon.

That's unfortunate. Maybe sentiment on HN will finally get him to come to his senses.

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

#99

Post by KG8 »

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…

Years ago had a similar albeit smaller discovery. Loading a flash application with a progress bar and setting the quality option to the lowest quality made the bar go faster.
Post reply on HN