3 ms·
I'm well acquainted with the merits of types in general (I've worked in Java & Scala for years). I'm curious why it's so special on the frontend. I can't tell
by shay_ker 8y ago
I'm well acquainted with the merits of types in general (I've worked in Java & Scala for years).
I'm curious why it's so special on the frontend. I can't tell if it's just part of the Javascript hype-train, or if there's legitimately something different about the frontend.
- quickthrower2 8y ago> I'm well acquainted with the merits of types in general (I've worked in Java & Scala for years). That's your answer - same merits for the front end.
- shay_ker 8y agoHm... I feel like that's not quite the full picture. On the backend, for instance, there are options - if you like typed languages, use them! And if not, use something else! But there appears to be a particularly strong movement towards TypeScript. I just can't tell if it's just yet another JS hypetrain, or if there is something else besides types that's a big win.
- mattmanser 8y agoBecause JavaScript is (still) a cluster fuck, where there is no formal, or even informal, shared code style and it often turns into a giant mess. Typescript makes it a little less likely you muck up, plus you can use new stuff like string interpolation without ever having to think about browser compatibility.
- madmaniak 8y agoIt's Microsoft paid. Before you had React - FB paid and before Angular - Google paid. For example Angular 1 was also promoted like - it's made by Google, so it makes sense. It didn't - Angular 2 is incompatible with 1 and rejects most of initial ideas. All these giants supported also by governments can change trends however they want. You call it a hypetrain.