Actually the article is wrong about this, the code is open source (Chrome or alteast Chromium which it is based on is an open source project after all) and their are drafts for the RFC.
Actually there are people working on submitting to the IETF as a RFC, it takes time.
It just uses an extra header to get it started/switch to the SPDY-protocol. Not only that, but the extension for HTTP to make the switch is already gone through most of the IETF-process.
I wouldn't be surprised if the biggest hold up is actually websockets. Because the new 'HTML5' websockets where found to be insecure, atleast in combination with transparant caching proxies that didn't implement HTTP properly. Java and Flash are just as 'insecure' or actually it is these proxies which can be fooled in caching the wrong information (think kind of like phising).
The last 'spec' of websockets was implemented atleast Opera and the Firefox-developers but as these problems exist, the websocket protocol is disabled in their browsers.
Actually Firefox 4 has had a lot of speed improvements, among other things start up and size. It is now efficient enough to run on your mobile. Even though the features (and webtechnologies) support increased tremendously.
Actually, I would say Firefox copies the UI from Opera. Firefox Sync actually existed as a seperate Firefox extension from Mozilla before Chrome added cloud sync.
The Firefox developers just want to release more often so they are changing the because there are many, many HTML5/CSS features which are now only implemented not at all or half (same for any other browser). These are just very large specs.
So they need people to upgrade frequently to get that code out to users (thus webdevelopers) and to get attention from users they are doing something for them to keep marketshare ?
Actually, NT3.x uses the same graphical design as Windows 3.x; Windows NT 4 uses the same as Windows 95 Windows 2000 (NT5) the same like Window 98. Well kind of. And Windows XP was for both home and office. (NT5.1) (Server side: Windows 2003) Windows Vista was NT6 (Server side: Windows 2008) Windows 7 ironically is NT6.1 (Server side: Windows 2008 R2 ?)
The obvious answer is, if you develop for all these different platforms you are probably doing it wrong (unless you have a specialized app). You probably should just use HTML/CSS/JS and something like PhoneGap.
I'm sure some kind of 'webapps' based on webtechnologies will be supported for ChromeOS.:-)
That way you can also target the iPhone, iPad, HP WebOS and everything else with the same codebase.
And the internet connection provided for all these devices is a DSL-/cable-modem/router running Linux, the websites he/she visits are running on Linux.
Slashdot Mirror
SPDY just multiplexes HTTP-requests over TLS ('SSL' as used by HTTPS) or in theory TCP.
Actually the article is wrong about this, the code is open source (Chrome or alteast Chromium which it is based on is an open source project after all) and their are drafts for the RFC.
Actually there are people working on submitting to the IETF as a RFC, it takes time.
It just uses an extra header to get it started/switch to the SPDY-protocol. Not only that, but the extension for HTTP to make the switch is already gone through most of the IETF-process.
I wouldn't be surprised if the biggest hold up is actually websockets. Because the new 'HTML5' websockets where found to be insecure, atleast in combination with transparant caching proxies that didn't implement HTTP properly. Java and Flash are just as 'insecure' or actually it is these proxies which can be fooled in caching the wrong information (think kind of like phising).
The last 'spec' of websockets was implemented atleast Opera and the Firefox-developers but as these problems exist, the websocket protocol is disabled in their browsers.
That is why people who deal with larger projects in javascript read things like 'JavaScript: The Good Parts' from Douglas Crockford.
Before someone asks why Lisp is useful, because I think functional languages are getting more attention again.
Just an example, look at webdevelopers a lot of them use JavaScript. It may look like C-syntax, but it actually is very much like Lisp.
Learning Lisp is probably very useful though.
The old video's from MIT are on Youtube btw, if anyone wants to:
http://www.youtube.com/watch?v=2Op3QLzMgSY&playnext=1&list=PL22393BCA1DAB07B2
So they keep the hashes and use that in the protocol-calculations, interresting. Thanks.
I think NT-passwords are not hashed, but encrypted, because the cleartext password is needed to implement the NTLM-authentication.
Like this ?:
http://www.supersimplestorageservice.com/
Seems pretty cheap. ;-)
Actually Firefox 4 has had a lot of speed improvements, among other things start up and size. It is now efficient enough to run on your mobile. Even though the features (and webtechnologies) support increased tremendously.
I think the PR will be about features, like it always mostly has been.
Like:
"Firefox just released their new version with features X and Y" (so maybe not even a version number in that title)
Ubuntu also has these strange code names (Apple is almost as bad) which to me sounds more like someone using the Firesomething add-on.
My guess would be they frequently break API's, that is why they frequently release a 'major' version.
Actually, I would say Firefox copies the UI from Opera. Firefox Sync actually existed as a seperate Firefox extension from Mozilla before Chrome added cloud sync.
The Firefox developers just want to release more often so they are changing the because there are many, many HTML5/CSS features which are now only implemented not at all or half (same for any other browser). These are just very large specs.
So they need people to upgrade frequently to get that code out to users (thus webdevelopers) and to get attention from users they are doing something for them to keep marketshare ?
Actually, NT3.x uses the same graphical design as Windows 3.x;
Windows NT 4 uses the same as Windows 95
Windows 2000 (NT5) the same like Window 98. Well kind of.
And Windows XP was for both home and office. (NT5.1) (Server side: Windows 2003)
Windows Vista was NT6 (Server side: Windows 2008)
Windows 7 ironically is NT6.1 (Server side: Windows 2008 R2 ?)
The obvious answer is, if you develop for all these different platforms you are probably doing it wrong (unless you have a specialized app). You probably should just use HTML/CSS/JS and something like PhoneGap.
I'm sure some kind of 'webapps' based on webtechnologies will be supported for ChromeOS. :-)
That way you can also target the iPhone, iPad, HP WebOS and everything else with the same codebase.
Xfce has Thunar, it is atleast a whole lot faster, haven't tried running it remotely though.
It actually works for me in the latest nightly build of Firefox, so maybe someone is working on it. :-)
The Woz recently said something along the lines of:
"Tablet is the PC for 'normal people'" (read: consumers)
The tablets Apple sells is a closed environment, nothing like the PC. Where the OS is also most hidden.
So I guess the desktop never really was a good product for the consumer market.
The desktop is a chicken&egg problem.
And a Microsoft-still-does-deals problem I think.
Just look what happend to the netbooks-market.
I wonder if the same will happen to the tablet-market.
Apple is bigger, what is your point ? ;-)
And the internet connection provided for all these devices is a DSL-/cable-modem/router running Linux, the websites he/she visits are running on Linux.
Interresting enough it's based on Windows 2000 kernel.
You mean like http://www.startssl.com/ already does this ? For free for the current CA-system.
That is something I want too.
Restrict a CA to a domain-list.
Possible have an option for: ask to add domain to list.
But it only works for technical users. No noob will understand this, so it isn't a real solution.