Can Google's Dart language replace JavaScript?

Recently, Google's new programming language, Dart, has emerged as a "structured Web programming" language. It is rumored that it is similar to JavaScript, or it can be said that it is ready to compete with JavaScript. The foreign RebuildingTheWeb blog analyzed this and cited the lessons learned by XHTML2. It believes that Google should adopt a more open attitude to developers to recognize Dart.

The full text is as follows:

Google is developing a programming language called "Dart", whose ultimate goal is to replace JavaScript with several fundamental issues that cannot be fixed. In addition, Dart is designed to completely remove JavaScript, so it is not backward compatible with JavaScript. Can such a radical technological change be successful on the Web?

Will the fundamental change of Dart split the Web?

Over the years, browser providers have told us that Web technologies must make steady progress. Otherwise, the Web will be split. This debate has ended the development of xhtml2. XHTML2 is a markup language. It was originally used to replace HTML with the same underlying problem that cannot be fixed. Like XHTML2, Dart also deviates from JavaScript. Will Dart split the Web like XHTML2? Or do we already accept that backward compatibility must be embedded in browsers, but not in programming/Markup languages?

Is JavaScript problematic?

Over the past few years, JavaScript has gained a lot of praise for its huge performance improvements and the newly added libraries and APIs. JavaScript is already so good. Why should we replace it?

The most serious problem is that,JavaScript applications are inherently insecure and vulnerable to malicious attacks and data theft. JavaScript lacks a wide range of feature libraries, such as advanced plotting, encoding, encryption, and network communication functions in Java and. NET.

JavaScript applications are usually built on loosely coupled technologies and are often not written by traditional programmers. The inevitable consequence is the generation of "spaghetti style" code. These codes are often complex and confusing, and are filled with browser version/bug problems or technical defects.

Most of the time (and most of the cost) for program development is spent on debugging. Creating an integrated development environment (IDE) similar to Visual Studio or Xcode for JavaScript applications is impossible. This makes it much more difficult to debug such JavaScript applications than the same desktop program. In addition, JavaScript is an interpreted loose language, which also increases the debugging complexity. This also means that developing a mature JavaScript program requires more developers, more time and money.

Can technology determine the future of Dart? Or fight?

If Google's Dart technology is better than JavaScript, can this lonely fact make it successful? Or will Google's expectations for this technology become a bubble? Will Google's Dart face the same fate of W3C XHTML2?

Google Dart actually has a bad start.The main problem is that Dart is developed by a single vendor.. Google is not going to be entangled in this issue, or it has long been working with other vendors to develop this technology. Even if Google acknowledges that support from other browser vendors is very important, it intends to use sweet words to encourage them to support this new programming language. But did they accept the application developers? After all, developers need to learn a new language and related new tools.

End

Google Dart is designed to replace JavaScript, and XHTML2 was originally designed to replace HTML. JavaScript does have technical issues that cannot be fixed, so it needs to be replaced by a well-developed language. However, Google's unilateral and non-negotiation methods indicate that Dart must be under some suspicion. It is inevitable to persuade application developers to embrace the challenges of Dart.

Original article: http://www.iteye.com/news/22801