The web is unnecessarily complicated. Multiple browsers support different technologies, different standards, leading to varying performance and compatibility issues. The problem is that it may be naive to think that there really open standards. Certainly, there are standards that can be referenced, but stopping and reflecting a moment that decided the standards? In other words, if the web is really open, why it appears that large enterprises govern the ship when it comes to major decisions?
See also : Sony Xperia Z4: Here what to expect
Google is a company that is at the center of the decisions that will shape the future of the web, which is not necessarily a bad thing. The thing to challenge is that the company could probably have a conflict of interest when it contributes to Web standards. Why? It develops its own browser (Chrome) and associated operating system (Chrome OS). Today, Google announced that it abandons SPDY for HTTP / 2 in Chrome.
"HTTP is the underlying network protocol that powers the web. The majority of sites use version 1.1 of HTTP, which was defined in 1999. A lot has changed on the web since its implementation, and a new version of the protocol called HTTP / 2 is well on the way to the normalization . We plan to gradually deploy support for HTTP / 2 in Chrome 40 in the coming weeks " , says Chris Bentzel, Google.
HTTP / 2 finally here!
Bentzel further explains that certain key features such as multiplexing, header compression, prioritization and protocol negotiation evolved from the work in an open environment, but not standard, which is the SPDY protocol. Chrome pushed the SPDY protocol from Chrome 6, but since most of the benefits of SPDY are present in HTTP / 2, it's time to say goodbye . He said that the web giant plans to remove support for SPDY in early 2016, and also remove the support for TLS extension named for the NPN ALPN in Chrome at the same time. "The server administrators are strongly encouraged to upgrade to HTTP / 2 and ALPN " , he advocated.
In this case, the passage of SPDY HTTP / 2 is the right choice. Comparatively, they are both "open", but HTTP / 2 is clearly the future because it is more like a standard. Frankly, most users will not feel any impact on this change. However, developers should take note. Fortunately, the SPDY compatibility will not be withdrawn before 2016, so you have ample time to make the transition.
Chrome has become a widely used and popular browser for a variety of reasons, but one of them is its speed. Google Chrome is touted to be fast and agile, thanks to its own protocols, SPDY. When Chrome was built SPDY was necessary because he crashed dizzily other browsers using the HTTP 1.1 protocol to transfer Web content. With the HTTP / 2 release, Google is finally ready to drop SPDY since the last HTTP standard brings a lot of performance improvements. And then, as all the major browser vendors have implemented, it is logical that Google toe the line.
See also : Sony Xperia Z4: Here what to expect
Google is a company that is at the center of the decisions that will shape the future of the web, which is not necessarily a bad thing. The thing to challenge is that the company could probably have a conflict of interest when it contributes to Web standards. Why? It develops its own browser (Chrome) and associated operating system (Chrome OS). Today, Google announced that it abandons SPDY for HTTP / 2 in Chrome.
HTTP / 2 finally here!
Bentzel further explains that certain key features such as multiplexing, header compression, prioritization and protocol negotiation evolved from the work in an open environment, but not standard, which is the SPDY protocol. Chrome pushed the SPDY protocol from Chrome 6, but since most of the benefits of SPDY are present in HTTP / 2, it's time to say goodbye . He said that the web giant plans to remove support for SPDY in early 2016, and also remove the support for TLS extension named for the NPN ALPN in Chrome at the same time. "The server administrators are strongly encouraged to upgrade to HTTP / 2 and ALPN " , he advocated.
In this case, the passage of SPDY HTTP / 2 is the right choice. Comparatively, they are both "open", but HTTP / 2 is clearly the future because it is more like a standard. Frankly, most users will not feel any impact on this change. However, developers should take note. Fortunately, the SPDY compatibility will not be withdrawn before 2016, so you have ample time to make the transition.
Chrome has become a widely used and popular browser for a variety of reasons, but one of them is its speed. Google Chrome is touted to be fast and agile, thanks to its own protocols, SPDY. When Chrome was built SPDY was necessary because he crashed dizzily other browsers using the HTTP 1.1 protocol to transfer Web content. With the HTTP / 2 release, Google is finally ready to drop SPDY since the last HTTP standard brings a lot of performance improvements. And then, as all the major browser vendors have implemented, it is logical that Google toe the line.