91 karma · joined December 19, 2011
https://electroheads.com/collections/all-electric-bikes?filt...
Get through to where you pick your cake design and pick one, then go back, repeat and watch the memory increase.
In the end we looked at the bottom line memory consumption and experimented until we saw reductions. We found using things like ng-show instead of ui-if, essentially preloading the partials and switching between them instead of reloading everytime, saved us enough memory to make the system viable.
In a recent rewrite of one of our applications into Angular we had huge issues with it consuming memory. I think our use case is quite distinct, we have a telephony component that needs to stay loaded so single page app really does mean single page app for us, but even so I would expect to see memory mentioned every now and then.
Found it slightly annoying that I couldn't view other auctions without just picking numbers in the address bar though. (Or signing up I presume).
It's not web based unfortunately so here's a short video of it running: http://www.youtube.com/watch?v=eY4DHcsuv1Y&feature=youtu...
And sourcecode: https://github.com/OneHP/murmuration
Also because I'm not great with my vector maths you'll spot that the boids have some odd behaviour where they favour vertical movement. Strange little bug.
Sell this to people running call centres, make sure it stays up all the time and they will love you.