1367: Installing

Explain xkcd: It's 'cause you're dumb.
(Difference between revisions)
Jump to: navigation, search
(Transcript)
(Explanation)
Line 8: Line 8:
  
 
==Explanation==
 
==Explanation==
{{incomplete|Created by a BOT - Please change this comment when editing this page.}}
+
{{incomplete|First draft.}}
 +
[[Cueball]] has a clever idea to skip the downloading and installing of applications on mobile phones with links to applications that would download the appropriate data and then run.
 +
 
 +
This concept however is already implemented in web applications. Clicking a link will make the browser download the web page and execute the contained HTML and javascript code.
 +
 
 +
In the title text [[Cueball]]s idea for local application storage is also already contained in the HTTP protocol by {{w|HTTP_cookie|cookies}} and {{w|Web_storage|HTML5 local storage}}.
 +
 
 +
Native phone applications and web applications are not completely interchangeable. The web browser that is needed to run web applications on a mobile phone doesn't allow access to several of the phones resources, like notifications and sensors.
 +
Projects like [http://cordova.apache.org/ Apache Cordova] try to make these resources available to web applications, but they do this by creating a native application wrapper for the web application.
  
 
==Transcript==
 
==Transcript==

Revision as of 06:05, 12 May 2014

Installing
But still, my scheme for creating and saving user config files and data locally to preserve them across reinstalls might be useful for--wait, that's cookies.
Title text: But still, my scheme for creating and saving user config files and data locally to preserve them across reinstalls might be useful for--wait, that's cookies.

Explanation

Ambox notice.png This explanation may be incomplete or incorrect: First draft.
If you can address this issue, please edit the page! Thanks.
Cueball has a clever idea to skip the downloading and installing of applications on mobile phones with links to applications that would download the appropriate data and then run.

This concept however is already implemented in web applications. Clicking a link will make the browser download the web page and execute the contained HTML and javascript code.

In the title text Cueballs idea for local application storage is also already contained in the HTTP protocol by cookies and HTML5 local storage.

Native phone applications and web applications are not completely interchangeable. The web browser that is needed to run web applications on a mobile phone doesn't allow access to several of the phones resources, like notifications and sensors. Projects like Apache Cordova try to make these resources available to web applications, but they do this by creating a native application wrapper for the web application.

Transcript

Installing


Cueball: Installing things has gotten so fast and painless.


Why not skip it entirely, and make a phone that has every app "Installed" already and just downloads and runs them on the fly?

I felt pretty clever until I realized I'd invented webpages.

comment.png add a comment! ⋅ Icons-mini-action refresh blue.gif refresh comments!

Discussion

explainxkcd has it pretty easy with this one since the comic explains a lot of itself. Maybe explain what a smartphone is and how apps work? 108.162.237.218 05:28, 12 May 2014 (UTC)

For some reason, this reminded me of the old Snaptu app. (https://en.wikipedia.org/wiki/Snaptu) 108.162.225.147 07:02, 12 May 2014 (UTC)

Maybe it should be mentioned that sometimes you DON'T want to auto-install every application and give it access to all your phone resources. Because, you know, malware. -- Hkmaly (talk) 09:47, 12 May 2014 (UTC)

I wonder why he chose cookies over localStorage... seems like localStorage does a better job of storing configs. greptalk12:06, 12 May 2014 (UTC)

document.cookies was invented before localStorage. --108.162.246.4 22:19, 12 May 2014 (UTC)

Firefox OS can technically do this, and technically does this. greptalk12:07, 12 May 2014 (UTC)

Web pages and native apps still has a few essential differences that prevent us to interchange them practically, at least for now. The latter can be compiled and optimized into binaries that executes performantly on the specific device/platform. Current web standards don't make pages/sites/apps this way, the web browser needs to load the text codes then interpret and run them on the fly, which is much slower. 199.27.128.79 08:33, 16 May 2014 (UTC)

Native apps on PCs? Sure. But on phones? Apps on phones rarely contains any native code and in fact often ARE written in web-compatible languages. I mean in java or javascript. Also, in many situations, combination of extremely optimized Java virtual machine and poorly optimized native code results in interpreted code running FASTER that compiled one. Not speaking about fact that not many applications NEEDS to run so fast - they spend most time waiting for disk, net, user input or screen refresh anyway. -- Hkmaly (talk) 10:22, 16 May 2014 (UTC)


Personal tools
Namespaces

Variants
Actions
Navigation
Tools

It seems you are using noscript, which is stopping our project wonderful ads from working. Explain xkcd uses ads to pay for bandwidth, and we manually approve all our advertisers, and our ads are restricted to unobtrusive images and slow animated GIFs. If you found this site helpful, please consider whitelisting us.

Want to advertise with us, or donate to us with Paypal or Bitcoin?