4 ms·
I hope they will some day implement variadic types: https://github.com/Microsoft/TypeScript/issues/5453 https://github.com/Microsoft/TypeScript/issues/5453. Als
by huy-nguyen 8y ago
I hope they will some day implement variadic types: https://github.com/Microsoft/TypeScript/issues/5453 https://github.com/Microsoft/TypeScript/issues/5453. Also, the plan for a 3.0 release looks a bit underwhelming: https://github.com/Microsoft/TypeScript/wiki/Roadmap#30-july-2018 https://github.com/Microsoft/TypeScript/wiki/Roadmap#30-july.... Why not call that 2.10?
- praxxis 8y agoSemVer - "Note that this PR is technically a breaking change since unknown becomes a reserved type name", from https://github.com/Microsoft/TypeScript/pull/24439 https://github.com/Microsoft/TypeScript/pull/24439 which is the first item in the list.
- frankpf 8y agoI don't think TypeScript follows semver. TypeScript 2.9 is not compatible with 2.8.
- deleted 8y ago[deleted]
- Scarbutt 8y agoAlso, the plan for a 3.0 release looks a bit underwhelming They have added a ton of language features and keep adding more with each release, lets hope it doesn't get bloated as scala.
- pudebe 8y agoExactly. For my taste they already added too many language features, which each time raises the mental bar to use it when you didnt use it for a couple of month.
- amzans 8y agoIMO Scala has a lot of very well thought out features that complement each other, and this is only going to get better with the move towards Dotty. For me it feels not as bloated as other languages which added features without thinking about how they fit to the existing ones. But I work a lot on Scala, so I'm probably biased since I know the language better than i.e. Typescript :)
- Cthulhu_ 8y agoThe problem / challenge is that there is too many choices, too many ways to tackle a certain problem, and every library you find will have a different method. Plus each one introduces some university / Phd level mechanic that most developers (e.g. me) don't understand.
- amzans 8y agoI understand the problem with that, and agree with you. While it can be very empowering to have a "sandbox" language, when it comes to shipping features and working in a team setting, it can require a lot of discipline to keep the codebase approachable for others. Languages like Go or even Python seem to help a lot in there by having strong conventions and an "obvious" way to do things.