Steps: go to theverge.com, open Timeline. Hit CMD-SHIFT-R for hard refresh, which will automatically trigger timeline. Wait. When the load event fires, Timeline will stop recording.
3,366 karma · joined March 23, 2009
Steps: go to theverge.com, open Timeline. Hit CMD-SHIFT-R for hard refresh, which will automatically trigger timeline. Wait. When the load event fires, Timeline will stop recording.
Anyone interested in further reading on the topic should check out anything by those guys, they're the foremost in the field.
I'm still not sure if this whole thing is a joke or not. Poe's Law in effect.
What do you mean by this? Can you give an example?
I think Brian "ending" Rubyspec might end up being the best thing he's done for it. Suddenly, as soon as he (and Rubinius) left, RubySpec is running and actively used on MRI for the first time in years, and JRuby and Opal have already swapped over to the new implementation. @eregon deserves HUGE credit for making this all happen.
What production website doesn't cache? You make it sound like it's a Ruby-only issue.
It's a fast-and-loose measurement, to be sure. Virtualization/dockerization is the only way to get a super-accurate measurement.
In theory, we're all nice people, and nice people don't need laws or handbooks to tell them what to do or who to behave.
But we're not all nice people. And when bad things happen, you need to have something written down that you can point to and say: "Hey, you violated this thing you said you agreed to." CoCs are not preventative measures (they don't proactively reduce bad behavior), they're more helpful for throwing out community members when they do something bad.
I'm also very optimistic on the future of JRuby, as with the new 9000 release it has the potential to bring Ruby speed in line with base Java. It's got decent corporate backing now as well with Red Hat and Oracle funding people to work on it.
Is that really "destroying evidence?" What if you just shut down the computer, rendering the hard drive unusable, its contents completely encrypted (a la TrueCrypt). The evidence isn't destroyed, it's just inaccessible.
That's roughly 111/k bags per month since launch. For the first nine months of a company, that's operationally extremely impressive.
The delays for new customers (3-6 months, yikes) seem ridiculous, but if you do the math, I'm surprised it isn't more.
Ruby optimizes for programmer happiness - that was Matz's explicit goal when writing the language. If that doesn't matter to you as much as speed on microbenchmarks, or if writing Ruby doesn't make you happy (it makes me happy!) then Ruby isn't for you.
https://bugs.ruby-lang.org/issues/7549#note-2
1. Matz is, and always will be BDFL. 2. The core Ruby team wants to talk in terms of C and MRI being the Ruby spec, not a third party/written RubySpec
However, it's also a failure - in part, due to Brian and his attitude towards contributors. See this twitter conversation: https://twitter.com/the_zenspider/status/547527644535726080 He's been grinding on Rubyspec for years, bless him, but I think there's a reason why he was unable to rally the community behind his effort, both in terms of gathering more contributors and in making it "official" in terms of the language spec.
JRuby, currently the only non-MRI ruby implementation that you can seriously consider for production use, runs the MRI test suite against JRuby. RubySpec is far from The Only Solution, though Brian would like you to think it is.
Very interesting how ideas from the first bubble re: brick-and-mortar are coming back.
Is that even a real sentence?
http://www.chromium.org/developers/using-requestautocomplete
EDIT: Here's more pics from South Africa http://uforsa.co.za/2013/09/mass-ufo-sighting-on-29-septembe...