Email me, chris@gstaff.org and I'll shoot you an invite. (your profile doesn't list an email)

Vivaldi with vertical tabs work well for this too, coupled with the keyboard shortcut to bring up a fuzzy tab selector. It's pretty awesome. Plus you get tab cycling in recently used order - the only sane option.

Likewise, I've moved to beancount http://furius.ca/beancount/ and the awesome fava https://github.com/aumayr/fava 21 years of Quicken data converted to a lovingly crafted text file. Ahh.

Also a big fan of Moneydance http://moneydance.com and have written a budget plugin for my family's needs

emusic by chance?

No, that wasn't it but thank you.

It costs a few bucks but BeyondCompare http://www.scootersoftware.com/ is the best differ I've used. It's not terminal based, but is supported on Windows, Mac, and Linux.

For those saying it breaks or ends at 10000. It doesn't if you append infinity like so http://www.datapointed.net/visualizations/math/factorization...

I also like how you can enable turbo by pressing the fast-forward button several times...

Cold startup sucks - it's horrendous for Java and just bad for Python.

If you have a popular app, this isn't an issue. If you don't, it hurts.

Cold startup is almost unnoticeable for Python apps (bite my lip! see update below). On the Java side it can be an issue but, as with most things, if you dig around, you can find some acceptable workarounds.

No - I've seen 'Hello World' style apps take over 4s to cold startup. For example http://timezonetimezone.appspot.com/iscorrect?query=EST

Took 4.67s to render http://www.webpagetest.org/result/100306_5PZ7/1/details/

I monitored cold startup for a month on one of my apps and some times see 10s cold startup. http://www.webpagetest.org/result/100309_5TDW/

This is after profiling, reducing imports, caching, using app appstats, etc.

Wow, you're right. I just ran a test on one of my Python apps and found the same thing. I always assumed 4 seconds was an acceptable start up time, especially when compared with some of the Java apps I have runnning on App Engine which have often exceeded the 30 second page limit on startup and generated a DeadlineExceededException. Thanks for showing your results. I would never have known this was an issue.

Couldn't you just set up a cron job to ping your app every 15 minutes until you start getting some real traffic?

You could - but it would need to be every 1 minute. Google tears down your app after 60-90 seconds of inactivity.

Some folks have resorted to pinging every minute but Google discourages that since it ties up their resources. If everyone pinged their site once a minute then resources would never be freed....

Here's a good thread on the issue https://groups.google.com/group/google-appengine/browse_thre...

They're fixing this in the future by allowing reserved instances that will always run.