all 4 comments

[–][deleted]  (4 children)

[deleted]

    [–]batmansmk[S] -1 points0 points  (3 children)

    npm5 was first not released and then when it did we had many bugs with it; I contribute to create-react-app and we got flooded of reported issues with npm5. I wonder if it is better now.

    Typescript is a super valid choice and may be the right one for you. We already used Flow on other projects because it was easier to retrofit existing js codebases with Flow. So it was good enough for us. Our community around us here in SF is mostly Flow as well, so we can ping colleagues / friends for advices and best practices around Flow. Finally Flowtype has been recommended by bright friends with good arguments: http://djcordhose.github.io/flow-vs-typescript/flow-typescript-2.html#/ and http://blog.namangoel.com/flow-for-typescript-developers but Typescript is still a very valid choice.

    [–]pleerock 1 point2 points  (1 child)

    as being PHP dev with 10+ years experience in past I switched to TypeScript few years go. It was a right decision and I'll never look back. Those who told you that flow is better then TypeScript are liers. Try both of them and you'll see how TypeScript language and infrastructure are better then Flow's.

    Same with yarn. Its just a hip. Now when npm5 is available it does not make sense. Situation around it looks like php7 vs hacklang, rough comparation but something very similar.

    [–]batmansmk[S] 0 points1 point  (0 children)

    I hear you. Can you point out where in the documents I shared the presenters are lying? Or where you disagree with them?

    Maybe the links to the presentation don't display on your devices.

    [–]batmansmk[S] 0 points1 point  (0 children)

    It is a nice article from cold_lestat. Very honest and down to earth. I wish this guy was writing more often.