Google Dart Article Correction
I'm the author of the article "Introducing Dart, the New Web Language from Google" in the March 2013 issue. I wrote the article in late December and submitted the article in early January of this year. During the time I was writing it, I was using Dart M2 (version 0.2.9.9). I made sure to have my colleagues check over my code and worked to make sure that everything was perfect!
"Best laid plans of mice and men often go astray." These words are all too true for me, since only nine days before the release of the March 2013 issue, Google released Dart M3, and with it came a new, non-backward-compatible standard library API. Of course, I didn't see that it had released the new version until February 28, 2013, which was hours before the March issue was going to be sent to everyone.
So what was I going to do? After I wiped the stunned look of realization off of my face, I quickly worked to update all of the example code that was now broken to use the newest API. I posted an entry on my blog at http://jamesslocum.com/post/44259278296 where I describe what happened, and I explain the differences between M2 and M3 Dart. I also provide re-worked examples that can be run with the newest versions of Dart and Dartium.
I apologize to any reader who was confused or frustrated trying to run the examples listed in the article. I assure you great care was put into writing them and they work perfectly on the M2 release. I had no way to predict that such a large breaking change would occur right before the article went to print.
I still think you should give Dart a solid chance. While the timing wasn't the best, the changes Google made were very good and moved Dart toward a more cohesive API. As any Rails developer knows, breaking changes can be hard, but they are usually for the best!
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide
- Peppermint 7 Released
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- Sony Settles in Linux Battle
- Understanding Ceph and Its Place in the Market
- Libarchive Security Flaw Discovered
- Maru OS Brings Debian to Your Phone
- Snappy Moves to New Platforms
- Profiles and RC Files
- Integrating a Linux Cluster into a Production High-Performance Computing Environment
- Susan Lauber's Linux Command Line Complete Video Course (Prentice Hall)