News for hackers. Stuff that matters.
Re:Announcing TypeScript 2.0 by cakoose on Thursday September 22, 2016 @05:02PM (#12560346)
> I'll never join a company that uses TypeScript unless I get to see the code base first.

That seems reasonable. But wouldn't the same thing apply to Javascript? Terrible Javascript code bases are very common.

Re:Announcing TypeScript 2.0 by shados on Thursday September 22, 2016 @08:11PM (#12561404)
Generally the terrible JavaScript is stuff you don't have to argue until you're blue in the face to avoid. A lot of people have bad JS code base, but they know they are bad and are trying to do better. That's fine by me.

For this particular stuff, if a team is really into the whole OOP/classes things, it's not like a small feature like arrow functions vs not, or semi-colon vs not... it will dictate the entire architecture of the entire code base, and it's easy to detect, so why not?