Earlier quoted context omitted.
[deleted]
People actively avoiding me means I don't have to deal with people. This is a good thing, yes. That's all I need to know - good work!
[deleted]
Composer – Disable GC when computing deps and refs
71–80 of 135 posts
Re: Composer – Disable GC when computing deps and refs
#72Re: Composer – Disable GC when computing deps and refs
#73Re: Composer – Disable GC when computing deps and refs
#74Earlier quoted context omitted.
No. Concern trolling and tone policing needs to fuck right the fuck off. Do you find you have much success motivating people when you use this tone of voice? I reported this issue in February. Others have reported it before I did. What is Composer's response? Silence and negligence while its maintainers go to cons and drink beer. Their priorities are totally fucking backwards. I would strongly advise using less infla…
[deleted]
[deleted]
Re: Composer – Disable GC when computing deps and refs
#75Earlier quoted context omitted.
Agreed. It's such a shame that HackerNews doesn't let you post animated GIFs - I think it'd really add a lot of value to the discussions here.
I'm hoping this is sarcasm since I don't think I've seen a single intelligent discussion in my life that was helped along by a funny GIF. Not to say there's anything wrong with funny GIF's, but I come to HN exactly because it moderates away that sort of stuff.
It was sarcasm. Sorry I forgot the tags - I'll be more careful in future.
Re: Composer – Disable GC when computing deps and refs
#76The 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.
it's completely retarded and shameful
Re: Composer – Disable GC when computing deps and refs
#77For those looking for a technical explanation, the PHP garbage collector in this case is probably wasting a ton of CPU cycles trying to collect thousands of objects (a LOT of objects are created to represent all the inter-package rules when solving dependencies) during the solving process. It keeps trying and trying as objects are allocated and it can not collect anything but still has to check them all every time it…
Couldn't I also speed up Composer by using Toran Proxy? ( https://toranproxy.com/ )
That would help speed up the network part of the install/update yes. The linked patch on the other hand hopefully gets the CPU part to a decent level for most people.
Re: Composer – Disable GC when computing deps and refs
#78Earlier quoted context omitted.
Please try and keep your attitude in check. Your tone is not helping.
[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.
Re: Composer – Disable GC when computing deps and refs
#79As far as i understand composer is roughly the same thing as the cpan client. And they just simply disabled the garbage collector for it. What is this guy doing that he needs gigabytes of memory to install a bunch of php libraries? Before: Memory usage: 2194.78MB (peak: 3077.39MB), time: 1324.69s After: Memory usage: 4542.54MB (peak: 4856.12MB), time: 232.66s
Yeah, seems like a bug "fix."
The jubilation in the comments over this seems... misplaced?
Re: Composer – Disable GC when computing deps and refs
#80Earlier quoted context omitted.
I think it's great too, but I shudder to think what it might look like 5 years from now. I can only figure that there will be dead gifs everywhere
I think most of those gifs are hosted on github. I tried to post a linked image, and it only showed the hyperlink. When I uploaded the image to github, it showed up inline.
Github proxies the images in comments: https://github.com/blog/743-sidejack-prevention-phase-3-ssl-...
Here's the code behind it: https://github.com/atmos/camo