4 ms·

> 1) Operator overloading Please, please, please, no.

by farnsworth 7y ago

mattigames 7y ago
You know it would be completely transparent right? Just gets transpiled into .__add__(obj)
- jakelazaroff 7y ago
  The explicit goal of TypeScript is to be JavaScript, with types — i.e. not introduce any features not likely to land in an ECMAScript spec.
  - mattigames 7y ago
    Which is a shame because JavaScript is constrained due needing backwards-compatibility above all (among other issues) but TypeScript isn't
    - MaulingMonkey 7y ago
      Not much of a shame IMO - there are plenty of other languages that transpile to JS without those goals, if you don't care about backwards compatability and 1:1 mappings to vanilla JS. On the other hand, there's only one language that I'm aware of - TypeScript - prioritizing these things, which is a major selling point of it to me. I don't want yet another leaky abstraction, or yet another runtime heavy enough for those abstractions to not leak. I just want enough types for my intellisense to work right, and for my sorry ass - spoiled by years of nothing but static typing systems - to be able to code without drowning in a veritable sea of uncaught type errors to debug, when I poke frontend stuff.
      - ujoh1 7y ago
        Hello See also how you can start making steady daily passive incomes on virta stock trading without you risking your money and your investment visit the website here http://www.virtatrade.com/index.php http://www.virtatrade.com/index.php for more details
      - mattigames 7y ago
        Typed and those features? there isn't a single one. But yeah, maybe what I need is a fork of TypeScript with those features (or maybe some sort of plugin)
- watt 7y ago
  We already saw this play out in Scala. People end up abusing these to create absolutely unreadable "DSL"s. Even when it's tastefully done, for example the "!" and "?" operator for messages in Akka, it's not better than the names "tell" and "ask".
  - mattigames 7y ago
    Fair enough.

> 1) Operator overloading Please, please, please, no.

mattigames 7y ago

You know it would be completely transparent right? Just gets transpiled into .__add__(obj)

jakelazaroff 7y ago
The explicit goal of TypeScript is to be JavaScript, with types — i.e. not introduce any features not likely to land in an ECMAScript spec.
- mattigames 7y ago
  Which is a shame because JavaScript is constrained due needing backwards-compatibility above all (among other issues) but TypeScript isn't
  - MaulingMonkey 7y ago
    Not much of a shame IMO - there are plenty of other languages that transpile to JS without those goals, if you don't care about backwards compatability and 1:1 mappings to vanilla JS. On the other hand, there's only one language that I'm aware of - TypeScript - prioritizing these things, which is a major selling point of it to me. I don't want yet another leaky abstraction, or yet another runtime heavy enough for those abstractions to not leak. I just want enough types for my intellisense to work right, and for my sorry ass - spoiled by years of nothing but static typing systems - to be able to code without drowning in a veritable sea of uncaught type errors to debug, when I poke frontend stuff.
    - ujoh1 7y ago
      Hello See also how you can start making steady daily passive incomes on virta stock trading without you risking your money and your investment visit the website here http://www.virtatrade.com/index.php http://www.virtatrade.com/index.php for more details
    - mattigames 7y ago
      Typed and those features? there isn't a single one. But yeah, maybe what I need is a fork of TypeScript with those features (or maybe some sort of plugin)
watt 7y ago
We already saw this play out in Scala. People end up abusing these to create absolutely unreadable "DSL"s. Even when it's tastefully done, for example the "!" and "?" operator for messages in Akka, it's not better than the names "tell" and "ask".
- mattigames 7y ago
  Fair enough.