So if the temperature increases, maybe Sahara will be green again? There is no rain there because there is a cold current flowing alongside the banks of the Mediterranean.
Really good stuff starts around 3.00 when he starts discussing Yale tuitions starting from the 19-th century, and compares them to gold, blue-collar wages etc.
If it's not a thin-layer above the core OS (Linux) how is that possible that it's been hacked to run on Android?
I watched a longish video discussing how webOS was developed and, well, I found it disappointing. Compare the man-months that went to webOS development to the 1.2$ bln HP paid. It just doesn't make any sense to me.
In the first place -- what was this WebOS thing that HP paid 1.2 bln $ for?
Do I miss something when I say that it is just a thin JavaScript layer on top of Linux, possibly not more complicated than an average JavaScript framework?
Why everybody insists on calling WebOS an operating system? I thought HP blew $1.2 bln to buy a JavaScript library (similar to YUI, JQuery, etc.). The underlying OS (Linux) exposed some API through that framework? -- oh my -- big deal.
Last time I checked I could not use Chrome for browsing documentation loaded from the local disk. This is the most innocent HTML application imaginable - just a frameset with the navigation panel on the left (TOC, Index, etc.) and the actual contents on the right. And Chrome will not allow one frame (e.g. the TOC) to load a page in another frame because it is a security risk. Duh...
How sad I cannot use Chrome until they fix this bug:
http://code.google.com/p/chromium/issues/detail?id=47416
The most innocent applications (framesets with documentation, TOC/Search on the left, actual content on the right) do not work in Chrome if loaded from a local hard-drive (or chrome is started with some weird, undocumented switch). Those framesets worked fine even in Netscape 4 and ancient versions of KHTML.
Frameset have long been unfashionable but, hey, they do have legitimate uses. Think a documentation bundle with a navigation panel on the left and the actual content in the right frame. Such framesets have worked fine even in ancient versions of Netscape and Konqueror/KHTML.
So, you'd expect they will work in Chrome, right? Well, if you load a frameset from a local drive, they don't:
http://code.google.com/p/chromium/issues/detail?id=47416
Because some moron thought this would make the browser more secure.
Slashdot Mirror
The competition from Google TV must be particularly stiff: http://tech.slashdot.org/story/11/11/11/1822240/logitech-calls-google-tv-a-big-mistake
... I have not upgraded my home page since 1999. Will its size have stayed the same?
How unfortunate that EU is running out of money and might no longer be able to fund such truly brilliant research.
So if the temperature increases, maybe Sahara will be green again? There is no rain there because there is a cold current flowing alongside the banks of the Mediterranean.
> rebels are fighting back on their iPhones
Translated: the government have created an app so that they can better track and manipulate the citizens
Or maybe this is saying that they are throwing iPhones instead of stones?
What a stupid thing to brag about. If they caught him, they could try to make use of his skills an knowledge.
> Does this mean that they will be reviving the TouchPad?
And not licensing the WebOS to vacuum-cleaner manufactures?
You should really check (and comment on) this: How government programs drive up college tuitions
Really good stuff starts around 3.00 when he starts discussing Yale tuitions starting from the 19-th century, and compares them to gold, blue-collar wages etc.
If it's not a thin-layer above the core OS (Linux) how is that possible that it's been hacked to run on Android?
I watched a longish video discussing how webOS was developed and, well, I found it disappointing. Compare the man-months that went to webOS development to the 1.2$ bln HP paid. It just doesn't make any sense to me.
In the first place -- what was this WebOS thing that HP paid 1.2 bln $ for?
Do I miss something when I say that it is just a thin JavaScript layer on top of Linux, possibly not more complicated than an average JavaScript framework?
Why everybody insists on calling WebOS an operating system? I thought HP blew $1.2 bln to buy a JavaScript library (similar to YUI, JQuery, etc.). The underlying OS (Linux) exposed some API through that framework? -- oh my -- big deal.
> Clinton, Obama, and the Housing Crisis; http://www.youtube.com/watch?v=ivmL-lXNy64#t=2m10s
I didn't know you could link to a certain time point in a YT movie (#t=2m10s).
Now, mod this up as informative.
Last time I checked I could not use Chrome for browsing documentation loaded from the local disk. This is the most innocent HTML application imaginable - just a frameset with the navigation panel on the left (TOC, Index, etc.) and the actual contents on the right. And Chrome will not allow one frame (e.g. the TOC) to load a page in another frame because it is a security risk. Duh...
How sad I cannot use Chrome until they fix this bug: http://code.google.com/p/chromium/issues/detail?id=47416 The most innocent applications (framesets with documentation, TOC/Search on the left, actual content on the right) do not work in Chrome if loaded from a local hard-drive (or chrome is started with some weird, undocumented switch). Those framesets worked fine even in Netscape 4 and ancient versions of KHTML.
Frameset have long been unfashionable but, hey, they do have legitimate uses. Think a documentation bundle with a navigation panel on the left and the actual content in the right frame. Such framesets have worked fine even in ancient versions of Netscape and Konqueror/KHTML. So, you'd expect they will work in Chrome, right? Well, if you load a frameset from a local drive, they don't: http://code.google.com/p/chromium/issues/detail?id=47416 Because some moron thought this would make the browser more secure.