We're here also maintaining some big platforms using Adobe Flash.
Even I mostly agree on the need to reduce unnecessary Flash usage on the public web, there are some features Flash provides that can not still be replaced by HTML5, like audio recording on browser which is not available on some still widely used web browsers.
If there is a need of providing support for those features on relatively old browsers in corporate environments then the best (the only?) choice is Flash Player.
I can also argue on the far less number of development and testing hours needed compared with HTML5 equivalent, where you know that content will render perfectly on all browsers that include Flash Player.
IMO, before killing player itself we will should focus in killing all those old browsers versions to provide developers a real alternative for these features.
Even I mostly agree on the need to reduce unnecessary Flash usage on the public web, there are some features Flash provides that can not still be replaced by HTML5, like audio recording on browser which is not available on some still widely used web browsers.
If there is a need of providing support for those features on relatively old browsers in corporate environments then the best (the only?) choice is Flash Player.
I can also argue on the far less number of development and testing hours needed compared with HTML5 equivalent, where you know that content will render perfectly on all browsers that include Flash Player.
IMO, before killing player itself we will should focus in killing all those old browsers versions to provide developers a real alternative for these features.