Microsoft Announces TypeScript 3.0 (neowin.net)
Microsoft released version 3.0 of TypeScript, which Microsoft describes as an "extension" of JavaScript "that aims to bring static types to modern JavaScript." Quoting Microsoft's Developer Tools blog:
The TypeScript compiler reads in TypeScript code, which has things like type declarations and type annotations, and emits clean readable JavaScript with those constructs transformed and removed. That code runs in any ECMAScript runtime like your favorite browsers and Node.js. At its core, this experience means analyzing your code to catch things like bugs and typos before your users run into them; but it brings more than that. Thanks to all that information and analysis TypeScript can provide a better authoring experience, providing code completion and navigation features like Find all References, Go to Definition, and Rename in your favorite editor.
Neowin reports: With any major version release, it is not unexpected for breaking changes to be introduced and that's certainly the case for TypeScript 3.0. One obvious change is that with "unknown" becoming a new type, it is now a reserved type name and can no longer be used in type declarations. Otherwise, there's a range of API breaking changes due to a number of functions and internal methods being deprecated or being made internal.
On the plus side, TypeScript 3.0 reportedly has improved error messages, along with project references that let TypeScript projects have dependencies on other TypeScript projects.
Neowin reports: With any major version release, it is not unexpected for breaking changes to be introduced and that's certainly the case for TypeScript 3.0. One obvious change is that with "unknown" becoming a new type, it is now a reserved type name and can no longer be used in type declarations. Otherwise, there's a range of API breaking changes due to a number of functions and internal methods being deprecated or being made internal.
On the plus side, TypeScript 3.0 reportedly has improved error messages, along with project references that let TypeScript projects have dependencies on other TypeScript projects.
... we should be looking for a better replacement. JavaScript is one of those languages that became far too popular for the wrong reasons.
" emits clean readable JavaScript"
;)
Just my 2 cents
Extend and absorb Javascript and crush it to Death!
I for one will join the Darkside for that!! It'd be like Darth Vader killing Jar Jar - he'd recruit the entire rebellion!!
Duh, I prefer to write clean, readable Javascript in the first place, instead of leaving that job to some obscure compiler.
Er, I do not get it, if at the end of the day it ends up as regular javascript that means there cannot be a speed boost of any kind. It does not reduce bug rates of any sort. Other than some programmers who get very angry about javascripts nimble weak type this does not seem to...well to do anything at all really, it just introduces syntax where there was none previously but nothing is being done of any significance. How is that a benefit other than for syntactophiles getting their rocks off about a pretend strong typing that speeds along at the speed of...regular javascript?
A new version release for yet another proprietary crock that I expect to never use.
example:
then Typescript would be Breaking Bad
A better Java minus the suck. Sort of like the webs free Kotlin. Excellent FOSS tooling (Visual Studio Code rocks) and works out of the box with zero-fuss dev-environment setup. It compiles to JS and Webassembly in a breeze and that stuff runs everywhere without anyone having to install some extra awkward VM.
As far as I can tell MS has redeemed themselves a little with TS.
If your planning to build non-trivial applications, check out TS, it's definitely one of the more worthwhile of the new "compiles to JS" languages.
My 2 cents.
We suffer more in our imagination than in reality. - Seneca
... another programming language. [smh]
CUR ALLOC 20195.....5804M
Once again a futile tempt to automatically eliminate it.
I actually happen to like and appreciate Typescript. It was easy to learn-by-doing by going through the Angular [2-6] tutorials.
As a long-time Java programmer, I don't have to give up the type checking at the IDE level that really reduces the common coding mistakes you get with plain Javascript. You just get to tryable-then-working code faster. But you don't give up any of the flexibility that Javascript gives you. And the async/await functionality makes client-side programming just so much easier.
Does anyone else feel this way? Or is it just fashionable to hate it because Microsoft had something to do with it?
Greed creates fragmentation.
Works great on Linux. TypeScript is almost necessary with angular 2. Why wouldn't someone want the best mix of static and dynamic types?
I have a solid 18 yeats of experience with JavaScript. There is absolutely no point to TypeScript (or similar languages like CoffeeScript). They provide some cool syntax candy and "extend" the language in a sense, but in the end it just spits out pure JavaScript and adds a level of abstraction when it comes to debugging. If you're a good JS developer, you can write excellent, readable, well-organized, and maintainable code. And with ES6 you can write truly OO code with real classes and inheritance if that's your thing. Core JS is not perfect but is very powerful if you know how to use it. I've written entire single-page apps using core JS and jQuery, complete with controllers and data models. There is nothing that TypeScript really provides or improves upon other than a syntax closer to Java, which JavaScript is not! Oh and this nonsense about code completion and refactoring is just the icing on tbe cake. Most modern IDEs can already do this and have been doing it for years FFS. Gosh even Atom with pluggins can do that.
Typescript is entirely open sourced, code and development. Check some facts before posting pure bullshit
Still no integers? Come on guys, why put all that work into it and leave that bleeding wound still bleeding? Pass.
When all you have is a hammer, every problem starts to look like a thumb.
Remember all those "Best viewed in Internet Explorer" sites?
This is just the second attempt to take over JS.
JScript was the first attempt, and nearly ruined the WWW.
I wonder if MS will ever learn that they do not dominate computers anymore.
Use whatever language you like.
But frankly, a better solution, would be, if we, instead of running a full-featured platform, running a crippled shitty platform on top of that, and then applications in that, would just run the applications *directly* on the full-featured platform.
Just use a damn "application firewall", or a proper OS, and be done with it!
Because no, virtual machines and similar sandboxed do not provide any more security!
And hell, if you can implement a browser using a webview, a networking module, and a URL input bar, then you can also do it with a full virtual machine, a networking module and a URL input bar. Or, the UNIX way: Build sandboxing into the execution of executables by the OS, have a /net/ directory with the domains (like /net/$domain:$port/$path), and in there, executables to run like normal. (So inside whatever sandbox/firewall/magic you want.)
The whole web application world is nothing but pure "inner-platform effect" cancer by utterly incompetent people who grew up clicking colorful clickables and never daring to enter C:\Windows\System because Windows (of course) said so.
You are free to kill off one or ten thousand other programming languages to balance it out, you know?
Or see it as "the next version of that certain language".
Of course that is exactly what Microsoft wants. Mozilla ruined their well-running "embrace, extend, extinguish" scheme with "JScript" back then. But of course they will try again. You do not expect a serial murderer to suddenly stop having "that urge".
Maybe Microsoft can get rid of JavScript . . .
"I believe in Karma. That means I can do bad things to people all day long and I assume they deserve it." : Dogbert
IMO, TypeScript is the only good thing Microsoft has ever produced (well their old corded mouse was decent). It emits readable JS, given that I don't see the risk. If they do something bad with it then I can just work off the compiled JS files.