Any plans to add C#-like extension methods to TypeScript? Or is there a way to achieve the same thing already? I know that a previous suggestion to add extension methods was closed as out of scope. But maybe it's time to revisit that, since TypeScript is now doing significant code transformations for downlevel await support.
Announcing TypeScript 2.1
31–40 of 226 posts
Re: Announcing TypeScript 2.1
#32Re: Announcing TypeScript 2.1
#33Incredible release. Was definitely waiting for the spread/rest improvements as well as being curious about the async stuff.
TypeScript continues to be for me the clear winner of the alt.js languages.
Re: Announcing TypeScript 2.1
#34So can I finally banish babel from my build steps?
I did while 2.1 was an RC. It has worked flawlessly and I haven't looked back.
Build and minification is still a pain though...
Re: Announcing TypeScript 2.1
#35If you still haven't given TypeScript a go as a Javascripter, now is a great time to do so. Whether you end up adopting it or not, it's interesting to get the types out of your mind and into the code. The first time you feel the speed/confidence of refactoring with accurate 'Find usages', you'll decide if the undeniable overhead of types is worth it.
I have to second Mr.timruffles. After using TS in a couple of projects I grew to miss it when I couldn't use it. If you don't like the C#-ness of Typescript, try using Facebook's flow. Typing isn't a magic bullet, typescript isn't even type safe, but it sure makes development easier and your apps more stable.
"Typing isn't a magic bullet, ..., but it sure makes development easier and your apps more stable."
That right there is the whole essence of typed programming :)
Re: Announcing TypeScript 2.1
#36Coming from Java land, TS is a life saver for front-end development.
Any plans for .NET Core / CLR backend ?
I think, this will be the silver bullet. TS types should be able to generate statically compiled bytecode => native binary ?
Re: Announcing TypeScript 2.1
#37So can I finally banish babel from my build steps?
The post did not mention anything about babel (or whether it is still needed). Any pointers?
Re: Announcing TypeScript 2.1
#38Been a Linux developer for ages C# was never my taste, I'm still a bit Microsoft-hatred as of now(Visual Studio Code is the only item I adopted for JS development, the rest languages I still use vi/Geany). How tightly TS is related to C#? That has been the main reason I had not tried TS seriously so far. Don't want to have anything to do with C#. I know...
Re: Announcing TypeScript 2.1
#39It's interesting to me that all of the initial reactions I've seen to this announcement have been around the introduction of async and object spread, which are available with babel, but the typescript specific features such as mapped types are completely ignored. I don't really have any particular meaning behind that observation, only that it tickled my funny bone a little bit.
Maybe it is me, but I feel like mapped types and keyof are terrible features, and using them would be a sign of a bad design/architecture.
In general, I don't think using a string that represents a static symbol (such as the name of a var, an attribute or a class) is a good idea.
I try to keep a simple stack (Typescript + NPM at the moment), and I prefer to wait for Typescript to have the feature I want, than to install a new dependency (Babel, for example) to my project.
Re: Announcing TypeScript 2.1
#40If you still haven't given TypeScript a go as a Javascripter, now is a great time to do so. Whether you end up adopting it or not, it's interesting to get the types out of your mind and into the code. The first time you feel the speed/confidence of refactoring with accurate 'Find usages', you'll decide if the undeniable overhead of types is worth it.
> The first time you feel the speed/confidence of refactoring with accurate 'Find usages', you'll decide if the undeniable overhead of types is worth it.
For your information: in VSCode, the "Find all references" and "Rename symbol" work out-of-the-box, even if your code isn't typed.
Edit and disclaimer: Not sure why I'm getting downvoted, my comment doesn't contradict parent message. I personally type my code too (with Flow), it's an amazing tool for static code analysis and avoid errors at the runtime. I would suggest everyone give it a try (with TypeScript, Flow or whatever).