News for hackers. Stuff that matters.

A comment on Designing very large JavaScript applications.

Re:Designing very large JavaScript applications by TAForObvReasons on Friday April 20, 2018 @04:56PM (#16888374)
> This Javascript framework is not open source. The reason it is not open source is that it kind of came out at the same time as React and I was like “Does the world really need another JS framework to choose from?”. Google already has a few of those–Angular and Polymer–and felt like another one would confuse people, so I just thought we’d just keep it to ourselves.

Given the current state of affairs, an open-sourcing of this framework would be welcome.

[ Parent | on HN ]
Re:Designing very large JavaScript applications by leetrout on Friday April 20, 2018 @05:32PM (#16888597)
Do you have some specific reason for this (genuinely curious)?

Think we've put ourselves in a corner, so to speak, with the Angular, react, preact, vue, ember, etc etc options and this would offer something compelling from the authors examples?

[ Parent | on HN ]
Re:Designing very large JavaScript applications by TAForObvReasons on Friday April 20, 2018 @05:39PM (#16888646)
The article discusses one of the major problems: "React component statically depend on their children." There are workarounds, sure, but there are all kinds of pitfalls with the dynamic workarounds, to the extent that I find myself breaking the react model regularly in applications (e.g. utilizing state outside of redux and forceUpdate)
[ Parent | on HN ]