Yes, but it's not recommended - it does not have inter-frame compression, so it is significantly less efficient than just having a regular video file and slapping 'gif' on it.
That's not strictly correct, it's rather that the current encoder does no inter-frame compression. Patches (and the frame system in general) does give tools to do some inter-frame compression (not as many as in video, but still quite expressive), just nobody stepped up to implement compression using them for animations yet.
Progressive decoding isn't a very useful video feature because you need to decode the whole frame before you decode the next frame for inter-frame coding methods anyway.
It is, however, a very useful image format feature, giving you most information from the spinner/sticker/emoji/sprite, and refinig the already playing loop as it loads. That's why animated jxl is a bad video format — it's not a video format, it is a separate kind of seemingly weird thing.
What, isn't this the cue for someone to explain that it's ironic webp is really a video format which is a bad image format, and now we have symmetry that JpegXL is a good image format which is bad video format? :-D
(I don't know if any of this is true, but it sounds funny...)
> We wouldn't tolerate secrecy in the calculations used to keep our buildings upright, and we shouldn't tolerate opacity in the software that keeps our tractors, hearing aids, ventilators, pacemakers, trains, games consoles, phones, CCTVs, door locks, and government ministries working.
Construction industry if full of privately owned technologies and closed source software, from architectural drawing board up to the last glass panel in a window.
Building are staying upright not because of openness, but because of the enforced standards for construction. Same can be applied to software orders.
Want to prevent a government office suite to be bricked remotely? Put forth requirements for autonomous work, self hosting, multiyear coverage for critical patches and ability to export the data at any moment in the format of your preference. Whoever provides this will get the contract.
This seems to me far more realistic aim than trying to enforce global legal straight jacket to be universally applied to all software and hardware products available for purchase in your country
For the major part BYD sales performance is dependent on government subsidies in the country where they sell three quarters of all the cars they produce. That is a high risk factor investors don't like.
And what's your opinion if the law would oblige the companies to remove features their products have like tracking transparency popups? Two countries' courts already fined Apple for enforcing a popup that warns users about tracking across third party apps (a feature Apple themselves do not use)?
My prior POV was that Apple would jettison the feature globally, but the discussion elsewhere in this thread suggests that salami slicing at the software-level is a cost larger companies are willing to bear.
I wonder why the author doesn't use IL2CPP and sticks to Mono. IL2CPP does produce much faster code, making Mono builds obsolete. This should be the very first step you do if you care at all about performance in Unity.
