By the way, there's an interest research on designing a new file system based on LSM tree that leverages SSD's sequential writing, as it is mainly motivated by SSDs' shortcomings with random writes: https://www.usenix.org/legacy/event/fast/tech/full_papers/Mi...
I believe TokuDB is using a flavor of B epsilon trees, i.e. a B tree with, per node, an associated staging area for writes to that node or its child nodes. Keeps inserts localised at the top of the tree, until the staging areas fill up. Then these staged inserts are propagated in batches down the tree.
In my opinion, a nice middle ground between the B tree and LSM approaches.
Exactly! I had the curiosity to check JAH's github profile too, and it raised more suspicious towards her than I had previously imagined. For a fair comparison, let's see a couple of female github repos (both frontend and backend):
See? Any of those smart women above has much more quality code in their repos with regular activity, even though not any of them works at github, that is, they push code on their free time.
"Julie Ann, Adria Richards and Shanley enter a bar: the bar just explodes because it's a symbol of the patriarchy."
But, seriously, I know various female programmers that I could trust not only my project, but my LIFE to. And as in the case of men, those are usually the low profile, highly productive, people. I doubt any "famous" developer this days in spite of gender/race/whatever. As with any hyped profession, there are a LOT of impostors trying to succeed without basic qualifications in computing. Hint: those are the ones who shout the loudest, have the highest number of followers on Twitter, but have very little, if any, REAL code on Github or any other public repositories. So... when the masks start to fell off they usually bail out their jobs loudly and pointing fingers to preserve their public personas. I doubt this is not the case of Julie Ann.
"You can fool all the people some of the time, and some of the people all the time, but you cannot fool all the people all the time.", Abraham Lincoln
1. The learning curve is really steep. I mean, really really steep. There's a critical shortage of (good) books, video, and tutorials on the web. I guess ExtJS' learning resources should be 0.1% of jQuery's. The examples on Sencha site were still using the 3 version last time I checked;
2. If you need to customize ExtJS, or need something slightly more sophisticated than CRUD screen, then you are pretty much on your own. You'll spend a large amount of time trying to "fight" the framework and your chances you succeeding are very low;
3. It's expensive and its open source license has restrictions;
4. Sencha seems to hide and obscure the access to the learning resources so that you are pushed towards their paid support.
5. It's slow;
6. The error messages (when they show up!) are cryptic.
7. ExtJS was re-designed for version 4, but some things like the Model objects are cumbersome and suffer many usage limitations;
8. It will never be adopted as a general purpose solution on Internet facing webapps for the reasons exposed above;
Java was viewed as being "good enough"; alternatives like Scala and Clojure were not considered.
If a company enter the what-is-the-hottest-language-of-the-week game it can easily drag itself in a downward spiral of death. Just because it boils down to taste! And it leaves a lot of hurted feelings around the way. Language is a lot about maintenance 10 years down the road.
Scala and Clojure each have significant design flaws, in my opinion, and neither would have been a significantly better choice.
Couldn't agree more! Be it a startup or a mega-corp, VPs should make their minds upfront and stay on their path until something amazingly better comes down the road. C'mon, if Google had chosen Scala, for example, they could have produced clean, concise code, FP-oriented software at the price of sluggish compilation times (many wasted minutes), lots and lots and lots of generated bytecodes, and binary incompatibility (ouch!). Jump into the trendy language badwagon and you find yourself nowhere pretty soon. I know of at least two prominent startups in Bay Area who are switching of Scala and adopting the old-fashioned Java, for many reasons, but fondness of OO or lack of vision are not among them. And a third startup is stealthily switching to Clojure. On the other hand, you have C/C++.
F1 is a successor of Megastore, even with relation to high write/read latencies. From bits leaked here and there by Google, one can safely assume they put highl value on cross datacenter consistency nowadays even if it means to hurt write ratios so much -- I recommend this video of Google IO 2011: http://www.youtube.com/watch?v=rgQm1KEIIuc (from minute 35:40 on). Megastore and F1 present abysmal latencies because they synchronously write to 3 data-centers at least before acknowledging the client side through Paxos or 2PC.
Only an idiot can assume that F1/Megastore is a drop-in replacement to MySQL (or Cassandra, jbellis!), but those guys invented BigTable, and battle tested it, long before writing the papers so they know where their priorities lie nowadays. On the other hand, I am highly curious about Spanner, the successor of BigTable, that powers F1.
