15 ms·
Dart 1.0 Is Out
- rdtsc 13y agoList of companies using it in production (from the blog post): * Blossom * Montage * Soundtrap * Mandrill * Google's internal CRM app * Google Elections Companies that started to add support for it: Adobe, drone.io, and JetBrains
- mikehotel 13y agoGoing forward, the Dart team will focus on improving Dartium, increasing Dart performance, and ensuring the platform remains rock solid. In particular, changes to core technologies will be backward-compatible for the foreseeable future. Today’s release marks the first time Dart is officially production-ready, and we’re seeing teams like Blossom, Montage, Soundtrap, Mandrill, Google's internal CRM app and Google Elections, already successfully using Dart in production. In addition, companies like Adobe, drone.io, and JetBrains have started to add Dart support to their products. Congrats to the team on releasing 1. Now to find a project to try it out in...
- notok22 13y agoI almost finished the Language Tour when I went to the faq and was dissapointed to see that the dart2js compiler supports only ie9+ (https://www.dartlang.org/support/faq.html#what-browsers-supported https://www.dartlang.org/support/faq.html#what-browsers-supp...). Too bad, honestly.
- efesak 13y agojQuery 2 is ie9+ too fyi
- quarterto 13y agoAnd jQuery 1.9+ is API-compatible with 2.0 and works just fine on oldIE.
- deleted 13y ago[deleted]
- nilliams 13y agoOpinion: nobody should be shipping any JS to oldIE, period. Their JS engines are woeful. Even if you can get something app-like (the kind of thing you would use dart for) to work, your app won't scale w.r.t. perf so you're painting yourself into a corner.
- quarterto 13y agoThat's your opinion and you're entitled to it but people do still have to ship things for IE6-8.
- SiVal 13y agoSome do, of course, but some of the rest of us are more interested in future advantages. If you need to target legacy browsers, legacy technologies are widely available. If you'd like the future to be as good as possible, you might want to build new tools without the same old constraints.
- nilliams 13y agoUnderstood. I'd just question if it needed JS - if JS actually added to the UX and outweighed the considerable dev cost.
- threeseed 13y agoHow on earth do you propose to implement client side functionality without JS ? The fact is that MANY people need to support IE6-8.
- nilliams 13y agoSample size of 1 etc, this is just my experience. I personally built a single page application about 2 years ago that worked in IE8, thanks to jQuery and the ecosystem of the time. jQuery, jQuery UI, various plugins incl. jsTree & DataTables. It flew in Chrome, Firefox and Opera, even then. In IE8 it was slow as hell. Event listeners were slow, ajax and parsing JSON was slow. Everything was crazy slow. The app felt lumpy and awful. And when I hit bugs, the developer tools just were not there. I would never do this again. I'd wager that for IE < 8, for any non-trivial app, round-tripping to the server will give you a better UX than using JavaScript. Deliver something usable for oldIE. There are many people that share this view. I suggest watching this talk on how the BBC deals with legacy browsers (9m 20s): http://www.youtube.com/watch?v=YfvMQ316hMU&t=00h09m20s http://www.youtube.com/watch?v=YfvMQ316hMU&t=00h09m20s
- kodablah 13y agoI think Dart has the potential to become a target for other languages [1]. The already-high-level code has a performant VM and it takes advantage of optional typing (unlike any other VMs I am aware of). In order to do so though, they should at least make a spawnString (like isolate's spawnUri) or even better, have the ability to JIT dart code by string but not execute it right away. 1 - https://www.dartlang.org/articles/why-not-bytecode/ https://www.dartlang.org/articles/why-not-bytecode/
- pacala 13y agoI hope people give Dart a chance before unleashing the fragmentation zoo upon it. It's quite a nice language.
- georgemcbay 13y agoAdobe's AVM2 (ActionScript 3 VM) took advantage of optional typing. Once upon a time this was going to be the basis of ECMAScript4 via tamarin, but that never panned out for lots of reasons, most of them political.
- camus2 13y agoFunny how things would be different today. ES4 failed mainly because some people thought ES3 was good enough. Adobe,harshly critized for Flash was the one pushing for a better javascript. I will never understand why Microsoft basically killed ES4. They had their own implementation on .net ( JScript.net ) so it's not like it was going to be a huge effort. The only reason would be Microsoft pushing Silverlight at that time which was a huge flop. We basically lost a decade because of it, as i predict javascript will eventually look like ES4,that's inevitable.
- pekk 13y agoJavascript lost a decade because of that. People without an investment in Javascript have lost over a decade because of Javascript's monopoly on clients being maintained. If we had not been forcibly locked into Javascript all this time, then competition would have produced a better alternative or whipped the process designing Javascript into shape. Now we are stuck with this ridiculously tall, messy stack which uses an application scripting language as a compile target, still lacks basic features like a standard package system, and pushes trivial language features like iteration into third-party libraries like jQuery. So now we are constantly pushing megs of JS, using insanely complicated build systems to get anything done, and for all this trouble our code runs at a speed roughly equivalent to C in 1998. (Now that Flash and Silverlight are dead I think it is safe for me to complain about Javascript without being an enemy of the open internet or whatever.) I don't really care about Dart, but it's way past due that there was something serious to challenge Javascript. All the triumphalism about how Javascript is already a perfect language to use for eternity is explicitly counterproductive. Making the whole internet depend on the fortunes of one language just sucks.
- andyl 13y agoJust waiting for "Works best on Chrome" Silverlight and ActiveX have already shown the usefulness of proprietary enhancements. No thanks.
- snird 13y agoDart is as open as possible. this is nothing like silverlight or activex.
- limsup 13y agoIt compiles to JavaScript. The VM and dart2js are MIT licensed. It's not the same situation.
- spankalee 13y agoAnd Dart is not a plugin, it gives you the whole DOM (though a _much_ improved API), unlike Silverlight, ActiveX, Flash, Java or any other plugin.
- threeseed 13y agoAnd who is responsible for keeping the DartVM/Dart2JS behaviour in sync ? Google being the ONLY committers don't exactly have a motivation to.
- dragonwriter 13y agoDart2JS will be the key thing that drives Dart adoption. So, yeah, Google has a motivation to keep it up to date.
- davidedicillo 13y agoWould someone who knows HTML/CSS/RoR better of learning Dart or JS next?
- dragonwriter 13y agoWithout any additional special assumptions about the someone and their particular circumstances, learning JS is probably a lower risk investment, learning Dart is probably higher risk and higher potential payoff; thinking only in terms of future income potential.
- camus2 13y agoEven if you use language X that compiles to javascript ,you still need to learn javascript, Or it's a bit like learning rails without understanding ruby.
- sek 13y agoNo, Dart is not CoffeScript. It really compiles, so you don't have to worry about it. The languages are so similar that stuff that is fast in Dartium will work pretty fine in JS.
- RobAtticus 13y agoI don't need to learn assembly to use C. I don't need to learn the JVM bytecode to use Java. Sure for special cases knowing those things can help get the very best out of your code, but for the other 99% of the time, it is not necessary. (Edit: Not that I recommend Dart over JS necessarily, but I don't agree with your argument.)
- tzury 13y agoSo if i get it right, the way "Google" sees the future, there is Go at the server side and Dart at client side (which is in fact JS). Am I wrong? I would expect Google, or at least, a team at Google, to take over NodeJS which is based on their V8 and expand it to universal server client language and libs. JS can be complied into go binaries after all, so why not letting people write apps using the same language. Let alone I see no effort on their side bringing any of those language into the native world of Android, instead we got this cluttering Java thing as almost the only options for most projects.
- spankalee 13y agoThe point of view within Google that spawned Dart is that JavaScript as a language has major and unfixable flaws that severely raise the cost of developing large apps. It's nice that node.js uses V8, but being based on a Google project does nothing to address the language issues. Note that that point of view is not universally shared at Google, and many people are fine with JavaScript, and probably would use node.js.
- tomp 13y agoI believe Google is using Go for completely different projects (i.e. fast backend services that don't really interact with the browser).
- staunch 13y agoAssuming that Google has much of an overall strategy here is probably a mistake.
- munificent 13y ago> I see no effort on their side bringing any of those language into the native world of Android The Dart VM supports ARM, and I've seen prototypes that get it running on Android. The team hasn't had much time to put into it yet, but I wouldn't infer that that says much about what we'll do in the future. (Not that I'm making any promises, either.)
- dragonwriter 13y ago> So if i get it right, the way "Google" sees the future, there is Go at the server side and Dart at client side (which is in fact JS). Am I wrong? Yes, you are, in fact, wrong. Google doesn't have so narrow a vision. Dart is server and client side (the native VM is, aside from a for-testing-only build, server-side only now.) But the client side isn't just Dart (or JS, in which Google has also invested heavily), its also C/C++, and other languages, hence PNaCl, which also just went into general release. And, sure, Go is a server-side language that Google is putting energy into, but so is Dart. And I doubt their vision ends there, those are just a couple of the more visible active fronts. > I would expect Google, or at least, a team at Google, to take over NodeJS which is based on their V8 and expand it to universal server client language and libs. The existing NodeJS team is doing enough for server-side JS-on-V8, and its open source -- Google could throw more resources, but its probably not the best bang-for-their buck in terms of developing new technologies that might improve the options for the things Google is concerned about. Doing what other people aren't doing is a bigger win. > Let alone I see no effort on their side bringing any of those language into the native world of Android I've seen quite a bit about Dart on Android (though I think there are issues with building the current distribution.) Less on Go.
- tzaman 13y agoWhy doesn't Google include the native Dart VM in Chrome? I think it would boost it's usage significantly. Maybe I'm missing a bigger picture.
- dragonwriter 13y ago> Why doesn't Google include the native Dart VM in Chrome? Probably because Dartium (Chome w/Dart) doesn't yet have the kind of performance advantage that makes it compelling enough to split the web that way -- making developers use dart2js for client code means that you don't need separate client code for Chrome (Dart) and everyone else (JS) -- and needing to commit to extended support of two different scripting runtimes in Chrome for the future.
- afsina 13y agoThey need make some changes in Chrome for doing this right. They aim to make DOM nodes garbage collectible with project oilpan [1] AFAIK. Both Dart and V8 VM will benefit from this. So this will take some time. But Dart is already very useful with Dartium for development and Dart2Js for deployment. [1] https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/V1vJmirHUGE/discussion https://groups.google.com/a/chromium.org/forum/#!topic/blink...
- kyrra 13y agoThis is exactly the issue. They are working on an experimental solution to let garbage collection happen for DOM nodes that are created from Dart or V8. This basically requires a rewrite of the memory management of DOM nodes. This is still very much a work in progress and not ready for prime time. The solution the team uses for Dartium is not the same as what they want to do for the shipping version of Chrome, so it'll be a bit before that's ready.
- amix 13y agoThis is really awesome! Congrats to the team! We have a ton of JavaScript/CoffeeScript code and I really wish we could use something like Dart. JavaScript is great for smaller projects, but once you get a ton of code it really becomes a unmanageable mess. I think tho' it would be amazing if Dart could run on the server side as well. This way you could just have one language on both the client and the server.
- spankalee 13y agoDart does run on the server. The VM runs standalone for scripts and long-running apps, and the dart:io library provides very node.js like file, network and HTTP APIs, with the addition of Isolates for actor-like concurrency.
- camus2 13y agoIf you are looking for a structured language (for front end dev), Typescript is a better alternative imho. Javascript devs can still read it and it's compatible with any JS library out there. Dart not so much since the semantics are different.You can still interact with JS libs but it's not as straight foward as TS. I tested a number of options (GWT,Haxe,CS,Dart,Opal,Jsx,...),while i'm not a Microsoft fan(by a long shot),Typescript is the solution that allows the best integration with legacy code and pure JS libraries,while making easy to port old java/C#/as3 code to JS.
- Flow 13y agoThat the semantics are different from Javascript is one of the big selling points of Dart. :)
- michaelwww 13y agoI've done a project in Dart and another in TypeScript and like them both a lot more than doing straight JavaScript. I appreciate the optional type checking in both and the IDE support that each enables. TypeScript is appropriate if your project is more quickly completed with existing libraries like jQuery UI and needs to run on older browsers. Dart is appropriate if you don't need to use older established JS libs and IE9 and above are your target requirements. I like having them both in the toolbox, but I prefer Dart slightly more than TypeScript for various reasons.
- rayiner 13y agoHow's the Emacs mode?
- rdtsc 13y agoThe one I am using (and I don't even remember which one it is or if there are multiple ones) does basic highlighting. There is no re-factoring support that I could find yet.
- ntkachov 13y agoThis is speculation: but JetBrains work on dart IDE, android releasing ART, I'm tempted to say we're 2 years out from seeing DART running on android. It makes sense from a business sense, have the option of running dart apps on android would free the platform from its java dependance.
- mark_l_watson 13y agoI hope that you are correct! That would be great. I have experimented with Dart on both client and server and it is a nice language. Fun to develop with.
- ahoge 13y agoThe VM already works on Android (x86 and ARM - not sure about MIPS).
- floitsch 13y agoThe VM works on MIPS too.
- clhodapp 13y agoWhat does ART have to do with Dart?
- Twirrim 13y ago3 letters
- jalan 13y agoI am a newbie in field of Web Development, and recently I felt in love with JavaScript, especially because of the sheer capability to write Client side and Server side code in same language. Thanks to Meteor.js, it made my bond with JavaScript even more stronger. But now with the buzz of Google Dart going around, I am afraid that, am I betting on the wrong horse? Is it the right to jump on Google Dart bandwagon? To be honest, it do looks promising. Please guide me, what should I do, since I am a newbie, I want to take advantage of the fact that, since I don't know anything, I better learn something that have much promising future, and have an edge over technology.
- dangoor 13y agoHonestly, JavaScript has orders of magnitude more usage and a lot more momentum than Dart does. I don't think you'll be harming your career prospects in becoming proficient in JS. I also think there are better choices than Dart if you want to learn something that will expand your mind. Dart strikes me as a very practical language.
- mark_l_watson 13y agoI have spent time with both Dart and with JavaScript + Meteor. Both are good stacks. If you are already up to speed on Meteor, why not just use that for a year, build applications, and maybe look at alternatives later. It is probably best to start writing web apps, and not on learning many tools.
- jalan 13y agoThanks for the advise, I am thinking of concentrating on JavaScript + Meteor for now.
- threeseed 13y agoLearn Javascript. Dart is a dead end technology. ALL the committers are from Google and it is not an open standard which basically eliminates any chance that Mozilla/Apple will ever consider adopting it. And frankly with Apple dominating the mobile web without them any solution will never eventuate to anything.
- AstralRabbit 13y agoVery happy to see efforts like this to bring new languages as alternatives to JavaScript. I'm sorry but no amount of spin can convince me of ever liking JavaScript. Why can't we just admit that we're stuck with it for now because there are no viable alternatives? 5 years ago, people were ragging on it just as they do on PHP now. And now all of the sudden it's the poster child for good programming? Please. Good news indeed. I look forward to the day where we no longer have to use JavaScript. If this offends someone, sorry.. but just my opinion. I can't stand JS.
- woven 13y agoPsyched! See our HN post about our Dart app (Dart rocks) and our team's disappointment with not being included in the 1.0 announcement. https://news.ycombinator.com/item?id=6735044 https://news.ycombinator.com/item?id=6735044
- munificent 13y agoI don't know anything about what went into deciding which companies were mentioned in the announcement, but I know for certain I and others on the team have a ton of respect and gratitude for all of the help you and Kai have given us. Thanks!
- woven 13y agoThank you! And congrats!
- vfclists 13y agoShameless plug!!
- Twirrim 13y agoWelcome to HN, home of the shameless plug and the nearly mindless rants.
- woven 13y agoSorry folks, I thought and still maintain that our situation was relevant to other startups and hackers. I thought we'd get some critical feedback, and we did. And yes, we wanted to tell our own story with respect to Dart since we had been expecting to do something like that for some time as part of Google's announcement. The post is removed and we're moving on.
- protomyth 13y agoIs there a downloadable reference manual for the language? I see book excerpts, but not a complete language reference.
- floitsch 13y agohttps://www.dartlang.org/docs/spec/ https://www.dartlang.org/docs/spec/
- afsina 13y agoThis is Language spec. not useful for developers. I would suggest downloading 5 links as HTML from here: https://www.dartlang.org/docs/dart-up-and-running/ https://www.dartlang.org/docs/dart-up-and-running/
- nfoz 13y agoSad to throw away the brilliance of prototypes to go back to single-inheritance classes. uck
- taylodl 13y agoMy thoughts exactly. Dart is representative of 90's language design and as such is a step backward. That's not to say JS doesn't have its issues, but Dart isn't the solution.
- mraleph 13y agoJS prototypes provide a single parent lookup delegation, which is not that different from single inheritance and is mostly used to emulate single inheritance class systems in the wild. Furthermore Dart supports mixins, so it's not exactly single inheritance classes.
- voyou 13y agoCould you explain the brilliance of prototypes? Prototypes in JavaScript are pretty awful, but I've never been sure if that's just the JavaScript implementation (for instance, the lack of a good way to clone an object makes using prototypes in JS more painful than it needs to be), or the concept of prototypes more generally.
- ionforce 13y agoHow are prototypes brilliant? I'm not familiar with them outside of JavaScript. Maybe you could provide some examples?
- Bahamut 13y agoDart seems interesting, but its sponsorship by Google creates a major problem - what incentive does Microsoft, Mozilla, or Apple have to implement Dart support in their browsers? What about JavaScript devs who choose not to support Dart (especially since many still have to support even as far back as IE8 due to enterprise/companies/organizations/schools that opt for long-term support solutions for software)? I don't think good answers are available to these questions, which makes me hesitant to jump in as quickly.
- klodolph 13y agoDart also compiles to JavaScript, and was designed to do so from the very beginning.
- Bahamut 13y agoIt adds complexity to the dev process, and I'm not sure of the benefits of said complexity. The devs still at the core need to understand JavaScript it seems like.
- chrisbuc 13y ago> The devs still at the core need to understand JavaScript it seems like. No, that's not the case. You need to understand the browser DOM, and the various APIs available to you, but these are presented by Dart libraries. If you have knowledge of Java or C#, then that knowledge will be useful, and if you have knowledge of JavaScript's functional elements, then that is also useful, but none of that is mandatory to be effective with Dart.
- Bahamut 13y agoBut if you're using third party JS libraries and want to integrate with a Dart app? Seems necessary to still have to understand JS to integrate properly since you still have to know how those libraries' API works.
- sigzero 13y ago
- moca 13y agoSome people wanted to build optional-typing language for real world for decades, and finally made it. That is a great achievement. From product point of view, Google would be much better to port Android Dalvik to Chrome. You can run GWT Java code in browser years ago. Running the same code using JVM would be much faster with much less code change. 5-10 man-year would be enough to do the porting, and it will share work between Android and Chrome for years to come. Of course, it would be much boring research work though. From performance point of view, asm.js gets much better performance with way less work. No matter how good Dart performs, it would never make sense to port high performance C/C++ game code to Dart, so you end up having to use both Dart + pNaCl, which is an awful solution. Technically, TypeScript is more interesting if Microsoft can keep it simple and fast, but I doubt Microsoft would make anything simple.