Wine on Javascript

[Zhenbo Li]

Hi All,
I'm came up with this idea since last year, and I'm glad to share this
idea to you today.

We tried to compile wine with clang[1], and most of the blocks have
been fixed[2]. I tried it on my computer, and wine was built
successfully, but `make test` failed.' I think wine+clang would work
fine soon.
Besides, the JavaScript engines are improving, for example, Google
V8[3], and we can expect a better performance[4].

Now, let's connect them: Why not run wine's IR with a JavaScript engine?[5]
At least, we have such benefits:
1. We can offer a online demo for wine
2. Wine can work on portable devices
3. Wine user can use the same prefix on different devices
4. We can have a better backend[6]

This is my humble idea. I'm looking forward to your reply.

[1]: http://wiki.winehq.org/Clang
[2]: https://llvm.org/bugs/show_bug.cgi?id=10638
[3]: https://code.google.com/p/v8/
[4]: http://arewefastyet.com/
[5]: http://kripken.github.io/emscripten-site/
[6]: https://software.intel.com/en-us/articles/graphics-acceleration-for-html5-an...

-- 
Have a nice (April Fool) day!
Zhenbo Li

[Jesse Litton]

This is why I try to avoid the internet on April 1st.

On 04/01/2015 04:05 AM, Zhenbo Li wrote:
> Hi All,
> I'm came up with this idea since last year, and I'm glad to share this
> idea to you today.
>
> We tried to compile wine with clang[1], and most of the blocks have
> been fixed[2]. I tried it on my computer, and wine was built
> successfully, but `make test` failed.' I think wine+clang would work
> fine soon.
> Besides, the JavaScript engines are improving, for example, Google
> V8[3], and we can expect a better performance[4].
>
> Now, let's connect them: Why not run wine's IR with a JavaScript engine?[5]
> At least, we have such benefits:
> 1. We can offer a online demo for wine
> 2. Wine can work on portable devices
> 3. Wine user can use the same prefix on different devices
> 4. We can have a better backend[6]
>
> This is my humble idea. I'm looking forward to your reply.
>
> [1]: http://wiki.winehq.org/Clang
> [2]: https://llvm.org/bugs/show_bug.cgi?id=10638
> [3]: https://code.google.com/p/v8/
> [4]: http://arewefastyet.com/
> [5]: http://kripken.github.io/emscripten-site/
> [6]: https://software.intel.com/en-us/articles/graphics-acceleration-for-html5-an...

[Bruno Jesus]

On Wed, Apr 1, 2015 at 7:25 AM, Jesse Litton <wine(a)eternaldusk.com> wrote:
> This is why I try to avoid the internet on April 1st.

I believe Zhenbo is telling the truth, since the kernel already boots
from javascript [1] it's perfectly plausible that any application can
run over it.

[1] http://bellard.org/jslinux/

Best Regards,
Bruno
> On 04/01/2015 04:05 AM, Zhenbo Li wrote:
> > Hi All,
> > I'm came up with this idea since last year, and I'm glad to share this
> > idea to you today.
> >
> > We tried to compile wine with clang[1], and most of the blocks have
> > been fixed[2]. I tried it on my computer, and wine was built
> > successfully, but `make test` failed.' I think wine+clang would work
> > fine soon.
> > Besides, the JavaScript engines are improving, for example, Google
> > V8[3], and we can expect a better performance[4].
> >
> > Now, let's connect them: Why not run wine's IR with a JavaScript engine?[5]
> > At least, we have such benefits:
> > 1. We can offer a online demo for wine
> > 2. Wine can work on portable devices
> > 3. Wine user can use the same prefix on different devices
> > 4. We can have a better backend[6]
> >
> > This is my humble idea. I'm looking forward to your reply.
> >
> > [1]: http://wiki.winehq.org/Clang
> > [2]: https://llvm.org/bugs/show_bug.cgi?id=10638
> > [3]: https://code.google.com/p/v8/
> > [4]: http://arewefastyet.com/
> > [5]: http://kripken.github.io/emscripten-site/
> > [6]: https://software.intel.com/en-us/articles/graphics-acceleration-for-html5-an...