Re:The Great CoffeeScript to Typescript Migration of 2017
by karatestomp on Friday May 15, 2020 @06:13PM
(#23198140)
Yeah, just getting rid of the "interesting I guess but I'd never use them on purpose because they're just not helpful and likely to cause confusion or bugs" parts of JS, like direct fiddling with prototypally-inheriting objects (ew), worrying a bunch about what "this" means and shuffling it around for little to no useful reason, or entirely-unhelpful scoping rules. Most of those are better in regular JS now. For me, the syntax was at best neutral, leaning toward undesirable. I just wanted the extra ergonomics and safety, which didn't require such a departure from JS.
[ Parent
| on HN ]
There are no comments on this comment yet.