Re:Mozilla’s Rejection of NativeClient Hurts the Open Web
by stcredzero on Sunday January 02, 2011 @01:39AM
(#2059577)
Thinking ahead is good, but precluding a technology because a particular implementation would have to be changed in 5 years is just flat-out silly for tech. You couldn't ever buy a car with criteria like that. Grasping for straws.
[ Parent
| on HN ]
Re:Mozilla’s Rejection of NativeClient Hurts the Open Web
by rizzzer on Sunday January 02, 2011 @01:55AM
(#2059615)
The point is that if you have only x86 and ARM binaries, you can't run them directly on a new architecture. It isn't a matter of changing an implementation.
It's like trying to run a C64 binary today. The only practical way is emulation, which is slow - but thankfully fast enough in this case. In general though, it means new architectures will run more slowly than existing ones. That's not a good thing.
Re:Mozilla’s Rejection of NativeClient Hurts the Open Web
by stcredzero on Sunday January 02, 2011 @02:36AM
(#2059673)
By then just recompile it for the next wave of tech/standards.
Re:Mozilla’s Rejection of NativeClient Hurts the Open Web
by rizzzer on Sunday January 02, 2011 @11:27AM
(#2060290)
Do you think we still have the source code to all C64 binaries out there? We don't. And in 5 years, we won't have the source to all the stuff we are running now.
Re:Mozilla’s Rejection of NativeClient Hurts the Open Web
by stcredzero on Sunday January 02, 2011 @07:32PM
(#2061620)
Fine, those things can just die or limp along.