JavaScript using Flow
-
-
Replying to @jamiebuilds @thejameskyle
Disappointing. I really wish I felt flow was a good fit for new JS infra projects. Better than Reason or OCaml though.
1 reply 0 retweets 2 likes -
Replying to @wycats @thejameskyle
Maybe getting a few big flow projects will improve flow. I'd like that a lot.
1 reply 0 retweets 2 likes -
Replying to @wycats
Outside of editor integrations Flow seems better at just about everything these days
3 replies 0 retweets 6 likes -
Replying to @jamiebuilds @wycats
And I don't see why the editor integrations can't be powered by TypeScript while using Flow
1 reply 0 retweets 2 likes -
Replying to @jamiebuilds @thejameskyle
Editor integrations, error messages, windows support, ecosystem (linting tools, .d.ts coverage) come to mind
1 reply 0 retweets 2 likes -
Replying to @wycats
In my experience TS error messages have not been noticeably better, Flow supports windows, linting is better (babel-eslint, prettier), ...
2 replies 0 retweets 9 likes -
Replying to @jamiebuilds @thejameskyle
Flow claims to support windows but in practice the background process and memory strategy plays poorly.
1 reply 0 retweets 0 likes -
Replying to @wycats @thejameskyle
Neither babel-eslint nor prettier work the way tslint does. Quick fixes might count as "editor integration" but they're significant.
1 reply 0 retweets 0 likes -
Replying to @wycats @thejameskyle
We're not going to litigate those over Twitter, but I think this view is little too "feature check box" focused.
1 reply 0 retweets 1 like
We should sync up soon either way :)
-
-
Replying to @wycats @thejameskyle
Also, regardless of my nitpicking, this project seems pretty cool.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.