Drop millions of allocations by using a linked list
1–10 of 158 posts
Re: Drop millions of allocations by using a linked list
#2i never knew this, thanks.
Re: Drop millions of allocations by using a linked list
#3Ruby people discovering algorithms ducks
Re: Drop millions of allocations by using a linked list
#4Just comes to show how careless Ruby guys were while building this.
Re: Drop millions of allocations by using a linked list
#5Just comes to show how careless Ruby guys were while building this.
1. Make it work
2. Optimize
Re: Drop millions of allocations by using a linked list
#6Ruby people discovering algorithms ducks
Really. Every time I whine publicly how web programming people aren't familiar with even basic CS, I get a slap.
But really, I should move to web programming. I'll be an expert computer scientist there, probably.
Re: Drop millions of allocations by using a linked list
#7I'm not very familiar with Ruby; where exactly did the duplication occur in the original code?
Re: Drop millions of allocations by using a linked list
#8Re: Drop millions of allocations by using a linked list
#9Re: Drop millions of allocations by using a linked list
#10I'm torn on this one. It's a great performance improvement, but on the other hand I would expect this way sooner than after almost 4 years of usage.