Ingvar Stepanyan

Looks like this was released, so closing.

Just in case this helps somebody - I've gathered a couple of workarounds for decorating functions in a composable way into one article here: https://rreverser.com/ecmascript-decorators-and-functions/ Let me know if I...

> and stuff like icu4x feels like the wrong choice for code which cares about footprint Oh yeah so I actually did try to use icu-properties for this couple of...

Technically, this is currently supported via JSX spread like ``` javascript ``` but I totally agree that having short syntax for separate properties would be a great addition.

@NekR I'm not sure I see benefits of inventing own `babel-plugin-jsx` over setting `jsxPragma` in Babel to own runtime.

Well, it's not really that specific and easy to write runtime that would just covert those calls into your own builders (instead of writing completely another transpiler plugin).

@NekR I just don't see where is "stick to React infrastructure". Function calls are the sanest way of constructing, optimizing and modifying objects, and they're not React-specific at all, as...

@trueadm Nothing stops you from writing a function that returns cached value, and in fact you'll get direct inlining in any modern JIT including V8, just as you do with...

> so say then so to Facebook React and ask them to stop doing optimizations here facebook/react#3228 Those optimizations are in separate optional transformer and it doesn't impact you at...

> I assume it would be hard to incline you and Babel community to develop additional feature to JSX output which is not used by the React, since you are...