http://en.wikipedia.org/wiki/Google_Native_Client
This thing helps to run machine code applications inside Chrome brouser. Apps can be in x86, x64 machine code, ARM, MIPS< or in the LLVM bytecode.
I'm played with SDK a bit, now I have to understand the file format apps are stored in and to use fasm to make them.

Oh dear, that sounds awful (the opposite of awefull). Remote sites able to run arbitrary code in the client is a security disaster waiting to happen. Hehe, I guess it will all be sandboxed or something, just like Java was supposed to be sandboxed and look at how successful that wasn't at stopping exploits.

03 May 2014, 12:35

JohnFound

Joined: 16 Jun 2003
Posts: 3500
Location: Bulgaria

JohnFound

Yes, really bad idea, normally for an evil corporation, pushing its product and willing to do anything to conquer new markets.

Don't know, I think it's a bit better than virtual machines. And much better than just downloading exe files from unknown sites.

There is a big difference. When we download something we consciously choose to do it and we have the option to examine it (perhaps with an AV, or debugger or whatever). But with a website we have no such choices and we get something we didn't even ask for that automatically runs without any action on our part. Perhaps the difference appears to be subtle but it is very significant and important distinction.

03 May 2014, 15:19

JohnFound

Joined: 16 Jun 2003
Posts: 3500
Location: Bulgaria

JohnFound

The web browser is a web browser. Not an OS. So, it should not run programs. The OS should.

03 May 2014, 16:20

michikaze

Joined: 03 May 2014
Posts: 5

michikaze

@revolution
I think there is an option to forbid it anywhere except google play. I also think that running it in browser is safer, since developers expect problems to happen, and so the restrictions are more fixed than on most users enviropment. It warned me then app tried to store local information, probably it also warns user before actual start. I haven't tested it online, only on localhost.

@JohnFound
Don't see much difference, I spend in browser more time than anywhere else. Wouldn't you like to skip the downloading step and play something right on the page?

Unfortunately, for now JS can't be avoided entirely, simply because HTTP protocol lacks some needed functionality. I mean the server-push technology is impossible without JS.

But the fundamental usage of a browser is to browse (sorry for being captain obvious here). And I think that is where people have tried to push the browser beyond what it actually is. Server push is not a browsing function. That should be in some other program if one needs such a thing.

04 May 2014, 09:30

JohnFound

Joined: 16 Jun 2003
Posts: 3500
Location: Bulgaria

JohnFound

revolution wrote:

But the fundamental usage of a browser is to browse (sorry for being captain obvious here). And I think that is where people have tried to push the browser beyond what it actually is. Server push is not a browsing function. That should be in some other program if one needs such a thing.

Hm, it is not so simple. From one point of view - yes you are right. But IMHO, it depends on the answer of "To browse what?". What if the documents that have to be browsed are not static, bug changing in time? Then the browser should provide some way to browse a dynamic document. Of course, the browser can refresh the document periodically, but this is wrong approach. Then the browser should have some functionality to detect the document change and to read needed part of the document. This is what is called "server push", because only the server knows when the document is changed. The only way now to provide such a functionality is by client side scripting, because the base client-server protocol (HTTP) supports only static documents.

Client side scripting is not "server push". That is just automated client polling. If by changing documents you mean games then that should be a different program, not a browser function.

04 May 2014, 10:26

JohnFound

Joined: 16 Jun 2003
Posts: 3500
Location: Bulgaria

JohnFound

revolution wrote:

That is just automated client polling.

No it is not, actually. The scripting is used to create some kind of "client site server" that connects to the web server and waits for events on the connection. The web server is that pushes events on the connection. The client side script reacts on these events and changes the document accordingly.

Why is it even considered necessary to have it? Is there a purpose behind it other than "that would be cool"?

There are some limitations in using the JS, flash and java's virtual machines: main is of course speed. Raw machine code will be able to load and work faster. It's simplier, and I hope it will find it's niche.

Quote:

But the fundamental usage of a browser is to browse (sorry for being captain obvious here).

to interact with everything outside your computer

Quote:

No. Absolutely not. Would you let random people come into your house and play with your children unmonitored?

weird analogy

Quote:

so... whats stopping the program from making it's own instructions ?

what do you mean by "making instructions"? Self modifying code? I think the lack of write access.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum