Flow

15 engineers on Hacker News describe using Flow first-hand: 2 endorse it, 8 regret it, 1 are mixed.

28%trust
15first-hand users
15in production
endorse 2mixed 1regret 8uses, no opinion

“I spent inordinate amounts of time updating our code for the latest breaking Flow version, until one came along that would have taken too long to update for”

regret · production · dwb · 2024-07-25 · source ↗ · wrong label?

“The language server was slow in the best of times, would crash constantly, would memory-leak all over the place.”

regret · production · brundolf · 2023-03-16 · source ↗ · wrong label?

“keeping up with the constant breaking changes... led to me getting disenchanted and burnt out with Flow.”

regret · production · spoiler · 2023-03-16 · source ↗ · wrong label?

“almost invariably come to regret some of the choices that I, or our team, have made (which include... React, Gatsby, Flow, Stylus, Enzyme, Jest, SCSS”

regret · production · just_a_username · 2022-12-15 · source ↗ · wrong label?

“I almost invariably come to regret some of the choices that I, or our team, have made (which include... React, Gatsby, Flow, Stylus, Enzyme, Jest, SCSS”

regret · production · azangru · 2022-12-06 · source ↗ · wrong label?

“I worked on a project that used used Flow 3 years or so ago... This is my deepest regret of leaving Flow.”

endorse · production · 3 yr · azangru · 2021-11-03 · source ↗ · wrong label?

“we migrated our entire frontend codebase from Flow to TypeScript and we're happier for it.”

regret · production · Raed667 · 2021-06-18 · source ↗ · wrong label?

“we've been using Flow for JavaScript on our team for a while and we can't get over a lot of the problems we run into with Flow”

regret · production · augbog · 2018-05-11 · source ↗ · wrong label?

“I get to use flow's type system which isn't perfect, but believe me, it's a breath of fresh air after coming from PHP”

mixed · production · adimitrov · 2018-04-24 · source ↗ · wrong label?

“We tried adopting Flow at a company I worked at, but dealing with gibberish errors and the huge meaningless stack traces was a productivity sink.”

regret · production · chmln · 2017-11-09 · source ↗ · wrong label?

“I know that flow has prevented me from checking in bugs, because I've tried to push up code with e.g. misspelled property names”

endorse · production · dwwoelfel · 2016-11-29 · source ↗ · wrong label?

“We don’t upgrade the flow dependency anymore either.”

neutral · production · ickelbawd · 2023-07-18 · source ↗ · wrong label?

“Also we use Flow / Typescript.”

neutral · production · crubier · 2018-12-26 · source ↗ · wrong label?

“it was a fair amount of work to migrate the existing code (especially since we had partially migrated to Flow)”

neutral · production · dgreensp · 2018-05-18 · source ↗ · wrong label?

“makes setting up background services (such as the Flow server) in development way harder than it needs to be.”

neutral · production · RussianCow · 2017-10-27 · source ↗ · wrong label?