Live data from Hacker News

Composer – Disable GC when computing deps and refs

github.com

81–90 of 135 posts

Re: Composer – Disable GC when computing deps and refs

#81
post #40

Earlier quoted context omitted.

1324 -> 232. If you say 70% reduction VS 100% increment sounds like you are talking the same stuff and it is possible to compare 70 with 100. The reality is even in the above edge case: 2x memory, 6x speed.

This; interpreting performance numbers is hard. Also, memory nowadays is cheap, CPU power isn't.

> Also, memory nowadays is cheap, CPU power isn't.

Unless you're running your deployment on a 512Mb or 1G VM. I've had composer max out swap on those too. Even with 2G RAM it's not been happy sometimes, so be interesting to see what difference this patch makes.

Re: Composer – Disable GC when computing deps and refs

#82
I remember story of my friend in algorithmic contest for high school students in Poland (which are quite hard). He solved problems correctly, but in his implementation he got to check in every iteration of loop if a collection still got any elements. He used col.size()==0 instead of col.isEmpty(). The first was O(n) and it fucked up all performance.

Re: Composer – Disable GC when computing deps and refs

#85
post #33

Looks like someone disabled garbage collection on that comment thread as well :)

The truth is, I don't understand the point on having to download MBs of stupid animated images I will not even look at when I expect to see a commit diff.

You could always use the Lynx browser

Re: Composer – Disable GC when computing deps and refs

#88
post #42

Earlier quoted context omitted.

[deleted]

Did you know that Composer is open source? One of the advantages of open source is that you have the freedom to take the code and fix issues that concern you. You can Google "open source" for more information - that might be a more productive use of your time than waiting for people who owe you nothing to make changes that you want.

Yes I'm well aware of what open source is and how it works (if you notice I'm pretty active on github); I've already sent a PR to fix part of the problem before.

However, it makes very little sense for them to, for example, merge a PR if it uses my public key for verification and not theirs. The problem I'm running into is that I can't just fix the issue without their cooperation.

Regardless, this is all moot because the Composer maintainer is now communicating with me privately to discuss how to fix the problem so it will be solved some day soon.

Re: Composer – Disable GC when computing deps and refs

#90

The commit is great. I love that the comments have spiraled completely out of control. At this point, 30 minutes after the link was posted, the comment thread is now a competition to see who can post the best gif. I know we're serious here, but stuff like this reminds me why I love the internet so much. It's fun to cut loose once in a while.

You must be a pedophile if you enjoy 11-year-old girls and 4Chan.
Post reply on HN