Why was JPEG encoding/GIF decoding removed?

Questions about the LÖVE API, installing LÖVE and other support related questions go here.
Forum rules
Before you make a thread asking for help, read this.
User avatar
slime
Solid Snayke
Posts: 3166
Joined: Mon Aug 23, 2010 6:45 am
Location: Nova Scotia, Canada
Contact:

Re: Why was JPEG encoding/GIF decoding removed?

Post by slime »

Someguynamedpie wrote:given the lack of JIT it'd be preferable to use the Lua C api instead.
Indeed. Some parts of love (for example ImageData methods) use the FFI when JIT compilation is available, and the Lua C API otherwise, partly since the FFI is so slow when it's not JIT-compiled.
User avatar
Someguynamedpie
Citizen
Posts: 71
Joined: Wed Mar 31, 2010 10:59 pm

Re: Why was JPEG encoding/GIF decoding removed?

Post by Someguynamedpie »

slime wrote:
Someguynamedpie wrote:given the lack of JIT it'd be preferable to use the Lua C api instead.
Indeed. Some parts of love (for example ImageData methods) use the FFI when JIT compilation is available, and the Lua C API otherwise, partly since the FFI is so slow when it's not JIT-compiled.
Interesting; however, out of curiosity, why aren't anonymous FFI types used instead, to avoid namespace collisions? Also, I noticed that the SoundData does the same thing, but have always found it odd you can't bulk upload samples but instead have to loop through all the samples in your sound data, it might be worth allowing buffer uploads using FFI types as a lower level feature (given sample manipulation are already a pretty low level feature as it is) for expediency.
Post Reply

Who is online

Users browsing this forum: Ahrefs [Bot], Google [Bot] and 13 guests