MarcusBrutus
Joined 13 years ago
Joined 13 years ago
http://mperdikeas.github.io/stack-piling-and-tumbling/index....
(click "start dropping grain" to start)
Github repo: https://github.com/mperdikeas/js-react-stack-piling-and-tumb...
All the great economists of the liberal tradition up to and including Von Mises wrote monumental works without the need for equations. It was Keynes who first used mathematics both as a quest for respectability (Physics Envy) and as a way to convince credulous politicians like FDR that this stuff is complex and best left at "experts". The disastrous results are still with us today. And no, Keynesian politics did not end the Great Depression, they actually prolonged the misery and it took WWII and the destruction of all global competition to end it.
Not to mention that what passes as "mathematics" among the economists is laughable among mathematicians. Latin was employed towards similar ends by the Roman Catholic Church (although a plausible defense could be mounted that a standard language better preseved the Doctrine against heresy). Ditto for the complex models sometimes employed by astrologists.
A con game, 'nuff said.
Otherwise, can you please explain why bother implementing a transpiler if the emitted sources are identical to the input sources minus the annotations?
Even the names should give you a hint: "TypeScript" is a language name (the microsoft version of ECMAScript more specifically). "Flow" is not. That's why it's called "Flow" and not "FlowScript".
(1) It is less intrusive. Flow's type system is built on annotations which are simply stripped away at runtime (as opposed to writing in another - albeit similar - language that gets transpiled to JS. Sure the transformations are always "file-local" as TS folks say but still it is another, totally unecessary level of abstraction and transpilation.
(2) Flow's type system is at least equally and quite possibly much more expressive and nuanced than TS.
(3) Flow annotations can be applied in a much more piece-meal way than TS.
(4) zero issues integrating with 3rd party libraries (because of 1) - and that includes the ability to type-check said 3rd party libraries (which is a breeze with flow-typed)
(5) To take advantage of TS you have to write JS code in the "JS with classes" style (a.k.a "JS for C# coders"). In contrast Flow allows you to take advantage of its type checking while coding: (a) in idiomatic JS (prototypes) (b) in JS with classes (c) any combination and mix of the two approaches. Flow feels a lot less opinioned as to your JS programming style.
(6) Flow it is not coming from microsoft (but hey, don't you know we've changed, please give us another chance and we won't fuck you over this time, please we love you so). TS team is trying very hard (perhaps too hard) to distance themselves from the negative brand value of microsoft
(7) Flow is not a blueprint for the Mother of all embrace-extend-extigunish strategies (see #6).
Seconds since the Epoch is unambiguous, eschews time zones, daylight savings time and other man-made concepts (it makes sense to Martians too). Plus it only requires an INTEGER type in the database which every RDBMS provides (so is migration safe). You also create demand for your future colleagues (or future self) around 2038. Or you can use BIGINT if that bothers you.
Additionally, crossing the Atlantic served as a filter to select only those people that were truly desirous of becoming Americans. Disgruntled EU voters have the nasty habit of lingering around.