Andreas Svensson

> It's not a philosophical reason. It's a huge tradeoff in complexity, both for tools and users. Right now it's just "stuff in brackets are JS expressions." Easy for for...

https://github.com/facebook/jsx/issues/39

My main objection would be that if this makes sense... then it should make sense for fat-arrow functions as well, if they choose not to have it JSX probably shouldn't...

@sebmarkbage @RReverser That's how arrow functions work too. PS. And having object children seems like something that is rarely useful.

You can't escape plain text, and even JSDoc/etc doesn't seem to support escape characters (so not even that makes sense). Hence it doesn't make any sense to escape comments, because...

> The reason I noticed this is that most JS engines (including JavaScriptCore, V8) will use more memory to represent the source if it contains any non-ascii characters - one...

This is entirely intentional, facebook/react#480. Summary: Indenting/beautifying code should never affect the outcome, especially as it means all indentation has to carry over into the final code and cannot be...

I can count the number of times I've had to use `{'\n'}` on one hand (and I still prefer it, it's explicit; explicit > ugly) and the thousands of times...

> He shouldn't rack his brain on why layout is different from what he wrote in that block and definitely shouldn't google how to insert extra whitespace in the layout...

I know that at least all of these suffer from it: ``` Button #1 Button #2 ``` These two doesn't even render the same: ``` Button #1 Button #2 ```...