Some pretty bold claims there. I’d like to see the evidence behind them.
I haven’t seen or heard anything to suggest FLAC has been superseded by a different, more efficient codec.
I don’t know why you’d dedicate paragraphs over getting upset about FLAC. It is space efficient, lossless, CPU efficient and tags well. Sounds like a perfect template for an audio codec, in fact.
This is nonsense! Roon supports FLAC because the consumer uses it. Moreover, i’d go as far as saying that FLAC is now the defacto standard (container) for lossless audio.
And most importantly (in my opinion), FLAC files contain built-in CRCs so one can run a batch job to insure that all the embedded CRCs (from when ripped/created) match the decoded CRCs. WAV files do not have this ability (nor do Apple Lossless). This is a key feature for me. And if one really wants uncompressed for some odd reason, dbpa offers a FLAC uncompressed option (not compression =0, but actually uncompressed).
Not specifically related to the OP question, but relevant based on the ensuing rabbit hole. I don’t really mind what tagging solution Roon, Flac or anything else uses. I have implemented a process that use MusicBrainz to scan and create/update downloaded music before it is released to my library. MusicBrainz uses an AcousticID instead of existing tags to identify tracks and so far, it has never been wrong after about 1000 tracks. Roon is a streamer/player, not a tagged, it should focus on being the best streamer possible. FLAC is just a container that already supports a horde of tags, has a huge installed base, and is nearly universally supported making the value proposition to change containers rather low. The proper solution would be to not change container types, but update the container itself to not use compression at the users request. Players don’t care how compressed or not a FLAC file is, just that it is a FLAC file which its DLLs and APIs can read and understand. Simple change with no massive update of the ecosystem to support a new format.