I don't think any of his technical arguments hold up. I'm also not sure that he would have convinced the Bootstrap team to have dropped this based on technical arguments if he hadn't seemed so annoyed, and made repeated references to how only people who speak the language should make certain decisions.
Some examples:
* the bug report is a command: "Stop developing RTL for Bootstrap!"
* the bug report ends with an exclamation point!
* the bug starts "I'm really annoyed..."
* "use cases that only natives can understand"
* A second command, bolded: "Remove it!"
I personally was inconvenienced by this because I was writing lots of bootstrap based .less, and if twitter and Bootstrap had worked together on an auto-flipping rtl system for Bootstrap then all the RTL users of my code would have got a far better service. Instead only those who use the Bootstrap CSS essentially as-it-comes get a manually RTL'd version from a 3rd party. A tool that can automate that work sounds like a far better deal for the RTL world, even if it would have annoyed this particular person.
I note that his argument against automated flipping included the fact that you really need one for farsi, one for arabic, etc. Yet he only manually produces one. Maybe with the right tooling he'd have got to where he wanted to be faster.
A link to such a tool: https://github.com/MohammadYounes/rtlcss (note how it documents various solutions to the 'problems' listed in the original bug report, like changing the font stack when in RTL mode)