11–20 of 102 posts
I don't understand Chrome apps. They require installation and only work on Chrome, so they come with none of the benefits of the web. They are slower and uglier than native Windows/Mac/Linux apps. What's the point?
I don't understand Chrome apps. They require installation and only work on Chrome, so they come with none of the benefits of the web. They are slower and uglier than native Windows/Mac/Linux apps. What's the point?
Just to add a few: - They work offline, like native apps, but are cross-platform, like web apps. - You can develop and distribute them without running your own server infrastructure (the Chrome store will distribute them and the run locally). - They work on ChromeOS
And as far as offline goes, that’s an active area of development within the HTML5 spec. It doesn’t strike me as a particular draw given that it’s at least possible, if still somewhat painful, to build truly cross-platform apps with offline capabilities.
Why should I support ChromeOS? ChromeOS is not the web!
Earlier quoted context omitted.
Just to add a few: - They work offline, like native apps, but are cross-platform, like web apps. - You can develop and distribute them without running your own server infrastructure (the Chrome store will distribute them and the run locally). - They work on ChromeOS
That’s a funny definition of cross-platform. You mean, it’s cross-platform if you use Google’s browser. And as far as offline goes, that’s an active area of development within the HTML5 spec. It doesn’t strike me as a particular draw given that it’s at least possible, if still somewhat painful, to build truly cross-platform apps with offline capabilities. Why should I support ChromeOS? ChromeOS is not the web!
I'm not telling you what you should do. I'm telling you why this model is attractive to me.
Earlier quoted context omitted.
Just to add a few: - They work offline, like native apps, but are cross-platform, like web apps. - You can develop and distribute them without running your own server infrastructure (the Chrome store will distribute them and the run locally). - They work on ChromeOS
That’s a funny definition of cross-platform. You mean, it’s cross-platform if you use Google’s browser. And as far as offline goes, that’s an active area of development within the HTML5 spec. It doesn’t strike me as a particular draw given that it’s at least possible, if still somewhat painful, to build truly cross-platform apps with offline capabilities. Why should I support ChromeOS? ChromeOS is not the web!
>>It doesn’t strike me as a particular draw given that it’s at least possible, if still somewhat painful, to build truly cross-platform apps with offline capabilities.
If you can achieve a cross platform experience using something that's installed on most PC's, and if it offers features or simplicity that is not available in the truly cross-platform spec, then that seems like a strong draw.
Earlier quoted context omitted.
Just to add a few: - They work offline, like native apps, but are cross-platform, like web apps. - You can develop and distribute them without running your own server infrastructure (the Chrome store will distribute them and the run locally). - They work on ChromeOS
That’s a funny definition of cross-platform. You mean, it’s cross-platform if you use Google’s browser. And as far as offline goes, that’s an active area of development within the HTML5 spec. It doesn’t strike me as a particular draw given that it’s at least possible, if still somewhat painful, to build truly cross-platform apps with offline capabilities. Why should I support ChromeOS? ChromeOS is not the web!
I haven't been excited about web-based IDE's previously as all the ones I've tried have been clunky and slow, but it looks like this is being built with Dart so should offer better start-up and runtime performance given it will be running natively on the DartVM inside Chrome App.
Looking forward to the day that I'm able to login, hassle-free to any ChromeOS PC and have instant access to my working environment. Which will be useful if you ever want to upgrade your workstation, e.g. when it breaks down or a shiny new model comes out.
Currently there are two kinds of platforms: the web, initilly intended for documents and native platforms, designed primarily for apps. Both have different strengths. The web: no installation, hyperlinking, decentralization and openess, etc. Native plaftorms: window manager, speed, collaboration between apps, much richer API, centralization (enabling human interface guidelines for example), etc.
A third platform having the best of both worlds would be great but that's just my utopic dream :)
Nope, they're Google's way of extinguishing non-Chrome browsers. Only Chrome/Chromium will be supported. That's called vendor lock-in - regardless of being open source.
Earlier quoted context omitted.
Just to add a few: - They work offline, like native apps, but are cross-platform, like web apps. - You can develop and distribute them without running your own server infrastructure (the Chrome store will distribute them and the run locally). - They work on ChromeOS
That’s a funny definition of cross-platform. You mean, it’s cross-platform if you use Google’s browser. And as far as offline goes, that’s an active area of development within the HTML5 spec. It doesn’t strike me as a particular draw given that it’s at least possible, if still somewhat painful, to build truly cross-platform apps with offline capabilities. Why should I support ChromeOS? ChromeOS is not the web!
Earlier quoted context omitted.
That’s a funny definition of cross-platform. You mean, it’s cross-platform if you use Google’s browser. And as far as offline goes, that’s an active area of development within the HTML5 spec. It doesn’t strike me as a particular draw given that it’s at least possible, if still somewhat painful, to build truly cross-platform apps with offline capabilities. Why should I support ChromeOS? ChromeOS is not the web!
Java is only cross platform if you use the JDK, Flash is only cross platform if you use Adobe's plugin, etc. So I don't think this is a completely funny definition of cross platform. >>It doesn’t strike me as a particular draw given that it’s at least possible, if still somewhat painful, to build truly cross-platform apps with offline capabilities. If you can achieve a cross platform experience using something that's…
Chrome's API don't have this. Chrome == Chromium, and there's nothing else under the sun that either have it or want it.
HOWEVER - Chrome has the largest marketshare by far, thus enforcing whatever it wants. Knowing competitors will not pick up the functionality because "its really made just for Chrome, not for the open web", that's called "extinguishing" competitors. But I'm sure everyone is all too familiar with that concept.