Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Wine Support On Chrome OS Is Unlikely

  1. #1
    Join Date
    Jan 2007
    Posts
    14,359

    Default Wine Support On Chrome OS Is Unlikely

    Phoronix: Wine Support On Chrome OS Is Unlikely

    If you were hoping to eventually be able to run Windows applications within Google's Chrome OS environment via Wine, the possibilities of that working out well are very slim...

    http://www.phoronix.com/vr.php?view=MTYyMDI

  2. #2
    Join Date
    Nov 2010
    Posts
    341

    Default

    ChromeOS sucks anyway. Better solution would be to replace it with Ubuntu, but I hear that's hard to do.

  3. #3
    Join Date
    Nov 2007
    Location
    Poland
    Posts
    15

    Default

    On the other "google" front chromium developers just killed video decoding acceleration on linux by marking it "wont fix"
    http://code.google.com/p/chromium/is...tail?id=137247
    and the reason was inability to make it stable
    https://codereview.chromium.org/176883018/
    :-(

  4. #4
    Join Date
    Jan 2014
    Location
    Tallahassee, FL 32304
    Posts
    89

    Default

    Who would anyone want to have WINE made for Chrome OS? I think Google could get into legal trouble with Microsoft if WINE is included in Chrome OS.

  5. #5
    Join Date
    Dec 2009
    Posts
    321

    Default

    How can Wine work on ARM? It doesn't emulate a CPU and can run code only on x86. Unless I misunderstood something. If this all is about x86 then it's another story. Doesn't ChromeOS allow installing extra packages in developer mode? It's essentially a custom Gentoo. So why wouldn't Wine work there?
    Last edited by shmerl; 03-03-2014 at 05:14 PM.

  6. #6

    Default I have to disagree on your comment

    Quote Originally Posted by GraysonPeddie View Post
    Who would anyone want to have WINE made for Chrome OS? I think Google could get into legal trouble with Microsoft if WINE is included in Chrome OS.
    1. wine on mac's? microsoft have not suse apple at all!

    2. wine is not supported by google it is open source and supported/hosted by code weaver

    3. when an application/software is made the developer/owner or he/she will go though the legal stuff not the platform the it's based on?

  7. #7
    Join Date
    Feb 2012
    Location
    Austin, TX, USA
    Posts
    43

    Default

    Quote Originally Posted by Dukenukemx View Post
    ChromeOS sucks anyway. Better solution would be to replace it with Ubuntu, but I hear that's hard to do.
    Xubuntu seems to be working well on the Acer C720, complete with Steam.
    http://www.reddit.com/r/chrubuntu/co...the_acer_c720/

    Here's one list of working Steam games (including, funny enough, Skyrim on Wine at 15-20 fps):
    http://www.reddit.com/r/Crouton/comm...p_etc_through/

  8. #8
    Join Date
    Nov 2013
    Posts
    142

    Default

    Quote Originally Posted by shmerl View Post
    How can Wine work on ARM? It doesn't emulate a CPU and can run code only on x86. Unless I misunderstood something. If this all is about x86 then it's another story. Doesn't ChromeOS allow installing extra packages in developer mode? It's essentially a custom Gentoo. So why wouldn't Wine work there?
    I remember reading that they're working on interfacing with QEMU to run x86 software on arm.
    And yes, this is about running Wine as a Chrome plugin. Once you enable developer mode, you can do pretty much whatever you want.

  9. #9
    Join Date
    Dec 2009
    Posts
    321

    Default

    Quote Originally Posted by Spittie View Post
    I remember reading that they're working on interfacing with QEMU to run x86 software on arm.
    This sounds like performance nightmare, especially on mobile devices. But I guess it can have some uses.

  10. #10
    Join Date
    Dec 2012
    Posts
    196

    Default

    And this is one of the reasons why Chrome OS can't be mainstream, even if all applications are made offline. It's made for the cloud, very secure, but with the sandboxed approach model, the available APIs are very limited. If I'm not mistaken, another big limitation (for security reasons) is that chrome apps (as any HTML5 app) have their own sandboxed filesystem storage, but can't access the global filesystem.

    Android at least exposes Linux syscalls.

    Chrome OS with Android APIs (thus, running apps on the Android Dalvik/Art RT instead of sanboxing as a chrome process) would offer a much more capable system.
    Last edited by newwen; 03-04-2014 at 05:05 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •