As web technologies have matured, there’s less of a need for browser plug-ins to add features for video playback and hardware access to the browser. That’s what Google thinks — so too does Mozilla — and it’s the main reason that Chrome will cease to support the old Netscape Plug-In API starting on January 1, 2014.
What does that mean for the web as whole for Google’s Chrome browser going forward? Chris Albrecht and I discuss exactly that during our GigaOM Chrome Show podcast, so download the episode or listen below for our thoughts. The move fits in with the advanced features in HTML 5 so that users don’t have to download and install plug-ins for various functionality: Most of these will be built in or programmatically available to web developers.

{"source":"https:\/\/gigaom.com\/2013\/09\/29\/google-chrome-starts-pulling-the-plug-on-browser-plug-ins\/wijax\/49e8740702c6da9341d50357217fb629","varname":"wijax_bf8724d4ee33b9e2b00081f789897deb","title_element":"header","title_class":"widget-title","title_before":"%3Cheader%20class%3D%22widget-title%22%3E","title_after":"%3C%2Fheader%3E"}