jongleberry

9 ms·

61.
by jongleberry 14y ago
why not just make this a real thing? adopt a cat from your local animal shelter.
62.
by jongleberry 14y ago
is there a possibility of foregoing EBS storage, using instance storage, and creating incremental backups to S3 using a secondary server on a replica set? is there a reason this would be a bad idea? seems like it would cost a lot less.
63.
by jongleberry 14y ago
if you look at the code, it's based on TJ Holowaychuk's component: https://github.com/component/component . there's i believe 600 "utilities" you can pick and choose from: https://github.com/component/component/wiki/Components . since it'
64.
by jongleberry 14y ago
true. i'm being a little sarcastic, but 1-2 levels of _unnecessary_ indentation bothers me when it's easily avoidable.
65.
by jongleberry 14y ago
it's more like it's unnecessarily messy, which bothers me. if it was necessary, then it wouldn't bother me. and it's not just the nesting that is messy, the whole `define` stuff going on is messy.
66.
by jongleberry 14y ago
agreed. the problem with these AMD frameworks is that the asynchronous nature and deeply nested callbacks are almost completely unnecessary because you end up concatenating/minifying the assets before production anyways. You end up with unr
67.
by jongleberry 14y ago
but please, not as slow as that website. that site takes me 8 seconds to load.
68.
by jongleberry 14y ago
and what if your whole site is dynamic? varnish doesn't do anything.
69.
by jongleberry 14y ago
500kb transferred? 2 seconds to load all the CSS and JS files? 4.5 seconds to load everything? Way too much overhead for a static page, IMO.
70.
by jongleberry 14y ago
it's unnecessary. if google can't give you your desired results within the first 10 results, they've failed. you should just retry your query instead of checking the next 10 results. also, infinite scrolling is more for "discovering" withou