Top Menu

Google Chrome Bans Many Older Chrome Plug-ins

When Steve Jobs was still alive, he made a lot of waves when he came out against Flash technology for the iPhone. A lot of people thought this was a bad move but it looks like with the release of HTML Version 5, Steve Jobs was onto something. The technology is a fast evolving arena. You always have to look forward to the future and make sure that whatever technology platforms you use must be scalable to the needs of the future.

Steve Jobs correctly saw that Flash being a proprietary technology was too limiting for the fast moving and fast evolving world of mobile technology. This is why most websites that are being designed for mobile optimization are using HTML 5. Thanks to Steve Jobs, this has become the de facto standard. Well it looks like the browsers are not far behind. Back when Internet Explorer was the predominant internet browser, many creative developers came up with plug ins to get around internet explorer’s limitations. Many of these plug ins used Java, Unity and Silverlight to truly expand and build on the typical browser’s capabilities.

Well, due to security concerns, starting in 2014 Google Chrome will no longer support these plug-ins. Keep in mind that we’re talking about plug-ins and not extensions. Plug-ins tend to be heavier on resources and they may have security holes. This is why Google is dispensing supporting plug-ins; however, extensions are still welcome. If a developer would like to build an extension for Google Chrome, that’s okay because that’s built on the Chrome platform according to Chrome rules. There’s a little development hole called the plug in that is causing some issues with Google.

We think this is a great move because it forces developers to play within the general extension platform of Chrome. This is a great move in google’s part and allows for greater scalability and standardization going forward.

, , ,