Flow vs. Typescript

Re:Flow vs. Typescript by chvid on Monday June 06, 2016 @05:10AM (#11845471)

Let's pick an example:

    function renderMarkdownToHtml(text)

And with static types:

    function renderMarkdownToHtml(text : String) : String

Well-defined interfaces is mostly not about types.

[ Parent | on HN ]

Re:Flow vs. Typescript by glibgil on Monday June 06, 2016 @05:24AM (#11845511)

When you want

    function render(markdown : Markdown) : Html

then you will see the reason for types (and lots of them)

[ Parent | on HN ]

Re:Flow vs. Typescript by chvid on Monday June 06, 2016 @06:01AM (#11845606)

Yep.

And there you have it.

Two different approaches to buidling software.

Which is more productive, which yields higher quality?

I have build plenty of software both ways. And my answer is a confident "it depends". But I will tell you this: A fine-grained type hierarchy over either Markdown or HTML opens up a very big can of worms.

All this reminds me of SOAP vs. HTTP/JSON: I have seen plenty of SOAP webservices seriously stuffed up regardless of/because of strong typing whereas developers seem to do much better with HTTP/JSON because of the simplicity and directness of the approach.

[ Parent | on HN ]

Re:Flow vs. Typescript by chii on Monday June 06, 2016 @05:46AM (#11845572)

does renderMarkdownToHtml return a string or does it return a DOM element?

[ Parent | on HN ]