News for hackers. Stuff that matters.

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

Re:How we connected React.js to C in an industrial product a... by GiovanniFrigo on Thursday October 29, 2015 @09:17AM (#10470708)
I get your point here, but since the bundled Chromium version is compiled by ourselves we do not rely on an external toolset, allowing us to support just one version at a time. If you're intrested, we use Sparkle (http://sparkle-project.org/) to deliver remote software updates.
[ Parent | on HN ]
Re:How we connected React.js to C in an industrial product a... by creshal on Thursday October 29, 2015 @09:43AM (#10470889)
> allowing us to support just one version at a time.

On the flipside, each program has to maintain the whole stack themselves, and have to push out security updates if necessary. I'm not sure this is an improvement over Java's security situation…

[ Parent | on HN ]
Re:How we connected React.js to C in an industrial product a... by mpitt on Thursday October 29, 2015 @10:09AM (#10471071)
I see it like this: 1) let the user handle the security updates of the JVM; 2) push out security updates in a centralised, controlled fashion.

IMHO, in a corporate solution like that described in the OP, 2) makes a lot more sense.

[ Parent | on HN ]
Re:How we connected React.js to C in an industrial product a... by leolanzinger on Thursday October 29, 2015 @10:07AM (#10471049)
didn't get your point honestly
[ Parent | on HN ]