Ask HN: Does Dart programming language need mvvm frameworks?

#1

Post by basicscholar » Sun, Feb 21, 2016, 7:54 PM UTC

Hi! I'm new to everything, specially web application development.

Taking a look into the insane JavaScript ecosystem, and seeing how many libraries/frameworks are being released every minute. Makes me want to better start writing web applications with the Dart programming language. And leaving JavaScript alone.

Or does Dart have the same amount of insanity in its ecosystem?

I mean, I just don't want to be spending my time in Angular, Backbone, Knockout, ... , React, ...

Thank you :)

Re: Ask HN: Does Dart programming language need mvvm frameworks?

#2

Post by softinio » Sun, Feb 21, 2016, 8:12 PM UTC

I would not go the dart route personally. If you want something different to javascript have a look at Typescript or Elm:

http://www.typescriptlang.org/

http://elm-lang.org/

Re: Ask HN: Does Dart programming language need mvvm frameworks?

#3

Post by basicscholar » Sun, Feb 21, 2016, 8:23 PM UTC

softinio wrote: post #2

I would not go the dart route personally. If you want something different to javascript have a look at Typescript or Elm: http://www.typescriptlang.org/ http://elm-lang.org/

Thank you @softinio Elm programming language seems promising. (y)

Re: Ask HN: Does Dart programming language need mvvm frameworks?

#4

Post by lollipop25 » Sun, Feb 21, 2016, 10:35 PM UTC

> Makes me want to better start writing web applications with the Dart programming language. And leaving JavaScript alone.

Escaping to another language won't solve this. Every language has it's own problems, just in different form and hype. It just so happens that JS is in the spotlight right now. What about PHP? What about CoffeeScript? What about Java? They all had their 15mins of (horrible) fame, JS is no different. Also consider that Dart was meant to overthrow JS, it just didn't succeed.

If you take Dart (or any non-JS language for that matter), consider that the web runs on JS. You'll have to worry (again) about tooling, integration with existing code, on-boarding of additional team members, availability of Dart devs, the abundance/lack of libraries, support.