News for hackers. Stuff that matters.
Re:Mozilla and Epic Announce Unreal Engine for the Web by pifflesnort on Wednesday March 27, 2013 @04:02PM (#5451642)
> Right, so by 2040 we can't distribute an application without rebuilding it for 5 or 6 different architectures

5 or 6? 2040? All we've seen over the past 20 years is the gradual reduction of in-use architectures down to a few winning players. We're even seeing it in the SoC/MCU space now, where custom architectures are being replaced with ARM.

I expect to continue to see evolution and simplification, not revolution. If there is a revolution, well, we'll want to take advantage of the power of that fancy new hardware, I suppose.

> one of which is a bitcode format that doesn't even run at native speeds, despite the name.

PNaCL generates native code from the bitcode.

[response to your edit]

> You're basically demonstrating the entire problem with the Native Client camp - you're so myopically focused on the immediate needs and the immediate environment (arm! x86! games! performance this year!) that you have absolutely no appreciation for the trail of destruction being left for future generations.

I would say that you're demonstrating why the web camp continues to fail so horribly to move past simple applications: you're so myopically focused on the ideology of tomorrow over providing a great user experience today.

In fact, I day say you're leaving a far worse trail of destruction, because web applications are the ultimate expression of always-on DRM. When the servers for your "apps" disappear in a few years time, the applications will disappear right along with them -- forever.

How is the Internet Archive going to archive your webapp?

> You have Pepper which is a huge bastardized, specialized clone of all WebGL/HTML 5 audio/media APIs

That's an overstatement of Pepper. It's quite simple -- far more so than the massive browser stack that WebGL+HTML5 brings with it.

In fact, Pepper is simple and constrained enough that someone other than an existing browser vendor or major corporation could actually implement and support a standalone implementation of it. By contrast, producing a compatible browser is such an enormous undertaking that even companies like Opera are giving up and tracking WebKit.

Re:Mozilla and Epic Announce Unreal Engine for the Web by hosay123 on Wednesday March 27, 2013 @04:27PM (#5451806)
>> You're so myopically focused on the ideology of tomorrow over providing a great user experience today.

> Through ActiveX Technologies, today's static Web pages come alive with a new generation of active content, including animation, 3-D virtual reality, video and other multimedia content. ActiveX Technologies embrace Internet standards and will be delivered on multiple platforms, giving users a rich, open framework for innovation while taking full advantage of their investments in applications, tools and source code. "ActiveX brings together the best of the Internet and the best of the PC," said Paul Maritz, group vice president of the platforms group at Microsoft. "Users want the richest, most compelling content delivered through the ubiquitous Internet."

— Microsoft press release, March 1996.

We've seen this all before, and it was as much of a land grab using similar "user experience" excuses then as it is now. And despite it all, everything from this press release is possible with open technologies today already. Now we come to address the performance issue, and platform proponents (let's drop the pretence – platform shills) continue to fiercely reject it, because providing a good user experience was never the original agenda.

I'm deeply reminded of the leaked internal DART e-mail ( https://gist.github.com/paulmillr/1208618 ) where as much ink was expended on marketshare as it was on technical issues.

Re:Mozilla and Epic Announce Unreal Engine for the Web by pifflesnort on Wednesday March 27, 2013 @04:30PM (#5451825)
This is a false comparison.

ActiveX was technologically flawed: it was specific to Microsoft Windows, and it was insecure.

NaCL is secure and portable, without sacrificing the user experience today.

Indirectly referring to me as a platform shill is unwarranted. The reason that I argue so strenuously for maximizing performance is simply that performance improves user experience.

> I'm deeply reminded of the leaked internal DART e-mail ( https://gist.github.com/paulmillr/1208618 ) where as much ink was expended on marketshare as it was on technical issues.

I've read the whole memo, and I don't understand what your complaint is at all. Google seems to be focused on actually improving the web as an application development target, and making it competitive with modern platforms.

Re:Mozilla and Epic Announce Unreal Engine for the Web by hosay123 on Wednesday March 27, 2013 @04:40PM (#5451885)
By your own words Native Client is technically flawed: it's specific to x86 and ARM (and whatever other vaporware platforms they promise "next week" – PNaCl has been due for years already), and removing the VM, it's also insecure. So basically Native Client is ActiveX inside a VM.
Re:Mozilla and Epic Announce Unreal Engine for the Web by pifflesnort on Wednesday March 27, 2013 @04:48PM (#5451929)
How exactly is that by my own words? You also seem to be confusing quite a few technical topics.

First, you're equating ARM and x86 with Microsoft Windows. Those are all "platforms", but they exist at very different levels of the technology stack, and the impact of relying on them is quite different.

Samsung and Apple can both ship compatible ARM devices. Only Microsoft could ship an ActiveX runtime.

Second, you're throwing out "security" as a red herring without actually explaining what is insecure. Exactly what are you talking about?

Lastly, if PNaCL is not viable, then NaCL is not viable. Thus, Google is holding off on NaCL until PNaCL is viable. In the meantime, I'm targeting mobile and desktop applications -- today -- which is entirely consistent with my earlier stated position.

Re:Mozilla and Epic Announce Unreal Engine for the Web by MatthewPhillips on Wednesday March 27, 2013 @05:59PM (#5452279)
"ActiveX is definitely going cross-platform," Willis says. "To be a viable technology for the Internet, we need to be able to support more platforms than Microsoft Windows. You cannot predict what kind of platforms will be on the other end."

http://books.google.com/books?id=97W638tj_NsC&pg=PA38...

Re:Mozilla and Epic Announce Unreal Engine for the Web by pifflesnort on Wednesday March 27, 2013 @06:57PM (#5452507)
ActiveX was, at its very core, not portable.

Are you making an objective technical argument, or a solipsistic one?

Re:Mozilla and Epic Announce Unreal Engine for the Web by kevingadd on Wednesday March 27, 2013 @07:09PM (#5452545)
Which part of ActiveX wasn't portable? COM is definitely portable. Shipping signed executables that implement COM interfaces is as "portable" as NaCL is, so no problems there.

If your complaint is that ActiveX controls used the Win32 API, then you're missing the point. A Mac or Linux ActiveX control would use OS-native APIs, but still use COM and be an ActiveX control.

Furthermore, if you had even looked up the Wikipedia page for ActiveX, you'd see that:

"On 17 October 1996, Microsoft announced availability of the beta release of the Microsoft® ActiveX Software Development Kit (SDK) for the Macintosh."

Yep, so non-portable that they released a Mac SDK back when Macs were PowerPC. Super non-portable. The non-portablest.

Re:Mozilla and Epic Announce Unreal Engine for the Web by pifflesnort on Wednesday March 27, 2013 @08:57PM (#5452861)
ActiveX was portable the way that the SYSV/SVR4 binaries were portable -- almost entirely in theory.

"It was introduced in 1996 and is commonly used in its Windows operating system. In principle it is not dependent on Microsoft Windows, but in practice, most ActiveX controls require either Microsoft Windows or a Windows emulator. Most also require the client to be running on Intel x86 hardware, because they contain compiled code."

What rational comparison do you have between NaCL's constrained syscall interface + Pepper, and ActiveX?

> Yep, so non-portable that they released a Mac SDK back when Macs were PowerPC. Super non-portable. The non-portablest.

Which produced binaries that couldn't run on any other PPC OS other than Mac OS, and provided a runtime that couldn't run the ActiveX controls being deployed for Windows clients, even if it was somehow magically possible to run x86 code.

It was explicitly advertised as being non-portable, as a feature: "Developers can create ActiveX Controls for the Mac that integrate with other components and leverage the full functionality of the Mac operating system, taking advantage of features such as Apple QuickTime."

http://www.microsoft.com/en-us/news/press/1996/oct96/macpr.a...

So, yes, "non-portablest".

What exactly is the equivalence to (P)NaCL?

Re:Mozilla and Epic Announce Unreal Engine for the Web by MatthewPhillips on Wednesday March 27, 2013 @09:39PM (#5452972)
The fact that NaCL only works in Chromium, and will only ever work in Chromium.
Re:Mozilla and Epic Announce Unreal Engine for the Web by derefr on Wednesday March 27, 2013 @11:02PM (#5453167)
Here's an implementation of NaCl that has nothing to do with Chromium: http://zerovm.org/
Re:Mozilla and Epic Announce Unreal Engine for the Web by pifflesnort on Wednesday March 27, 2013 @10:21PM (#5453084)
Not due to technical constraints, unlike ActiveX. It's a self-fulfilling prophesy -- Mozilla's refusal to adopt NaCL will, indeed, stall the adoption of NaCL.

Things might get more interesting if NaCL provides a higher performance deployment target for Chrome users than asm.js does. Then you can just cross-compile for both.

Re:Mozilla and Epic Announce Unreal Engine for the Web by bzbarsky on Wednesday March 27, 2013 @04:19PM (#5451746)
Last I checked, Pepper was full of underdefined stuff that depended on details of Chrome internals. So no, it's not "simple and constrained" enough that you can implement it without reverse-engineering said internals....
Re:Mozilla and Epic Announce Unreal Engine for the Web by pifflesnort on Wednesday March 27, 2013 @04:22PM (#5451773)
Anything in particular? I eyeballed the API docs recently and didn't see anything so frightening, but you may have more in-depth evaluation:

    https://developers.google.com/native-client/peppercpp/inherits
Google has also stated that they're open to re-evaluating and reworking the API.
Re:Mozilla and Epic Announce Unreal Engine for the Web by bzbarsky on Wednesday March 27, 2013 @05:23PM (#5452098)
A simple example: What happens if negative values are passed for the top_left argument of Graphics2D::PaintImageData? The API documentation doesn't say.

I just picked a class and function at random.... That sort of thing is all over the API.