The same thing. As for TODO it’s completely out of row.
Zero TODO policy might be a good practice from the standpoint of issue tracking and project management.
From the perspective of code quality a better argument would be “todo’a in code encourage people to postpone refactorings and write bad code”. That’s arguable, but is at least about code quality, not something different.
After glancing over the article I can identify at least those points;
- helpers, many of them, but at least think about if/each/with
- template syntax validation at compile-time
- strict check of data
- auto-escaping (is it context-aware?)
- syntax highlighting for templates
technically all of them except highlighting could be solved with templates and several lines of code, but it’s like jQuery vs native DOM API. The former is more convenient.
Even though the article starts with “I love CoffeeScript “ and cite “researches” w/o getting references, it introduces a good point that “TypeScript isn’t only about static typing checks per se”.
Actually, yes. That size of 3.2kB isn’t very informative.
Adding the size of a slightly bigger app would help in improving understanding Ivy’s real power.
Can we write a simple app w/o adding half of the RxJS to the bundle?
That’s how it’s done in FP except most goodies are already here for you like auto-currying and operators as functions.
Or you can use a lib with those things already here like ramda.