Yeah no worries Carlos. I’ve been getting the same impression too. I'm totally down to move with what the team decides.
I think a name change is fine after 3 years when the “migration link” is less important as most people who want to migrate will have already well underway if not mostly completed. Just wanted to get my thoughts up there before a [VOTE] thread hits. Loving your thoughts and insights on the name change and this discussion overall. Cheers, Chrsmrtn Sent from my Windows 10 phone From: Carlos Rovira<mailto:carlosrov...@apache.org> Sent: Wednesday, September 13, 2017 3:45 PM To: dev@flex.apache.org<mailto:dev@flex.apache.org> Subject: Re: [DISCUSS] Name of the FlexJS Fork Chris, 2017-09-14 0:37 GMT+02:00 Chris Martin <chrsm...@outlook.com>: > > As for the JS being apart of the name, I’m not too worried about it. Since > we’re still in pre 1.0, I’d imagine we’re still working on stabilizing and > getting that conversion to JS to work seamlessly? Once that has stabilized > I can totally see us “cross compiling” to Android, iPhone, etc. were > naturally we’d want to loose the “JS” part of the name. That I can only > figure would land around 3 years down the road? I honestly don’t have a > good beat on where the FlexJS project is at right now. I feel like it’s > close but just not there yet. > > If we all already think the JS suffix is a mistake for a robust name, we should address it now, since it cost many time to get people know and respect a brand. So stick with xxxJS to change it in three years, is for me something we shouldn't do at all, IMHO.
