How we connected React.js to C in an industrial product and everything went ok

Re:How we connected React.js to C in an industrial product a... by 2bluesc on Thursday October 29, 2015 @11:11AM (#10471614)

> So instead of updating Java, we now have an ecosystem where everyone and their dog are shipping their own bundled Chrom(e|ium) instead, which surely is not going to cause even more upgrade-related problems in the future.

And each install wastes an impressive amount of space.

[ Parent | on HN ]

Re:How we connected React.js to C in an industrial product a... by GiovanniFrigo on Thursday October 29, 2015 @04:30PM (#10474054)

I won't call 120 MB (total weight of our app, including assets) an impressive amount of space. Also consider it's something people will use for work purposes, an unique configuration tool instead of having 3 or 4 small tools to configure each single meter type.

[ Parent | on HN ]

Re:How we connected React.js to C in an industrial product a... by GiovanniFrigo on Thursday October 29, 2015 @06:52PM (#10474975)

Errata corrige: 84 MB. 120 was the debug build!

[ Parent | on HN ]