You just might reconsider (and that is what bb is banking on), at the end of the day having to police the number of repos you can have is a pain(esp in a startup, where people are seemingly forever going off to hack away on random stuff). Sure bb isnt as pretty--current redraw notwithstanding--but unlimited repos is very handy indeed. just saying. Inline commenting was missed (we moved from gh to bb a few months ago), but i see that has been released too.
In my humble opinion, in the vast majority of cases, yes. Because " C ", " D ", " C# " should be easier for search engines to disambiguate (at least working with Lucene, it is, and I imagine Google etc are similar-ish).
As for Java, Python the context in the page likely to point to its intended audience (and it helps they have been around for ages etc). Otoh, " go " is likely to be used in a lot of literature, including other programming related texts.
Try searching for something with clojure, and then try go -- the quality of results is usually substantially different, and my unsubstantiated hunch is that not all of it has to do with lack of go-related content.
It was kind of interesting comparing the quotes from the various network operators. For instance, this management-speak gem could apply to any product at all:
"Etisalat aim to enrich the user experience and improve the life of its customers by providing enhanced services across a complete portfolio of devices and operating systems. Firefox OS will provide an open source platform to our customers and various ecosystem players, such as application developers, to experience innovative services. Thanks to this strategic initiative, the industry will benefit from a sustained growth in mobile data and the development of cutting edge applications, as well as the promise of affordable smartphone devices that provide an enriched customer experience."
I saw them but those are but single datapoints (and apps seems to vary wildly in requirements). would be handy to have a slider so you could answer the 'what-ifs'.
also, was an early beta signup, really liked dotcloud, but have to agree this pricing is pretty complicated :(
In fact, I tried on-instance storage too -- this didnt help substantially. The reality is that many (most?) stacks these days need to be able live happily on AWS...
You'd think -- but the 10gen guys weren't surprised when we were struggling at this level (periodically), on a RS with two AWS large instances and relatively large objects.
Absolute ops/sec in and of itself is relatively meaningless tbh.
We had a very similar situation ~300 writes per second on AWS. but I suspect some of this has to do with the fact that most people address scaling by adding a replica set, rather than the much hairier sharding setup (http://www.mongodb.org/display/DOCS/Sharding+Introduction), this seems natural b/c mongodb's 'scalability' is often touted. In reality though, because of the lock, RS dont really address the problem much, and we encountered many of the problems described by the OP.
Not to denigrate the work the 10gen guys are doing -- they are obviously working on a hard problem, and were very helpful, and the mms dashboard was nice to pinpoint issues.
We decided to switch too though in the end, though i still enjoy using mongo for small stuff here and there
Far more likely than 'abuse' (they could have just charged afterall) is probably Google's realization that they have an uncontested lead in machine translation - and there is a lot of money to be made here.. They recently won a contract with the European patent office to machine translate patents for them...
..){kind=link}