As Dave said, let’s see how this plays out at Facebook, but it’s currently not looking too great.[1]
My understanding is that it would preclude a reactjs component set, but I could be wrong. [1]https://github.com/facebook/react/issues/10191#issuecomment-315707719 <https://github.com/facebook/react/issues/10191#issuecomment-315707719> > On Jul 17, 2017, at 1:09 PM, Yishay Weiss <yishayj...@hotmail.com> wrote: > > Does that rule out a reactjs component set (ala createjs)? > > From: Harbs<mailto:harbs.li...@gmail.com> > Sent: Monday, July 17, 2017 12:47 PM > To: dev@flex.apache.org<mailto:dev@flex.apache.org> > Subject: Re: FYI: React appears to be a no-no > > No. > > I just thought this was newsworthy. > >> On Jul 17, 2017, at 10:27 AM, Alex Harui <aha...@adobe.com.INVALID> wrote: >> >> I"m not following. Do we currently have a required dependency on React? >> >> -Alex >> >> On 7/16/17, 6:19 AM, "Harbs" <harbs.li...@gmail.com> wrote: >> >>> The incompatibility of React’s license is potentially significant for >>> FlexJS.[1] >>> >>> [1]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues >>> .apache.org%2Fjira%2Fbrowse%2FLEGAL-319&data=02%7C01%7C%7C4c6a9d8c95534e63 >>> 772208d4cc4d45db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636358079641 >>> 383681&sdata=Ag6aXVH9z9XDazv6hpTakzzcNA%2BdIUBrCS1sYTLGTho%3D&reserved=0 >>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.a >>> pache.org%2Fjira%2Fbrowse%2FLEGAL-319&data=02%7C01%7C%7C4c6a9d8c95534e6377 >>> 2208d4cc4d45db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63635807964139 >>> 3686&sdata=KeNChB38k71gekwa0h%2Fq6P8P3VN%2FbB2TYzICzB%2BosTo%3D&reserved=0 >>>> >>> >>> >> >
