Flow Type VS CoffeeScript

I love JS, but I want types. I don't want TypeScript though, but I'll do it if the job requires it. Has anyone tried building in flow for a large project? This was facebook's static type checking approach: https://flow.org/. - Source: Hacker News / over 1 year ago

In my examples, I’ll use the Flow type system so that it’s easier to follow the idea. The code consists of two parts: a service API and a recommendation flow. - Source: dev.to / over 1 year ago

You think we could try to make it such that people use JS + Flow the static type checker. Source: over 1 year ago

The two biggest contenders in adding static types to JavaScript are Flow (by Facebook) and TypeScript (by Microsoft). As of date, there is no clear winner in the battle. For now, we have made the choice of using Flow. We find that Flow has a lower learning curve as compared to TypeScript and it requires relatively less effort to migrate an existing code base to Flow. Being built by Facebook, Flow has better... - Source: dev.to / over 1 year ago

Just FYI, Facebook has a JS dialect called Flow. There was a point in time that Flow and TypeScript were duking it out, but clearly TS has won. I think Flow is still used inside Facebook, but I don't think it has really caught on in the larger developer ecosystem. Source: over 1 year ago

JS isn't perfect, but it's good enough. And there is ongoing effort to make it even better. Also, many other languages compile to JS (without WASM). Notably: - https://www.typescriptlang.org/ - https://coffeescript.org/ - https://clojurescript.org/ - https://www.transcrypt.org/ I wrote https://multi-launch.leftium.com, which is only 6% JS. The majority is Svelte (65%) + TypeScript (27%). ( - Source: Hacker News / 4 months ago

As a front-end web developer, do you still use CoffeeScript or jQuery? Unlikely, as TypeScript, ES/TC39 and Babel (and the retirement of Internet Explorer thanks to @codepo8 and his EDGE team) have helped to transform JavaScript into some kind of a modern programming language. - Source: dev.to / about 1 year ago

On the other hand, companies choose React because that's where all the developers are. If you want to build something that can be maintained years from now, you better not choose the next hype train that goes straight to nowhere (remember CoffeeScript ?). You want something battle tested that has stood the test of time, where you won't have trouble finding developers to scale once you need to. And nobody ever got... - Source: dev.to / over 1 year ago

Http://coffeescript.org/#expressions this comes from Lisp and makes a lot of things easier. Obviously this was not implemented in ES6 because it would break compatibility and there is also some problems with implicit returns that made the feature a bit weird I wonder if a syntax like this for JS would work: const eldest = if (24>41) { escape "Liz" } else { escape "Ike" } with "escape" working like a mix of "break"... - Source: Hacker News / over 1 year ago

Coffeescript[1] was a flavour of JS syntax meant to look similar to Ruby syntax. You just compiled it back to JS. It was nice for working on Rails projects since it made everything feel more “cohesive”. I assume this project is here for older Coffeescript[1] projects who want to start using typescript, and need access to interfaces/types that were present in old CS files. [1] https://coffeescript.org/. - Source: Hacker News / over 1 year ago