544 karma · joined November 23, 2009
1. 3x3 Spaces grid 2. Each major application assigned to a space. Primary editors (vim, Textmate, etc.) in space 5 (center), others surrounding it. 3. Each application typically maximized to fill its space. 4. When I need to switch applications, command-tab between them.
This gave me each application with almost a full screen of space, isolated to itself, with little cognitive overhead. I don't need more than command-tab at this point to manage my workflow.
I installed Lion today. Now, I have a linear set of spaces, but some of the applications I was giving full-screen to can actually use the whole screen. Mail is one of them. Chrome's support is a bit buggy so I'm avoiding it for now.
I still command-tab between applications, and that works fine, giving me all the space I had before. It seems to me that Lion's replacement for spaces was designed for me: someone who assigns one space per major application and likes to have those applications full-screened. I can 4-finger swipe left/right between the spaces (I had to set 3-fingers for page swiping so I could keep using the trackpad for Chrome forward/back). That means I can't use 4-finger-swipe to pull up the command-tab switcher, but 3-finger-swipe-up brings up MC, which is close enough, now.
Just food for thought. If I had to deal with the multiple-screen issues OP mentioned, I'd probably go nuts, but I've only used a customized Ubuntu for such situations long-term. As a laptop user, MC seems designed for me almost to the T.
Most everything else they've confronted was done by Amazon and Google years before Facebook had to.
But then, they won't be entering any CC information without being at Google's domain. You only enter CC information at checkout.google.com, and it initiates a popup to go there if you are either not logged-in or don't have a CC entered.
So, as an attacker, all they're doing is getting you (the naïve user) to click a button that looks like Google's button, and since they've already gotten you to click on a button to begin with (to initiate the transaction) they've already gotten any clickjacking exploit you need out of the user.
Who knows how you make money off it, though.
1. Wire fraud maxes out at 20 years outside of a presidentially-declared emergency. No fine cap, it seems. http://uscode.house.gov/download/pls/18C63.txt
2. Computer fraud under 1030(a)(4) caps out at 5 years with no prior offense, no fine cap. http://uscode.house.gov/download/pls/18C47.txt
3. 1030(a)(2), (c)(2)(B)(iii) looks to be another cap of 5 years. Ibid.
4. 1030(a)(5)(B), (c)(4)(A)(i)(I),(VI) looks like another cap of 5 years. Ibid.
IANAL, just trying my best to read the code itself.
I think the tough part is that GitHub's innovations in collaboration are primarily a huge win for open source. GitHub makes discovery of these projects so much easier, connects disparate people across communities (and countries!), and provides a unified technical stack and process "stack" for those people to contribute (same bug trackers, same "send me a pull request" approach, same wiki). That's something that's a pretty big deal for OSS.
Most of those issues aren't as big a deal for a business in my experience - most businesses either don't have such problems (discovery) or have their own solutions (process). But hey - you guys have got customers, you're hiring like crazy, and I love your stack personally; I'm certainly not judging! Just offering my perspective on why some folks might not buy in to the collaboration stuff from a business point of view.
This isn't code, these are written assignments we're discussing. English is pretty damn flexible, and nobody gets suspended for "Abraham Lincoln died in 1865." There's no point invoking degenerate cases to argue against a policy. That's just silly.
When a nontrivial sentence appears both in an essay and in one of the listed sources, the Wikipedia page, or a top Google hit for the subject, you can draw inferences. If you can argue that you just happened to write:
> However, just six days after the surrender of Confederate commanding general Robert E. Lee, Lincoln was shot and killed by Confederate sympathizer John Wilkes Booth at Ford's Theatre in Washington, D.C.
just as it appears on Wikipedia at present, and convince your peers it's more likely than not that you did, then you won't be punished. Not unsurprisingly, such pleas typically (but not always) fail.
This is roughly consistent year-to-year.
First of all, MessagePack throws up a benchmark on their front page bragging about how it can deserialize 3 integers and a string faster than Protocol Buffers. Lovely. Of course, besides being a silly microbenchmark, that's in an array - not a keyed map, and since your protocol is going to evolve, you'll need a keyed map. Since MessagePack serializes map keys with the message, you're going to take a big hit there. Let alone when you have a protocol that grows over several years and has to support a service with over a hundred keys. Eventually, your string keys will become too big of an overhead, and you'll switch to integer keys. Then you have to roll your own translation layer between your space-saving integer keys and useful names for your keys. It's roughly at this point you wish you had picked the "creaky" solution which has done the right thing™ for almost a decade (though of course not open source for that long).
Social Networks are not supposed to be the same as a broadcast medium. What is being discussed in this thread is how to bridge the gap, but to suggest that information flow "should be dictated by the recipient" instead of permitting fine-grained sharing misses the entire point of Google+'s approach to sharing.
Allowing the recipient to dictate information flow is excellent for self-promotion, marketing, and news broadcast. It doesn't make sense for how people interact with friends, family, drinking buddies, and colleagues.
Who exactly is using monitoring tools that sample every 5 minutes? Goodness. Maybe I've been spoiled, but I couldn't imagine using such a blunt tool.
It doesn't change the fact that 60TB is tiny for a company whose every product involves storing enormous quantities of data and serving them at monstrous scale.
Plus, since the moon has synchronous rotation, the mirors would at least always be facing us. Assuming all the other massive difficulties got worked out, it'd be a good place for those mirrors.
Primarily, this means you don't have to support internationalization - which is hardly a bad thing, especially if you work on a startup, where worldwide distribution should be the last thing on your mind. When your product is rendered in over 80 scripts, including right-to-left languages, you can't afford to figure encoding will sort itself later.
People really need to learn what anti-trust is and what it isn't. My goodness, the label gets applied to everything.