Tweet
PNaCL is much more interesting than I first thought.
First, as I said before, I want you to have the ability to run PNaCL if that is what you need.
I apologize, it has been a few years since the last time I looked at that project. At that time, an application needed a version for each platform. And it required that you keep a 64bit version, even if you were only targeting a 32bit version. So, Google recommended you copy your 32bit exe and rename the copy for the 64bit version.
Still, due to the design, isn't the only thing you are gaining is speed? It requires you compile any dependencies you need, and not use things provided on the host, unless they specifically design a route for you, right? This implementation interface is the same one that the browser vendors have created as browser soup in the web, making it necessary to rewrite the same css in four of five different ways for every design. Every vendor would have their on pet interfaces that would convince you to use their browser, creating larger code to deal with the different code paths.
Or is your argument simply being able to use whichever language you want, instead of relying on what you are given?
PNaCL is much closer in concept to ActiveX than Dart, trying to meet many of the same problems. At least it is open source. It does have the issue of only being available to Chrome and Google products, whereas Dart is targeted at all evergreen browsers. (Did Opera adopt it when they adopted Blink?)
Also, I see PNaCL as more of an as needed tool, such as provided something cpu intensive such as encoding video in the browser. (Not sure why anyone would want to do that on a web page, but it might make sense in a media web app.) Dart is meant to handle the rest of the program, though I don't know that it wouldn't meet the need of the media app, as I haven't written an encoder in Dart, yet.
Anyway, Goodnight.
First, as I said before, I want you to have the ability to run PNaCL if that is what you need.
I apologize, it has been a few years since the last time I looked at that project. At that time, an application needed a version for each platform. And it required that you keep a 64bit version, even if you were only targeting a 32bit version. So, Google recommended you copy your 32bit exe and rename the copy for the 64bit version.
Still, due to the design, isn't the only thing you are gaining is speed? It requires you compile any dependencies you need, and not use things provided on the host, unless they specifically design a route for you, right? This implementation interface is the same one that the browser vendors have created as browser soup in the web, making it necessary to rewrite the same css in four of five different ways for every design. Every vendor would have their on pet interfaces that would convince you to use their browser, creating larger code to deal with the different code paths.
Or is your argument simply being able to use whichever language you want, instead of relying on what you are given?
PNaCL is much closer in concept to ActiveX than Dart, trying to meet many of the same problems. At least it is open source. It does have the issue of only being available to Chrome and Google products, whereas Dart is targeted at all evergreen browsers. (Did Opera adopt it when they adopted Blink?)
Also, I see PNaCL as more of an as needed tool, such as provided something cpu intensive such as encoding video in the browser. (Not sure why anyone would want to do that on a web page, but it might make sense in a media web app.) Dart is meant to handle the rest of the program, though I don't know that it wouldn't meet the need of the media app, as I haven't written an encoder in Dart, yet.
Anyway, Goodnight.
Comment