I thought that too. What a bizarre phrase to apply to a language he clearly loves. Enterprise level type checking normally means supporting pretty much just the concept of "classes" (ala Java) and calling it a day - leaving the developer(s) to take the burden and create all sorts of god awful "design patterns" to work around fundamental flaws in their language of choice.
I know that is not the case with TypeScript. I believe the recent version added support for union types which is going to blow the mind of the naive JavaScript masses, for sure.
Describing any language as "enterprise grade" is rarely a good thing. Wording and phrasing is important.
Oh come on, you're not even trying. He means, the type checking and refactoring capabilities that you want to have in a large team that relatively quickly changes composition. I.e. the kinds of teams you often find in enterprises.
I doubt Google doesn't use any of the type checking and refactoring tools that come with all Java IDEs out there. You think they rename Java methods with command-line search&replace just to stay in touch with their inner startup? Come on. They're an enterprise like any other and they use what the OP calls "enterprise-level type checking and refactoring capabilities".
I agree that it's a stupid name but I think you're misunderstanding on purpose.
>* Oh come on, you're not even trying. He means, the type checking and refactoring capabilities that you want to have in a large team that relatively quickly changes composition. I.e. the kinds of teams you often find in enterprises.*
I rarely find such large teams in enterprises.
What I usually find is ad-hoc projects, some in VB6, some targeting IE6 in 2016 still, others in J2EE with "enterprise" application servers, etc. Most done by 1 to half a dozen people. And I don't see them "quickly changing composition" -- the same persons work in the same IT deps for decades...
>I doubt Google doesn't use any of the type checking and refactoring tools that come with all Java IDEs out there. You think they rename Java methods with command-line search&replace just to stay in touch with their inner startup?
No, I mean there's nothing enterprisey about refactoring.
Well, of course. Old geeks are screwed on startups and startup-y companies.
The enterprise IT (and the financial sector, major organizations, etc) are the places where old geeks are quite ok -- if not to hire, surely to keep past 40 and 50 when they have already been working for you. The median age in an IT department in a large enterprise is much higher than in any SV startup.