Hacker Newsnew | past | comments | ask | show | jobs | submit | donatzsky's commentslogin

I'll take this opportunity to shamelessly plug my darktable beginner guide, which aggregates advice and the currently best tutorials: https://notebook.stereofictional.com/how-to-get-started-with...

If you're coming from the likes of Lightroom or Capture One you will have to learn a very different way of working, but in return you get a lot of control over the edit.


Atrocious in what way? But no, it hasn't changed in any significant ways since 2019.


Better is subjective, but the editing is much more powerful. However, it's also a completely different editing paradigm (largely on-rails vs. layers/nodes), so some acclimatisation is required.


As the one responsible for writing much of the FAQ, I can assure you that's not what is meant. The point is to hopefully make new users aware that they can't assume their Lightroom knowledge will help them, and thus encourage them to consult the manual or some tutorials. It's an unfortunate fact that many coming from Lightroom think they already know everything and don't have to learn anything new, but when they fail to make head or tails of darktable they conclude that the issue is that it's trash and not that they didn't bother educating themselves - and they will often loudly proclaim this on Reddit in a rather entitled manner.

But yes, the library features could do with some improvements.


OpenCL is deprecated, not unsupported, on MacOS and may be removed at some point, but it absolutely does still work for now. If you don't have OpenCL acceleration, it's a bug.


Look into the keto diet. Fat is definitely not the main issue, sugar and other simple carbs are.


Your conclusion presupposes we buy into the "keto diet is healthy" proposition.

However, there is a preponderance of real data that fats have been demonized by the sugar industry in the past, and HGI foods (high-carb, generally) are a bigger issue.


It wasn't killed off. Support was removed from Chrome, for what appears to be rather spurious reasons, but practically everyone else are busy implementing it.


Sadly removing support from Chrome is effectively the same as killing it off. And the reason is Google wants people to use webp instead.


Not really? Chrome dropped support but Google is actually supporting the JPEG-XL rust port that Firefox is waiting on.


Friendly reminder that WebP is trash https://www.youtube.com/watch?v=w7UDJUCMTng


While I'm not the biggest fan of WebP, using generation loss as a metric wouldn't be an indicator of a real world scenario. I can't think of any actual instance where an image needs to be re-encoded, say, 10 times, let alone 100+ times.


What do you think happens to images shared and re-shared between people online?


> killed off

my guesswork is that JPEG XL will likely outlive Chrome by 100+ years


While certainly an impressive effort, it's not even close to competitive yet. As is pointed out in a comment on [1] and as can be seen from the rat piss yellow in the sky, the algorithms are very much on the naive/simple side of things.

[1] https://youtube.com/watch?v=7QymsCRNRHE


ART (Another RawTherapee) has a more Lightroom-like approach to masking that you might like better.


A (very) relevant post from 3 months ago:

Xee: A Modern XPath and XSLT Engine in Rust

https://news.ycombinator.com/item?id=43502291


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: