> Should they leave it on Python 2 with zero security updates, or invest lots of time porting to python 3?
Leave it, of course. The only meaningful security risk at this point is something like heartbleed. We're talking security issue in 10 year battle hardened protocol. This is a fantastically rare case. Not something you need headcount on a constant basis to deal with.
"250M printers compromised by Google Cloud Print" is an ugly look. It won't matter at that time that Google rescued a beloved product from being Deep-Sixed.
Re:Google Kills Cloud Print
by Already__Taken on Monday November 25, 2019 @10:28PM
(#21635432)
Right. Is nobody remembering the Google Plus API fiasco?
Sounds simple but sometimes it is not so easy.
E.g. it might be written in Python 2 for all we know. Should they leave it on Python 2 with zero security updates, or invest lots of time porting to python 3?
Obviously there will likely be a million other internal examples of the python 2 to 3 migration that we don't know about.