> o changes are being made to the .tflite file extension or format. Conversion tools will continue to output .tflite flatbuffer files, and .tflite files will be readable by LiteRT.
Odd choice since it strongly undermines the stated purpose of the rebrand in the first place: to break it away from the Tensorflow brand and emphasise it being model/framework agnostic. Working with ".tflite" files more or less immortalises what they're trying to get away from.
Would've made more sense to bite the bullet and launch with a ".litert" format which is identical to ".tflite", but continue to work with the later. That would remove the conceptual integrity issue without breaking any compatibility.
Odd choice since it strongly undermines the stated purpose of the rebrand in the first place: to break it away from the Tensorflow brand and emphasise it being model/framework agnostic. Working with ".tflite" files more or less immortalises what they're trying to get away from.
Would've made more sense to bite the bullet and launch with a ".litert" format which is identical to ".tflite", but continue to work with the later. That would remove the conceptual integrity issue without breaking any compatibility.