I'd treat this as completely new, far from complete software heavily inspired by the Adobe Suite, rather than a "port".
But maybe folks who use workflows that don't involve RAW photos have better luck.
I'd treat this as completely new, far from complete software heavily inspired by the Adobe Suite, rather than a "port".
But maybe folks who use workflows that don't involve RAW photos have better luck.
Rome wasn't built in a day, nor Adobe destroyed in a single git push. But they both shall fall.
1. LLMs
2. an executive team that hates your customers. this problem with company culture goes back at least 13 years: https://fstoppers.com/video/adobes-ceo-deftly-dodges-questio...
Unfortunately any benefit from #1 is neutralized by #2
Seriously, you have no idea the kind of goodwill you've squandered, and the kind of resentment you've created. I expect it will bite your company squarely in the ass.
Revenue over the last ten years
August 31, 2026 — $6.760B May 31, 2026 — $6.618B February 28, 2026 — $6.398B November 30, 2025 — $6.194B
August 31, 2025 — $5.988B May 31, 2025 — $5.873B February 28, 2025 — $5.714B November 30, 2024 — $5.606B
August 31, 2024 — $5.408B May 31, 2024 — $5.309B February 29, 2024 — $5.182B November 30, 2023 — $5.048B
August 31, 2023 — $4.890B May 31, 2023 — $4.816B February 28, 2023 — $4.655B November 30, 2022 — $4.525B
August 31, 2022 — $4.433B May 31, 2022 — $4.386B February 28, 2022 — $4.262B November 30, 2021 — $4.110B
August 31, 2021 — $3.935B May 31, 2021 — $3.835B February 28, 2021 — $3.905B November 30, 2020 — $3.424B
August 31, 2020 — $3.225B May 31, 2020 — $3.128B February 29, 2020 — $3.091B November 30, 2019 — $2.992B
August 31, 2019 — $2.834B May 31, 2019 — $2.744B February 28, 2019 — $2.601B November 30, 2018 — $2.465B
August 31, 2018 — $2.291B May 31, 2018 — $2.195B February 28, 2018 — $2.079B November 30, 2017 — ~$2.008B
August 31, 2017 — ~$1.844B May 31, 2017 — ~$1.773B February 28, 2017 — ~$1.682B November 30, 2016 — ~$1.611B
Besides, you're on HN, we don't value revenue here because we're idiots. But even the market agrees. Stock down 64% from peak.
Tootsie Roll Industries heats sugar and has nearly triple your P/E.
And on top of that, you need a bunch of different files from different sensors to test with. Canon, sony, apple, fuji, nikon, olympus, etc. -- if you're building a truly general application, that's a concern.
Or if you're like me and you shoot fuji, you just build a fuji raw parser and call it good. The "TAM of 1" world of software development...
"Hey ChatGPT, what would the sufficiently smart compiler argument look like in the LLM era?"
Oh the times we live in.
I also let it build one btw: https://egeozcan.github.io/ketchup/ (not a PS clone, more amateur painting oriented)
For lopsy, the biggest issue I ran into was combinatorial bugs: certain sequences of tools and actions would cause a bug to occur that wasn't obvious from isolated tool testing. I solved it by having Claude generate complete projects, full documents with novel concepts chosen randomly, built in the browser with playwright. This continues to expose so much more than individual unit/tool tests, and I have an automated loop that addresses them. (And a bonus from that: I use the outputs to make tutorials to show what the tool can do).
That tracks.
So it's the Omarchy of Adobe-like software?