Web Development: Go in the New type script compiler

The typescript was once produced out of the requirement to compensate the largest weaknesses of JavaScript. Over the years this web development has been an almost indispensable tool, which always has a slight edge for JavaScript in its development level.

Microsoft recently announced that the base of the typescript has been completely modified – ie compiler, the type script has been translated into JavaScript, and other components that are responsible for interaction with equipment and growth environment. Microsoft made a stunning option for many people. Most of them hoped that if anyone takes this step, Jung is used as a programming language, as JavaScript is already popular rust-based equipment in the environment, such as bundle RPAC.

But the Typescript team along with Anders Hijalsberg decided as a rhyme instead of a rhyme. The goal of domestic implementation in Go, which is compiled in contrast to the just-in-time conversion of the type script in the bitecods-is a noticeable lack of improving the execution time of the type script tool and the memory consumption. According to the current benchmark, the new type of script receives ten -time time for the construction of various projects.

Apple Hardware leak on X: First Parts of a “Vision Air” appeared?

This article is dedicated to the question as to why this improvement is so important, where the current weaknesses of the typescript are and how the development of the new compiler, which is managed under the code name Corsa and under the version type 7.

What is Typscript?

In 2012, Microsoft published the first edition of the Typescript after two years of development. Programming language on Github has been developed with public viewing since 2014 and is subject to Apache 2.0 license as an open source project. Meanwhile, the Typescript version has reached 5.8.

In short, the typescript is a programming language that complements JavaScript to compile type safety – with the goals of developing large applications and being able to create a basis for better growth tools.

There are many reasons that spoke for the use of typescript instead of JavaScript in both front and backnd projects on the web:

• Static typing: JavaScript has only a weak type of system that is in favor of runtime errors. With its large -scale alternative stable typing, the typscript offers great flexibility on one side and on the other hand helps developers to identify possible mistakes in an early stage.
• Improvement in code quality: Especially on the interface of the module in an application, but also for libraries, the typescript allows a strict definition of interfaces, which significantly improves the maintenance and readability of the code. It benefits large projects and reusable libraries.
• Tool support: JavaScript Ecosystem rely on the typescrippt to provide better equipment to developers. The development environment such as visual studio codes can help develop a node.JS application, if the types of types of node.JS are established, especially in relation to the completion of auto and performance of functional signature.
• Polyphils: Typescript Ecmascript supports modern features from the standard and integrates features across the board long before and most environment such as browser. Typscript can create various ECMASRIPT versions as an output and thus also supports the old environment. This option goes back to the ECMASCRIPT 3 version (this version of the JavaScript standard was published in 1999).
• Structured Development: In addition to standard JavaScript and type security, typskript introduces other constructions such as interfaces, enams and generic that allow data structures and interfaces to be better modeling. Some object -arantated design patterns cannot be applied to the native JavaScript or only with extra effort. The presence of the interface makes the work quite easy here.
• Strict atmosphere: Typescript enables configuration options like strictNullChecksTo avoid frequent errors from the beginning.
• Framework and Library Integration: Many framework and libraries in JavaScript ecosystem are either applied directly to typscrippt or bring at least types of definitions with you so that you can basically integrate in a typist environment and play all benefits.

What is notable: Typescript (still) has been fully programmed in the typescript. The origin of the programming language will also be continued in the Typescript in version 6. At the same time, the team works on version 7, which will then be a Go-variant and will change the typescript implementation as soon as the two projects have achieved a facility equality. The current schedule of the development team provides for the full version of the command line compiler in mid -2025, capable of completing the type of source code and translation.

Currently, the Typescript-Go-Completeer is working for almost completely pure typescript code. What is still missing is the support of JavaScript, JSDOC and JSX. At the end of 2025, a version of the facility that manufactures projects will be expected. In addition, one of the most important development facilities should be available with language service.

But why is such a rigorous step necessary as again in another programming language? Typescript follows its advantages, especially in large applications. Along with the growing code base, however, the typeskcript’s resource requirement also increases in the type of testing and construction. On the one hand, it leads to opening a project in a long -term development environment, as the code here is initially processed by the language service. And the construction of a large application can also be a lot of time. There is another one in the pure word, even a big problem due to the high need of Rama. This can lead to memory problems and, in the worst condition, crashed through out-of-memory errors.