11–20 of 53 posts
You know what, bringing Dart to android development may be a good idea. Web hobbyists hate java with a passion but may embrace Dart for its resemblance with javascript.
Honestly I still don't see the point of Dart. It's made some strange choices (IMHO) like optional typing. The idea that code can be shared between client and server is the panacea touted by GWT, which (IMHO) failed to eventuate (eg some classes weren't "GWT compatible" and this included protocol buffers generated classes). Dart seems like the next throw of the dice. I am not optimistic about its successes. Go on the…
Honestly I still don't see the point of Dart. It's made some strange choices (IMHO) like optional typing. The idea that code can be shared between client and server is the panacea touted by GWT, which (IMHO) failed to eventuate (eg some classes weren't "GWT compatible" and this included protocol buffers generated classes). Dart seems like the next throw of the dice. I am not optimistic about its successes. Go on the…
Dart + Native Client Modules almost makes me excited about web programming again. Obviously not for general websites, but for specific applications it would not be unreasonable to require Chrome to be installed as the alternative would be installing a native app anyway.
I think I know what you mean, though. It's nice to be able to pick a narrow target that covers most of your customers and code for that.
And then I completely lost interest when I started structuring my code well, and realised that I didn't need it as much as I thought.
You know what, bringing Dart to android development may be a good idea. Web hobbyists hate java with a passion but may embrace Dart for its resemblance with javascript.
Bringing Go development to Android would be even better, but I doubt either will ever happen, at least not as an officially sanctioned way to create native apps.
There are some things in Dart that would be nice to have in Javascript, but I don't see why Google wouldn't just try to work them into future ECMAScript revisions. With the exception of banning eval and run-time modification of prototypes, I don't see anything that's completely incompatible with a future revision of Javascript. I'd even bet that the ES standards committee will eventually give in on the "arrow" lambda…
Is google really betting dart will take off? Because I don't see microsoft/apple/mozilla supporting it in the future. But of course dart can still be a cofeescript competitor.
Honestly I still don't see the point of Dart. It's made some strange choices (IMHO) like optional typing. The idea that code can be shared between client and server is the panacea touted by GWT, which (IMHO) failed to eventuate (eg some classes weren't "GWT compatible" and this included protocol buffers generated classes). Dart seems like the next throw of the dice. I am not optimistic about its successes. Go on the…
There are middle grounds between unsafe manual memory management and full garbage collection other than atomic reference counting. Region systems (like in Cyclone and Rust), for example.