3 ms·
> Sure you can - you just do it. You just make the necessary fix. No, you can't. Not simply. > But you do it quickly, within a short time of launching it. Any
by illiarian 3y ago
> Sure you can - you just do it. You just make the necessary fix.
No, you can't. Not simply.
> But you do it quickly, within a short time of launching it. Anyone who was able to make use of it within a couple months, will be able to adapt and fix things.
That's not how the web works. "People who make use of it in a few months" could easily apps and sites serving millions of people. This is a process that applies not only to image codecs, but to, say hardware APIs and interfaces, network protocols etc.
> But there's no reason to take so long.
There are very many reasons from technical to political to anything in between (and sideways, too).
- ars 3y agoSo, if it's behind a flag then people know not to use it, and therefor no one actually uses it. So you can change it if you want, but you never will because you'll never get feedback. Or, if it's not behind a flag, then you can tell people not to use it, but they will anyway, which is exactly what you want, because then you get feedback. And when you change it, nothing really bad happens. Sounds like the flag method is a failure, and just releasing it actually works.
- illiarian 3y agoAll the modern features that you see on the web have gone through the flag method at one point. In JPEG XL case it failed not because it was behind a flag, and the failure of one feature doesn't mean that the entire system isn't working. > Sounds like the flag method is a failure, and just releasing it actually works. No, "just releasing" doesn't work for the reasons I outlined above.