Claus Reinke wrote:
1 help to document current base functionality in code
(there could be standard libraries listing "pre-defined"
functions imported from the host environment)
We don't have one notion of "foreign" in the real world. Nations and
languages differ in vital ways. I'm reminded of Solzhenitsyn:
"In recent times it has been fashionable to talk of the levelling of
nations, of the disappearance of different races in the melting-pot of
contemporary civilization. I do not agree with this opinion, but its
discussion remains another question. Here it is merely fitting to say
that the disappearance of nations would have impoverished us no less
than if all men had become alike, with one personality and one face.
*Nations are the wealth of mankind, its collective personalities; the
very least of them wears its own special colours and bears within itself
a special facet of divine intention.*"
Anyway, back to code ;-).
Different native-code compilers and OSes (not always tied, btw) will
choose different FFIs, depending on local macro- and micro-economics.
Even today we have a choice between calling conventions on Windows (not
always obvious; Rust has changed at least once in its young life).
The OS and compiler release schedules are decoupled from browser and
other JS engine-bearing software cycles.
FFIs are inherently unsafe if not crippled or lumbered with a complex
research project such as NaCl or Xax.
So I doubt TC39 would ever agree on a single FFI.
2 provide a window for optimized, cross-browser
implementation of device access, without the work-arounds
currently employed in Phonegap/Cordova and related projects
You seem to have missed the work in the last 8 months in the W3C DAP and
WebAPI groups:
http://brendaneich.com/2012/02/mobile-web-api-evolution/
Gecko pioneered most of these for B2G but Samsung is getting WebKit
patches in. FFIs are *not* the way to integrate device access, note
well. We need the web JS security model, appropriately extended.
/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
