I've been developing for Ruby 1.9 exclusively since December. It does unicode right, it does block parameters and local scope right, and it's fast. It's also been stable for six months. What is everyone waiting for?
Read more...
If you said "whattergate??" then click here.
The blog-o-twit-o-sphere is coming down pretty hard on TechCrunch for this and unfortunately generating enough noise to drown out the few people who have stopped twooting for a moment and thought about what is actually happening here.
Some unknown person went through a lot of trouble to steal damn near every internal document at Twitter. Then, they handed those documents over to the biggest tech news site on the four internets. One can only assume that they very much wanted TechCrunch to publish those documents. Had TC declined to do so, this person would have simply moved on to Drudge, Slashdot, Cake Wrecks, etc. until the thief found someone willing to publish the documents and give him the satisfaction of screwing Twitter.
Knowing this, Twitter was no doubt relieved to hear that their good buddies at TC had acquired the documents before anyone else. TC could craft the release so as to minimize damage to Twitter, while still satisfying the thief enough to avoid or delay further leaks. If there are more leaks, the incredibly popular TC story provides a distraction.
Of course, in the interests of professionalism, and to further sate the malevolent thief, Twitter must publicly express their outrage towards TC. They can't admit that they authorized the public release of confidential documents.
As to the question of how exactly the publication of the documents was "crafted", there is no particular reason to think that they omitted anything besides personal information that was not newsworthy. Indeed, Arrington says as much in this article. Trying to hide anything "juicy" would just leave it up for grabs by a less cooperative news outlet.
Maybe my tinfoil hat is too tight, but this all seems fairly straightforward to me. I'm not all that interested in this topic, I'm just annoyed by all the noise from the "ethics" debate when there is no ethical issue at all.
The blog-o-twit-o-sphere is coming down pretty hard on TechCrunch for this and unfortunately generating enough noise to drown out the few people who have stopped twooting for a moment and thought about what is actually happening here.
Some unknown person went through a lot of trouble to steal damn near every internal document at Twitter. Then, they handed those documents over to the biggest tech news site on the four internets. One can only assume that they very much wanted TechCrunch to publish those documents. Had TC declined to do so, this person would have simply moved on to Drudge, Slashdot, Cake Wrecks, etc. until the thief found someone willing to publish the documents and give him the satisfaction of screwing Twitter.
Knowing this, Twitter was no doubt relieved to hear that their good buddies at TC had acquired the documents before anyone else. TC could craft the release so as to minimize damage to Twitter, while still satisfying the thief enough to avoid or delay further leaks. If there are more leaks, the incredibly popular TC story provides a distraction.
Of course, in the interests of professionalism, and to further sate the malevolent thief, Twitter must publicly express their outrage towards TC. They can't admit that they authorized the public release of confidential documents.
As to the question of how exactly the publication of the documents was "crafted", there is no particular reason to think that they omitted anything besides personal information that was not newsworthy. Indeed, Arrington says as much in this article. Trying to hide anything "juicy" would just leave it up for grabs by a less cooperative news outlet.
Maybe my tinfoil hat is too tight, but this all seems fairly straightforward to me. I'm not all that interested in this topic, I'm just annoyed by all the noise from the "ethics" debate when there is no ethical issue at all.
Volunteering at FutureRuby last weekend was a pretty sweet deal. Aside from a bit of lifting and fetching, my job was to stand at the back of the conference room during every talk, which is the only thing in the world I would have wanted to do anyway. Kudos to the organizers for thinking of that, and for generally being superhuman and making the whole thing come together.
Read more...
Modal web frameworks offer a simpler and more natural way to implement some web workflows in code. They've been around for decades and a few of them are written in Ruby. So, why aren't we using them? I wanted to find out, so I made my own.
Read more...
This brilliant bit of marketing appears to be doing quite well in the twit-o-sphere. The cause is getting Microsoft to support "standards" by using the IE8 engine to render HTML email in Outlook, instead of the Word engine, which has been in there since 2007. Behind this movement is the "grassroots" Email Standards Project, which is apparently composed of one email marketing firm and two freelance designers. Judging by this deluge of copypasta, the sheeple are overwhelmingly supportive.
Read more...