I’m very happy to see these changes. We are avid users of Flow on a few large codebases and parse/merge speed has gotten to be a problem, especially on a combined React/React Native codebase.
I have also noticed some of these holes in Flow’s coverage, which are difficult to detect (you usually have to introduce a type error…
Very surprised to see all the negative comments on this post. Azer was far ruder to you, Mike, than I would have expected.
Isaac’s capitulation here was precisely because he understood the legal landscape, and had likely handled requests like this before. If Kik decided to actually put lawyers on it, they’d win.
Behave like a child, be treated like one.
The OP is disingenuous from the very start. Making one’s modules less available is not “liberating” them. Unpublishing hundreds of modules that are vitally important to the ecosystem is the very definition of a “knee-jerk reaction”.
I contribute dozens of libraries to the JS ecosystem, some of them very widely used. Just because a package is libre does not mean it is responsible to pull it from repositories and break thousands of builds, just because it is “yours”.
This is a ridiculous thing to do when you know that a major part of the JS ecosystem depends on — and pins to — your packages. By unpublishing, you broke every npm build that depends on Babel (which is a major demographic) in order to assert a point about an unrelated package.
This is a nice article. The tooling is getting better all the time. I’m a big fan of trace.gl, although Chrome’s Profiler/Timeline is starting to make it easier to do this kind of work.
I respect the work you’re doing on rfx and rtype, but it is a bit disingenuous to not mention the fantastic work being done on Flow and…