2 ms·
And I used plain JavaScript for my latest project, not because 'I wanted to make money' (or lose money) but because that removes one barrier to contribution by
by jacquesm 3y ago
And I used plain JavaScript for my latest project, not because 'I wanted to make money' (or lose money) but because that removes one barrier to contribution by outsiders. Requiring a compiled toolchain and a second language (some of the libraries the project relies on are in JavaScript) is a step up from just a browser and a text editor (and in the case of a GitLab hosted project: just a browser). JS is a terrible language, let there be absolutely no doubt about it. But TypeScript is not what browsers run.
It's nice that the author puts their main reason for using this particular tool up front: they want to make money. But wanting to make money is not necessarily correlated with the use of TypeScript, JavaScript or any other programming language. And it misses that 'wanting to make money' even if it does correlate with the use of TypeScript would still be a preference.
Finally: what's missing from the story about the typo is why there wasn't a system around all of this code that would notice that a particular KPI's relationship to another KPI came in wildly outside of the predicted range. Obviously: typed languages are great, but typos can happen in any language and such a defense-in-depth strategy against silly mistakes will benefit you regardless of the kind of language that you use.
Awaiting the 'we use Rust because we want to make money' blogpost that is sure to follow.