I Was Wrong About TypeScript
triplet.fi
I Was Wrong About TypeScript
1–10 of 194 posts
Re: I Was Wrong About TypeScript
#2Having avoided typescript thus far, I really appreciated this take. Thank you for sharing it!
Re: I Was Wrong About TypeScript
#3Another good alternative is Facebook's flow. Rather than being a transpired language it works on top of JavaScript files.
This two tools are amazing and it improves working with JavaScript to the point of never wanting to go back to not typed JavaScript
Re: I Was Wrong About TypeScript
#4Been using typescript since its introduction. It really helped me improve my JavaScript code quality and most importantly it's really good at keeping large projects tidy and easy to comprehend.
Re: I Was Wrong About TypeScript
#5I recently started learning TS after reading a previous HN post on it (https://medium.com/@basarat/typescript-won-a4e0dfde4b08) and listening to the JS Jabber episode with Anders Hejlsberg himself explaining the benefits (https://devchat.tv/js-jabber/209-jsj-typescript-with-anders-...). These two (plus knowing that Angular 2.0 is going to be much easier with TX) totally sold me on learning it. I'm in the middle of this Pluralsight course: https://app.pluralsight.com/library/courses/typescript-in-de.... Besides the benefits of TS, I'm learning how perfect VS Code is for writing it. I've been a big proponent of WebStorm in the past, but VS Code is really shining for this type of work.
Re: I Was Wrong About TypeScript
#6Ashamedly at one point I was on the anti-Angular 2 bandwagon due to Typescript, because Microsoft. When I started learning Angular 2 myself I've found I actually enjoyed working with Typescript, for many reasons. (confidence that my code wasn't a ball of mystery before it ran, using inline templates, succinctness of annotations, etc)
At the same time, you're gonna need to use some preexisting libraries, and run into the issue of not having types available. (though they do exist for most mainstream libs) However, I found creating types for any given lib pretty flexible, and that you can usually get away with just enough types.
Re: I Was Wrong About TypeScript
#7I prefer frameworks that focus on pure javascript because the ones that don't tend to allow you too use javascript but have sparse documentation on how to use it effectively, instead focusing on typescript. When I first tried Angular 2 their javascript "hello world" example wouldn't even work, it was some bug in their site. I already need to use all sorts of other tools and abstraction layers when building websites/apps, typescript feels like just another abstraction layer (which it is), that means another vim plugin for typescript (or a bloated IDE), another npm dev dependency, another layer to the build process, so I try to avoid it for these reasons.
Re: I Was Wrong About TypeScript
#8Last week was my first week trying out Angular2 + TypeScript. I use mostly Java & C# at my day job. I was actually a really shocked at how fast i was able to gain a working knowledge of TypeScript. The only thing i don't like is my project has extra files everywhere (.js + .ts). However there is probably a way to make my IDE hide them or something.
Re: I Was Wrong About TypeScript
#9Another good alternative is Facebook's flow. Rather than being a transpired language it works on top of JavaScript files. This two tools are amazing and it improves working with JavaScript to the point of never wanting to go back to not typed JavaScript
You're absolutely right. Flow seems to be a very good alternative.
One thing I would like to add regarding the .js files, TypeScript 1.8 added a flag --allowJs which makes some sanity checks to the plain old .js files.
Re: I Was Wrong About TypeScript
#10I recently started learning TS after reading a previous HN post on it ( https://medium.com/@basarat/typescript-won-a4e0dfde4b08 ) and listening to the JS Jabber episode with Anders Hejlsberg himself explaining the benefits ( https://devchat.tv/js-jabber/209-jsj-typescript-with-anders-... ). These two (plus knowing that Angular 2.0 is going to be much easier with TX) totally sold me on learning it. I'm in the middle o…
WebStorm does offer syntax highlighting of HTML inline templates, but I'm sure that's a matter of time before that feature comes to VS Code. I do think that WS does provide a nice workflow at the expense of a much heavier tool.