DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Join us today at 1 PM EST: "3-Step Approach to Comprehensive Runtime Application Security"
Save your seat
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Deployment
  4. Dart for Android: Why Google Should Embrace Dart over Java

Dart for Android: Why Google Should Embrace Dart over Java

Alec Noller user avatar by
Alec Noller
·
Jun. 18, 14 · Interview
Like (0)
Save
Tweet
Share
14.93K Views

Join the DZone community and get the full member experience.

Join For Free

Google's programming language, Dart, has been around for a while now, but it hasn't quite taken off the way others have. It's not currently central to the way anything is done, and according to some, that shouldn't be the case. Cyril Mottier, for example, recently wrote an article suggesting a hypothetical sunny future for Dart: a starring role as the core programming language for Android.

Mottier presents a laundry list of limitations for Java as it currently stands when it comes to Android:

  • Outdated primitives types
  • The whole Google vs. Oracle fiasco
  • Google's lack of control over Java's progression

And that's just a few of them. The answer, Mottier suggests, may be to bring Dart to Android. 

He's not alone in this opinion, either. In fact, just a week or two earlier, Christian Grobmeier made a similar argument on his blog, describing Dart as something of an under-appreciated gem brought to the world a little too early, before it truly had a place it belonged:

Dart is great, but the browser vendors didn't ask for it. Nor did the hardcore JavaScript users. It is and will continue to be hard for Google to convince other people to switch from JavaScript.

Sure, you can do a lot of great stuff with Dart; like server side programming. But JavaScript has that all too. So why bother?

And the answer, Grobmeier says, is Mottier's as well: bring Dart to Android.

The argument is even more poignant now the Apple has released Swift, which Grobmeier sees as an analogous development. Swift is surprisingly similar to Dart, he says, and it's making him a bit jealous:

Now with Apple having a great, nice-looking and easy-to-use language like Swift ready for programmers, I think it's now the perfect time to bring Dart to Android. I am honest: being a long time Java developer, I will not miss Java that much.

It may not be a perfect solution, or a comprehensive one, though. Wolfram Rittmeyer, responding to Mottier's post, suggests that he is open to alternatives to Java - that seems to be a recurring sentiment - but takes issue with the idea that Google might embrace Dart so fully:

If there is one thing, where I didn’t agree with Cyril, it’s his paragraph, where he suggests that Dart could be the one language for all of Google’s projects. Such that Google could get rid of Python, Java, C++ and whatever else they use. I don’t think that’s feasible.

The problem, Rittmeyer says, is that a full switch to Dart would render vast quantities of Java libraries useless. Google certainly has the man-power and money to get around a hurdle like that, but it's still a major hurdle. Beyond that, most would agree that there is no single programming language that is the best for everything. 

So, unless you're pushing for acceptance of Groovy for Android instead, Dart as a Java replacement is an interesting hypothetical future. There may be a few drawbacks - or maybe a lot of drawbacks - but interesting nonetheless. What do you think? Could it work?


Dart (programming language) Google (verb) Java (programming language) Android (robot)

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Efficiently Computing Permissions at Scale: Our Engineering Approach
  • Taming Cloud Costs With Infracost
  • Five Key Metaverse Launch Features: Everything You Need to Know
  • Express Hibernate Queries as Type-Safe Java Streams

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: