I'd still like Prism to live on...it allows the user to turn any website into an application.
Mozilla Chromeless 0.2
41–50 of 72 posts
Re: Mozilla Chromeless 0.2
#42Earlier quoted context omitted.
https://developer.mozilla.org/en/chrome ^ I think Mozilla called their thing Chrome for a long while.
I believe "chrome" has meant "the GUI of an application" for a very long time. I think it predates mozilla, but I could be mistaken.
Re: Mozilla Chromeless 0.2
#43Earlier quoted context omitted.
Actually, check out Adobe Air (for ajax developers). Basically it's webkit as a desktop app and pretty mature. I've used it in the past, but I think Mozilla has a big opportunity here as Adobe has pretty much abandoned the web desktop aspect of AIR to focus on flash/flex for mobile. Also, Adobe removes some of the best parts of webkit like web workers and I recently found a giant performance bug in their javascript e…
Does Air still require a shared runtime component to be installed beforehand? We all know how well that worked with Java.
Looks like Air is similar to Java in that respect (or in my more cynical view, Visual Basic - but multiplatform).
Re: Mozilla Chromeless 0.2
#44Am I the only one who thought this was some attack on Chrome? Whenever I hear talk about browser chrome I always think that Google's name choice was a little confusing. Probably best in the end, though, since it's a catchy name.
Google seems to be making a habit of that... Closure and Noop are two other examples that come to mind.
Re: Mozilla Chromeless 0.2
#45Re: Mozilla Chromeless 0.2
#46Re: Mozilla Chromeless 0.2
#47Earlier quoted context omitted.
> The reason that Google Native Client is not set fair to become an "open Web standard" is because three of the four non-MS vendors oppose it for reasons of self-interest. As a user, I don't want to see NaCl's compile-once-per-each-architecture model become part of the web. It's true browsers oppose it out of self interest, but NaCl has its own problems that haven't been solved. PNaCl is a good start and much more in…
So what remaining problems with NaCl's compile-once-per-each-architecture model do you believe can't be solved by the combination of multi-architecture compilers (llvm, gcc ...) on the developer/server end and PNaCl on the client? Obviously the implementation is incomplete and immature, but Mozilla and Opera aren't even pretending that their opposition to NaCl is based on the immaturity of the implementation. > And w…
It looks like PNaCl aims to "solve" this problem by using 32-bit-targeted LLVM... including 32-bit pointer alignment. It's not immediately obvious how portable this would be to some hardware, and more importantly I'm not aware of any plans to support anything other than x86 and ARM initially (well, and x86-64 using its ability to run 32-bit code as far as I can tell). Am I just missing something on this front?
If I'm not missing anything, then this project's main impact if it caught on would be to restrict the set of hardware on which you can access web content, which is NOT a good thing.
Re: Mozilla Chromeless 0.2
#48Earlier quoted context omitted.
Actually, check out Adobe Air (for ajax developers). Basically it's webkit as a desktop app and pretty mature. I've used it in the past, but I think Mozilla has a big opportunity here as Adobe has pretty much abandoned the web desktop aspect of AIR to focus on flash/flex for mobile. Also, Adobe removes some of the best parts of webkit like web workers and I recently found a giant performance bug in their javascript e…
Does Air still require a shared runtime component to be installed beforehand? We all know how well that worked with Java.
Re: Mozilla Chromeless 0.2
#49Earlier quoted context omitted.
So what remaining problems with NaCl's compile-once-per-each-architecture model do you believe can't be solved by the combination of multi-architecture compilers (llvm, gcc ...) on the developer/server end and PNaCl on the client? Obviously the implementation is incomplete and immature, but Mozilla and Opera aren't even pretending that their opposition to NaCl is based on the immaturity of the implementation. > And w…
Well, for a start there's the problem that LLVM itself is architecture-dependent, last I checked. It's not as arhictecture-dependent as assembly but the last time I looked you couldn't generate the same LLVM on x86 and x86-64, say. Has that changed? It looks like PNaCl aims to "solve" this problem by using 32-bit-targeted LLVM... including 32-bit pointer alignment. It's not immediately obvious how portable this would…
LLVM bytecode is 100% architecture and platform independent, unless you call into platform-specific bits or into blobs of machine code.
Re: Mozilla Chromeless 0.2
#50Earlier quoted context omitted.
Actually, check out Adobe Air (for ajax developers). Basically it's webkit as a desktop app and pretty mature. I've used it in the past, but I think Mozilla has a big opportunity here as Adobe has pretty much abandoned the web desktop aspect of AIR to focus on flash/flex for mobile. Also, Adobe removes some of the best parts of webkit like web workers and I recently found a giant performance bug in their javascript e…
Does Air still require a shared runtime component to be installed beforehand? We all know how well that worked with Java.
Up until Craig's lawyers killed my app, I was using the flash installer that was seamless. Same sort of installation process can be seen on TweetDeck which uses AIR.