flow is very immature in terms of tooling in comparison with #typescript. But Im keeping eye on both
no worries
-
-
Replying to @martin_hotell @AccoladeInc
We're heavily focused on it right now as a team, I suspect that will change soon enough
1 reply 0 retweets 3 likes -
Replying to @jamiebuilds @thejameskyle and
good to hear! But what I really dislike is that you're not collaborating with TS team at all
1 reply 0 retweets 1 like -
Replying to @martin_hotell @AccoladeInc
Flow has talked to the TypeScript team many times. I'm new, haven't been involved at all...
1 reply 0 retweets 0 likes -
Although I did try to work with them when I was still more actively working on Babel, they weren't interested.
2 replies 0 retweets 0 likes -
Replying to @jamiebuilds @thejameskyle and
Out of curiosity, what instance did you feel we were uninterested?
1 reply 0 retweets 0 likes -
had conversation with Jon about sharing resources or standardizing around an AST
1 reply 0 retweets 0 likes -
Replying to @jamiebuilds @thejameskyle and
don't think that's the perspective the TS team has. I'd avoid making too many claims
1 reply 0 retweets 0 likes -
Replying to @wycats @drosenwasser and
I'm not making claims, I was literally told the team was not interested.
2 replies 0 retweets 1 like -
Replying to @jamiebuilds @thejameskyle and
flow/babel/ts all were a bit standoffish from my outsider perspective.
2 replies 0 retweets 0 likes
another attempt may go differently.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.