>>2865817device designers and desktop programmers have very different philosophies when it comes to designing code.
for 99% of applications, the advent of modern, fast computers has caused desktop programmers to become lazy in general. instead of
> "i have more processing power so now i can make the computer answer harder problems in the same amount of time"its now:
> "the computer is fast enough that instead of working really hard-to-program fast code, i can save time and effort by just writing lazy, more abstract code."device manufacturers to some extent still use the first philosophy because they have to cram the best features into the cheapest (worst computer) package possible that can get the job done.
plus it's common knowlege that the source code behind anything from Adobe is a giant pukestain
Also, im looking into this seriously now. Virtually all the free RAW editors for XTrans use dcraw to do the actual decoding, which uses a demosaicing algo designed by Frank M (complicated last name i can't remember). this is what causes the nasty artifacts.
you can see the code theyre using for demosaicing by opening up the latest version of dcraw.c and ctrl+f RAF a few times. it's pretty well commented
If someone figures out a better algorithm and gets their patch applied to dcraw, we will see all the open source lighttable softwares eventually adopt it and get better.
i might start putting some thought into this...