Re:The Great CoffeeScript to Typescript Migration of 2017
by jessaustin on Saturday May 16, 2020 @08:38AM
(#23202910)
Your comment above seemed to refer to constraints in the other direction: "we can't use Lisp because the only coders available to hire only know Java!" The point is, coffeescript and javascript are much more similar than that, especially now that javascript has imperfectly copied some of coffeescript's improvements.
Re:The Great CoffeeScript to Typescript Migration of 2017
by dgoldstein0 on Saturday May 16, 2020 @05:37PM
(#23207408)
It's not we can't use it, but rather using it for everything would make hiring, onboarding, and retention tougher, as well as maintenance.
Apologies if I have the wrong impression in the earlier post.
You might even guess that the "old guard" could have been against such a migration. As someone who should have been a member of that, I wasn't a fan of changing... But then got a few rude reminders from debugging coffeescript that didn't mean what I meant to write. At which point I started thinking that maybe everyone else had a point.