Arthur Stolyar
Arthur Stolyar
@Alxandr Hmm.. interestingly, why?
@Alxandr yes, good reason. But there might be a problem with current `` which in supported implementations means `foo.Bar()` (or `create(foo.Bar)`) and if `` will translate just to `{'foo.bar': ''}`...
Karabiner actually works on me on macOS Sierra except of per-app configs. Any idea it's possible to fix that? (Karabiner-Elements doesn't support per app config either)
Just made little PR #22 for the case that all will agree with this feature. @RReverser can you review it?
@sebmarkbage [Here](https://medium.com/@nekrtemplar/jsx-everywhere-a6ee99290e0d) I believe now is another consumer of JSX :-)
@RReverser that is explained in blog-post, but in short, Babel emits React-specific calls even with changed pragma (traspiling there also is called React, not jsx, btw). Inlined output also is...
@RReverser See https://github.com/facebook/jsx/issues/29#issuecomment-76677259 and next comment. /cc @sebmck
@RReverser well, what is a problem with separate compiler plugin? Also, why then react team is about to optimize their output and use inline object instead of functions calls? I...
@RReverser Why is Babel central implementation and why then have the spec at all? Imagine Brendan Eich and Mozilla are saying -- why v8, let's stick to one central implementation,...
@sebmck it will be handled by the functions anyway, but just later. Stack traces point sounds fair, but there is always are trade-off between usability and performance. Function calls probably...