[ Dart hits a bull's-eye for Web developers, InfoWorld columnist Neil McAllister says. | Peter Wayner reveals what's hot in scripting languages. | Subscribe to InfoWorld's Developer World newsletter for the key news and insights on software development. ]
InfoWorld: Is that what you mean by Dart being a language for structured Web programming?
Bak: It is. You can write small applications in Dart, but as the applications scale, you can start adding types to your programs, and that really specifies a programmer's intent. So if you make a module, you can see exactly how you're supposed to use the module based on the types you have specified in the interface and you can also check that in Dart. If you really have big teams working on the same source space, this actually makes a lot of sense.
InfoWorld: What is the benefit of Dart running on both clients and servers?
Bak: It's like any other language that runs on both sides. You can decide late in the process whether you want the code to be running on the server or in the client. You have to bear in mind that if you are writing Web applications, clients are very different. You have a Web browser on a desktop, which is very powerful, and you can put a lot of logic on the client side. But if you run a mobile phone, which also has a Web browser, you often want to off-load some of that code on the server side. If the application, both on the server side and the client side, is written in the same language, you have the option of deciding where the code should execute.
InfoWorld: How hard is it going to be for developers to learn the Dart language?