Let's talk about DART first. At the GOTO Developer Conference to be held in October, Google engineers said they would announce details of a new programming language called DART. Lars Bak, Google's engineer, will give a keynote speech at the GOTO Developer Conference. It is responsible for Chrome V8 Javascript Engine and has previous experience in Virtual Machine Development. Bak holds a large number of patents, but most of them come from earlier SUN's work period.
Another Google Engineer, Bracha, disclosed some content in his blog. He first expressed dissatisfaction with Javascript and then proposed that the Internet should continue to evolve, in addition, the performance of the multi-core processor needs to be utilized. He also said:
Javascript is still a language with severe restrictions on platform deployment.
Then the gods appeared and dug up the communication between Google employees in last November. Since then, a group of Google teams have been studying the future of Javascript. The new Google language mentioned in this letter is called Dash. It seems that it has now changed its name to Dart. HoweverSome of the content in this letter can't help but make people feel cold in the back:
We will seriously encourage Google developers to focus only on Chrome, so as to bring us the best user experience.
Developers who only focus on Chrome can xxxxx ...... Developers who focus on all browsers will have to xxxxx ......
Someone commented on REDDIT that I don't understand why people have to follow Google to help them replace existing technologies with their own technologies. They always promise that "we must try new standards", but their own technology has not become the same as so far:
Google does not like MPEG, so it creates VP8.But at the beginning, they didn't make any effort to build it into a true open standard.
Google does not like HTTP, so SPDY is created.However, there is only support for Chrome and Google Web applications, and there is no indication that it will become a standard organization. Can you imagine that Microsoft's IE has built a set of HTTP standards and then only communicates with Microsoft's own IIS service?
Google does not like the NPAPI plug-in models of all non-ie browsers, so it creates completely incompatible plug-in APIs and Native clients of Native code.
Google does not like JPG and PNG, so it adopts WebP graphics format.
Now Google does not like Javascript again, so it starts to develop Dart.
It is estimated that Google will not like CSS or even HTML.
True,Google's proprietary technology is open-source, but they do not want to promote it as an open and open standard, an open standard means that everyone in the industry has the opportunity to explore design, development, and guidance for technological advancement to be available to everyone. However, all the technical standards Google has developed are completely controlled by Google. Google decides everything about this technology (including Android, are you right ?).
Yes, these technologies and standards are open-source, but does this open-source mean anything? VP8, SPDY, NPAPI, Native Client, WebP, and Dart are all under the control of Google. So far, almost all of them have been deployed only in Google's Chrome browser. Yes, you can also deploy it in your browser, but you cannot control its development at all. You can only play with Google in its black box. Yes, you can also use open-source code to modify a set of technologies suitable for you without being subject to Google, but such laborious results are meaningless, do you want a website to deploy SPDY and its various variant versions at the same time to get a faster response speed than HTTP?
If Google is really a responsible and sincere company that promotes open-source and better technical standards, what they should do is to report their ideas and technologies to open standards similar to W3C, let the whole industry work together to develop, create, and improve this better technology and make it a true open standard.
Original article: http://www.guao.hk/posts/google-to-unveil-dart-programming-language.html