I think G+ sees the cookie and forces a login. Google Groups does the same thing, and it drives me insane.
464 karma · joined March 2, 2008
[ my public key: https://keybase.io/alec; my proof: https://keybase.io/alec/sigs/EwhDB5ZFYHetGQT4QBxryMKudydFlHx6vfI2ZbYaXTY ]
hnchat:M7diobfazxWsK0TZ9aVm
I think G+ sees the cookie and forces a login. Google Groups does the same thing, and it drives me insane.
It has support for many of the Python niceties: classes, list comprehensions, positional arguments, and so on. Interesting experiment, but I ended up thinking that Python is not the best language for the browser.
You should now update your HN profile with pride, to read "Founder @ Tindie" rather than "Engineer @ UrbanAirship" :)
That's the good. The bad is mostly typical big company stuff: you're a cog, you won't get significant choice on what to work on, you have to "play the game" to get promoted.
I left two years ago because I wanted to try a startup and it was the right decision for me. Much more diverse role, touched a lot more technologies, got exposure to a lot more interesting problems. YMMV
It's a good read, and to me it highlights just how difficult it is to get funding in Australia. To put it in perspective, they are a well established company with solid founders and a proven business model, and they still had a great deal of difficulty raising money.
(I am an ex-Googler)
MonoDevelop, MonoTouch, and C# have been an absolute pleasure to work with. Completion is insanely fast, with fuzzy matching. C# delegates make implementing event handlers a pleasure. The integration with Interface Builder is a bit shaky at times, but I suspect that may be a bug in XCode.
I have been looking for the equivalent of CommandT for buffers for a while, and the closest I've found is this: http://www.vim.org/scripts/script.php?script_id=1890
Unfortunately it's fuzzy file matcher is nowhere near as useful as CommandT's, so you'll have to use them in conjunction.
Once a company is acquired, all of the same constraints that apply to internal Google projects now apply to it. They are Google for all intents and purposes. "Strategy taxes" now apply, they'll have to port their iPhone app to Android, port their systems to Google infrastructure, and so on.
That is, if the acquisition doesn't get gutted entirely and its employees redistributed to other projects. See AppJet, Jaiku, JotSpot, etc. The "Google Blackhole", or talent acquisitions.
Desktop: Hackintosh, Core 2 Quad @ 2.83GHz with 8GB RAM and a GeForce 8800 GTS.
Laptop: Core 2 Duo MBP @ 2.26GHz with 4GB RAM
Server(s): Arch Linux
Software
MacVim, Python, Go, Chrome, Adium, Tweetie, Homebrew, Fabric, Git, git-flow, Rietveld, GMail, Redmine.
First, by making it trivial to get patches to the maintainer. Prior to GitHub, if you wrote a patch for a project, you would have to track down the appropriate channel to submit the patch, then jump through any hoops required. Whether it be mail directly to the maintainer, a patch on a bugtracker (probably also requiring signup), mail to a mailing list (again probably requiring signup), patch having to be in a particular format, etc.
The second problem is what to do if the maintainer doesn't respond? Sometimes you might end up forking the project and hosting it in yet another random web page. Sometimes you might just end up dumping the patch onto the net, in the vain hope that someone else would find it if they had the same problem. I have done both, a number of times. With GitHub, the patches are clearly there as forks.
At least with GitHub, the barrier to writing a patch and getting it in the face of the maintainer is almost zero. This is an improvement. If they don't respond, at least it's obvious to users from the proliferation of forks, and if they're lucky they can find the particular fork that fixes their issue.
Solving the human problem of maintenance is a big challenge. If GitHub solves that as well, I'll be amazed.
According to a screenshot in the Reddit thread of a mail allegedly sent by Plannr, it will be shut down.
The OP's implementation automatically determines the correct format string from the type of the variable. So you can simply do:
LOG_EXPR(some_int); LOG_EXPR(some_float); LOG_EXPR(some_complex_cocoa_type);
I stopped using Posterous because of it, now I will happily be able to try it again!
BumpTop with a touch based interface would be much more appealing than a mouse. Seems like a good fit.