Skip to main content

I Will Not Learn Dart

I don't want to learn Dart, at least for now. I hope to explain in this post how I think, so begin.

Dart want to be next big language of the Web, but this really doesn't matter. JavaScript will be with us for years from now, and other Browser vendors do not implement it, at least if Google do not pay them to.

It will have at best all Chrome users, and this probably be about 20-30% even in a couple of years, so only a couple of developers will really use it for real. Just now how GWT now is used. 
GWT and Dart will be used only by people that use Java, but they not WebDevelopers most of the time. Most of WebDevelopers write JavaScript, not Java or even PHP. 

What are benefits of Dart rally?
  • classes
And that's pretty all of it. 

Really, there is nothing really impressive in this new language. This is mix of some other OOP languages. Nothing new. I can tell that this is boring. 

Even getters na setters are available in JavaScript, just nobody use them because they are slower. 
Types - JSEngines guesses types, and if only programmer stick to one type in one variable it will work really fast on new VM, this isn't really a issue here. In optimization faze it can be easily done without types in language. 

As I see It now, Dart will probably end like Go for servers. Anyone really use it for real. Somebody on the whole world for sure, but it don't catch up. 

Consider running the same code on server and client. Node has done that, nothing new. It would be nice but not really that important. 

"at least for now" - time to explain this.

Oracle is not happy seeing Java on Android, especially because they get Java and make it only for them. Java was supposed to work pretty the same on all platforms, Google ignored it and implement only a subset of it. In my opinion Oracle should win it. 

What Google want is really new language that is very similar to Java, to be familiar to Java developers. Language bring all sweet sugar to developers from Java. This is all they want from at least a couple of years, and now are waiting to see in Java 8. 

Read the post from conference:
09.13LarsBak: the competition is not JavaScript … We’re up against the fragmented mobile platforms
Do You all get it now? 

Dart is not new JavaScript, and it rather never will be. Instead it will be new language for Android, just like ObjectiveC for iPhone. Chrome will support Dart, but probably only chrome. There will be tools compiling Dart to JavaScript just like now they are for Java (GWT) but this is nothing new. It wouldn't be really standard. Nobody that has at least some knowledge about the web would not consider Dart as the main language, at least I think and hope not. 

After about year or two I can think about learning Dart, for now I prefer to Learn better JavaScript. It will be for years from now with us. Dart would be interesting when it will be available in Android (maybe I finally buy one ;). Dart would be in my opinion better than Java, easier, more powerful. 

I can be wrong, many times I was, so If You like Dart use it, make it better, but please do not tell me that it will be new language of the web, JavaScript has done this and it will be for at least a couple of years from now. 


Popular posts from this blog

Course Review: The Bitfountain iOS 8 with Swift Immersive

This is second big iOS learning project. For first one read iOS Programming book review. As I only have two of them done I have to compare them somehow.

I am mindful that it took me a really long time to finish it (since last autumn). For a couple of months this year I didn't even have the internet to learn it, so it could not be helped. But last half of the June I've spent watching the videos every day and managed to finish it before any new internet problems.

So how was it?
In my opinion, it's great if you're starting out. There are a lot of basics, and seeing how to do things in XCode just makes your learning much easier than looking at the photos in the book. On the other hand, learning is more shallow and it is much easier to just follow the videos and learn only the basics without bigger picture about iOS SDK. I somehow missed more challenging exercises (even though I don't like to do them ;)

Course it pretty long but many videos are quite short (1-2…

How to Learn when Life is Short

I haven't really think this through but I have read really interesting articles recently and I just wanted to write for myself later.

Life is Short by Paul Graham

It's just that, learn from people older that you what is most important, and that life actually is short...

Instead of Goals or Resolutions, Try Creating Rules by Leo Babuta

In the time of New Year Resolutions, it's good to read something that is proposing different way of achieving things. Still I see much more value in habits than setting goals. But...

The Easy Way To Learn Hard Stuff by Per Harald Borgen
It's something that I read from time to time and I know it works sometimes for me. The things I learn then are really learned and something Jakub Wasilewski  has told me many times to do. Still it's uncomfortable and for some reason, I have failed to use this method more than once or twice. Writing it here so maybe I can think about it more and figure out how to do that more often.

Towards an understandin…

Hero's Journey in Presentations

Artur Skowroński recommended me: Want a Better Pitch? Watch This. by Andy Raskin and I think it is so great and applicable to all kinds of talks that I want to help it get more popular.
So the plan of presentation is going to follow these steps: Enemy - ProblemWhy now? - call to actionShow how the world will look like without the problemProblemsEvidence that you fixed the problem The image at the top is because it reminds me of Hero's Jurney. It has fewer steps but there is a lot of similarities. Especially #3 made me realize that grand vision of the future is something that I should have used in my talks.  The result at the start of the presentation makes a lot of sense actually. Everyone already knows that I speak about something because I probably fixed it and if you tell about it at the end then it might be hard for some people to see the bigger picture in the solution you're going to present.