You can always replace the branches with tags (git tag failed-branch-mybranch mybranch && git branch -D mybranch). That way, you still will have access to the unmerged commits later, but your list of branches is clean. Your tags will bloat up, but I personally don't go through my tags nearly as often as my branches.
The screenshot you're referencing is from OS X! If you don't quit Chrome for a while, then open "About Google Chrome", that dialog or something very similar will display.
This is the first thing that came to mind for me. I recently wrote a WSGI Python app that made use of chunked encoding, so that it could emit multi-hundred MB text files without loading them all into memory first, and one of the big hurdles was running into an error after having sent some data. In the end I had to implement a fancy Javascript check and keep some state in the app to check if there had been an error and the downloaded file was no good.
While I wait for the site to load, I figured I'd comment with my own placeholder-cat experience. A site I worked on was taking a while to get me the actual images, so I took to Pixelmator and fixed myself some LOLcat placeholders. People loved it, except for one of the QAs, who said it was going to give her nightmares.
I think the name is "Careers 2.0" as in, this is the new version of how you manage your career. Before, you searched for jobs on job boards, sending out your resume, etc. Now, the employers come to you. Careers 2.0.
I can't seem to get it to work in Google Reader. I get no mouseover text at all, neither the Comic Text version nor the default Chrome version. Am I doing something wrong?
Maybe keep a list of my votes in the application cache and check against that as well as the ihackernews API? Same with my comments, too. I would really enjoy if it appeared to have read-your-writes consistency.
Cool, I'm using it to write this. Seems to work well enough. I wish there was a light theme, as I'm not really a fan of the light grey on black. Also,the voting doesn't seem to work correctly. I voted up this story, then quit the app and re-launched it, and it said I hadn't voted. Trying to vote it up again though failed, as the vote had indeed gone through.
410 days ago? I had just noticed this behavior in Chrome myself a few weeks ago, and thought it might be new beta behavior that no one had really talked about. Guess not.
Why would they save work on the in-tab UI and make the close-tab X button on the right? The window control buttons are on the left like any other Mac app, and the same goes for the closing X button on the Developer Tools frame. Both of those are on the right in Windows. As you saw with the Arabic screenshot, they've already done the work to allow the closing X buttons to be on the left; if they wanted the Mac tab closing buttons to be on the left, they'd be on the left. It's not just a holdout from Windows.
Interesting timing, as my team was about to start using Pivotal Tracker for our project. Hopefully this encourages them, and the fact that they'll have to pay $50/month after July doesn't scare them away. Not really a big price tag, but any money over free is the hurdle.
It seems like a number of apps will probably do this. For instance, I can't find Twitter for Mac outside of the app store, which is disappointing because I'm still on Leopard, stuck with Tweetie 1.2.8. I would say to be wary of losing your Leopard user-base, but being on the Mac App Store probably will give you enough exposure that you'll make up for it and more.
I will say this: Apple is not afraid to leave old technology behind. While website XYZ aims to support multiple versions of every browser, including those released a decade ago (IE6), Apple won't even support Leopard with its new store, which was the version that came with the Mac I got just over a year ago.
To all the people who voted me up because you too felt you were in the same situation, I'm sorry. I got home from work and there is indeed a Cr-48 in my possession now! Google is truly amazing. :/
I won't agree that it looks dumpy, but it certainly doesn't look modern, or in any way similar to the Googleplex. Of course, that's nearly everything in New York. Many think that's a plus...
To be honest I had the same problem, but did eventually scroll. I think my initial hesitation to scroll was because the top of the page looked so much like it could be an entire landing page, with prominent twitter, facebook, and email links. Of course (now?) there's also a little popup that says scroll, which if clicked scrolls you to the beginning of Ben walking.
Well, they can't really say so clearly exactly what they did. In an effort to stop people from gaming it, they keep their exact algorithm hidden. When people get around it, they tweak it further, in an endless cycle.
My guess is that their solution isn't actually based on customer's true opinions of the vendor, and thus the solution is cheatable. Hiding the solution is probably their best option at this point.
I don't get why I'd want to use virtualenv if my production servers allow global package installation. Ideally my Python deployment should be the only thing running on the server, right? In that case, having a virtualenv seems like overkill. And for local development, it's just a hassle to have to enter the virtualenv every time I want to run the code, when I could just have the needed packages installed globally.
The truth isn't that you don't need a teacher. You may be able to learn everything from a book or solitary practice, like yourself. But others probably can do that sometimes, may sometimes need a teacher, may sometimes need to discuss with peers, etc. And I don't mean that some people are visual learners, or readers, etc. I mean that people learn different topics in different ways, on different days, with different contexts, etc.
I think the cultural norm should be that if one way of learning isn't working for you, try another way. Practice, read it yourself, ask a friend for help, get a tutor, whatever you need.
My mistake. When I checked after their announcement yesterday they had not updated their store page (http://www.sencha.com/store/touch/). Also, their license was a bit confusing to me, and I thought it was only free for those who wished to make their entire application open source.