The title of this article is needlessly inflammatory. Can some mod change it? <i>ChromeOS</i> is not dropping support ext* at all; its <i>files application</i> that is meant to be used with external drives is. That's a pretty huge difference.<p>I actually think the rationale for this is pretty good:<p>> Re #19, we understand that this was an undesirable decision for some users, but we sometimes need to make a product decision like this. Chrome and Chrome OS strive for simplicity. Every feature comes with complexity. Complexity adds maintenance cost, QA cost, slows down development, and adds surface of security exploits (as mentioned in #12). We should add a feature only if its benefit clearly outweighs its cost, but this particular feature was slipped in for some historical reason.<p>It's a shame for the people who were actually using this. But lots of people are overlooking that <i>this is just about the ChromeOS files application</i>: ChromeOS can still mount and access ext* drives in general through its Linux kernel and utilities, Crouton and the likes can still use it, and people who specifically need to use the files app for whatever reason have plenty of choices for a file system.