http://hg.python.org/cpython/file/tip/Objects/listsort.txt
Sits in the actual source code to cpython. One of the many reasons I love python. (check out the notes on how dicts are implemented too)
1,391 karma · joined October 24, 2009
http://hg.python.org/cpython/file/tip/Objects/listsort.txt
Sits in the actual source code to cpython. One of the many reasons I love python. (check out the notes on how dicts are implemented too)
I don't think a short doc is of any help for evaluators. You shouldn't be basing your decision on 400 words and some bullet points. If you're serious about your datastore then you should treat it seriously.
1) doesn't appear to support external users. I can't seem to give a client access so they can comment on tasks, answer my questions or track my progress. All people you invite to a team appear to have unfettered access to all things.
2) no spec/pricing sheet on what's included. blog says "is and will remain free for teams with up to 30 members", but how much will it cost afterwards? Also, for the free plan, how many attachments can I add? What's the max size of an attachment? I don't want to invest my time into a new thing and then hit some invisible limit. (Yes, I've tried to look in the support/help faqs)
3) import/export. will you make it easier for me to move in from my current system? once I'm in the system am I locked in?
I'm currently using Apollohq, and it's been doing pretty well. It has all the features I mentioned above, as well as time tracking. Only thing is it costs money (a bit too much for my small team) and they've been slow to get a phone-friendly version. The interface has also slowed down since the beta, but for the time being I'm overlooking it because I expect growing pains.
That said, I think everyone I've talked to agrees Grooveshark has the best coverage, but everything there is so disorganized (and nobody is really sure of the legality).
Do you want a company to 1) only brew products (with a business model) internally until it is ready to ship, or 2) develop and release lots of things and see what works or not?
Google leans towards #2. They don't really care if they can make money off of something, if one of their engineers is interested in something they're allowed to take that risk. They put lots of stuff in the wild and if it doesn't stick then they kill it (or in most cases leave the source to the public - see wave) - or try to make it profitable (look at gapps).
Yes, a lot of things coming out of Google die, but that's only because they're putting out lots of things all the time. The day they stop putting out unproven stuff and only release v1.0 products is the day they lose their innovation edge.