101–110 of 169 posts
Earlier quoted context omitted.
That language will be web, I suspect. Perhaps Google will offer prerolled components specifically for Android? I strongly suspect that Chrome is the platform Google wants to push for client development now, with Android essentially as a shell for it. While web may arguably be "worse" on Android now, Google has a very large, talented engineering team who could change that relatively fast. Java is a dead end at this po…
Web is a platform, so they would need to rewrite half of Android, I don't think it would be worth it, I don't see real benefits of that for users or devs... I think that Java 8 is a great language, I like it a lot more than Javascript. Go would be great too.
"Chrome-specific code that means they won’t be able to run on other web browsers" This sounds vaguely familiar...
Prediction: The much-anticipated convergence of Android and Chrome is near. These new Chrome apps are the programming model for the upcoming native Android webapps The next milestone I expect to see is V8 added alongside Dalvik as a first-class runtime for Android. Maybe in Android KitKat?
If they would do this we'd have a new set of apps that behaved and felt very differently which would probably cause a lot of confusion among users.
What I could imagine is some kind of framework that makes it easier to share data and state between a Chrome app on the desktop and Android apps on mobile.
Earlier quoted context omitted.
Having developed several server-side projects in Dart, the language/environment brings a hell of a lot to the table optimized for reducing complexity and improving productivity which: - Provides a familiar language with clean semantics and low ceremony - Provides the fastest dev iteration times (there's no compile step, just edit + run in Dart VM/Dartium) - Provides ~10x faster start-up times than JS with snapshots (…
Most of your points were already covered by Smaltalk, and we all know where it is nowadays. Sorry, but I lost count of the languages I have used since 1986 and just don't believe in Dart ever taking off unless Google makes it so.
I've also used a number of languages in the last 15 years, and I've personally found Dart to be overall be the most productive which has become my go-to language whenever I need to something quick done. It's missing an ecosystem of mature libs which popularity helps most with - but Google has a ton of investment behind Dart which is developing the entire platform (language/libs/toolchain) giving it its best chance to succeed - if it fails to gain any traction it wont be for technical reasons. It looks like it will take over and be the preferred to succeed GWT and Closure Library, with internal usage it should see continued investment for years to come.
Prediction: The much-anticipated convergence of Android and Chrome is near. These new Chrome apps are the programming model for the upcoming native Android webapps The next milestone I expect to see is V8 added alongside Dalvik as a first-class runtime for Android. Maybe in Android KitKat?
Earlier quoted context omitted.
For me the exciting bit is being able to access devices from them. E.g. I've been waiting for this for a while because you can write an app which communicates directly with an Arduino or any other serial device. This means that a lot of special purpose desktop apps communicating with custom hardware can be written as Chrome apps and take advantage of the speed/ ease of UI development of web apps. For one of the apps…
Chrome extensions have had access to external devices for a long time. It's not often used, but I've done stuff implementing chrome + arduino. http://developer.chrome.com/apps/app_hardware.html A quick google search shows: https://github.com/BertHartm/Chromeduino
One thing that I think is really cool about Chrome Apps is that you can write USB drivers in Javascript that will run on any platform that runs Chrome or Chromium. This means that if you want to make a hardware device that syncs with the cloud, all you have to do is write what is essentially a web app, and anyone with Windows, OS X, Linux, or Chrome OS can use your thing. I'm personally working on a Chrome SDR app fo…
yeah, same here, I'm writing a CNC controller, the UI is a google chrome packaged app talking on USB. it's a pain to use, with all the restriction, the buggy API (it doesn't crash, it just hangs, you can't investigate) and the browser bugs (I have to use a canary for development, I'm really far from a release).
Prediction: The much-anticipated convergence of Android and Chrome is near. These new Chrome apps are the programming model for the upcoming native Android webapps The next milestone I expect to see is V8 added alongside Dalvik as a first-class runtime for Android. Maybe in Android KitKat?