Vibecoding Photoshop: Time and pressure(andreklein.net) |
Vibecoding Photoshop: Time and pressure(andreklein.net) |
It was discussed here on HN yesterday and then, the anonymous person behind it removed the "Issues" section completely from their Github
https://news.ycombinator.com/item?id=49972730
https://replayweb.page/?source=https://archive.org/cors/gith...
I have a huge respect for your work on Photopea, been using it constantly since the time I completely moved to Linux a year ago. It has the best Photoshop parity yet to find! Would you ever consider to: 1. Open sourcing your work (partially or completely) under some kind of a permissive/copyleft license. 2. Rewriting some parts of the website that require performance as WASM targets. 3. Using any modern JS frameworks, e.g. Svelte.
If I may ask, if you were to do this all over again in 2024 - 2026, would you choose SSR?
Wouldn’t that screw up his whole thing? Because now you need infra to render to free users?
Can you settle an argument, perchance? Is it pronounced "Photo-P" or "Photo-pia" (as in "utopia")?
The immediate reaction is to ask whether any of these would be good enough to replace Photoshop (or Pixelmator or whatever). That's a first-order question and it's an open one --- you probably couldn't replace a real workflow with vibe Photoshop today, but I wouldn't bet against that being the case a year from now.
But the second-order questions include consideration of the people who can't use Photoshop, either because of cost or (to me, more importantly) because of lack of platform support.
In a world where 90% of the functionality of things like Photoshop and Word are replaceable with personal apps, how much does platform support matter anymore? How much do platforms matter anymore? I'm a committed macOS user and have been since the TiBook. Will I be 5 years from now? I'm deeply uncertain, but one thing I'm pretty sure of is that if I'm not a macOS user, I also won't be a Windows or Linux user.
Now, you can just prompt the 10% you need and not even have to use up your computer's resources with the rest of Photoshop. I didn't like a single one of the many Android TV video player apps. Most of them were way too big, had all kinds of features I didn't need, took a while to launch, had stupid "libraries" that you had to populate your videos into, and relied on third party lookup services to get things like movie posters and other metadata. Pre-2020 I would have just picked the least bad one and lived with it. Now, I just vibe-slopped a player app with only the features I want and nothing else.
Out of curiosity, how much did that cost?
The same applies to software: you'll describe a problem and a network of agents will write a solution faster than you can Google it, download it, install it, and start using it. It'll work with your accessibility requirements out of the box; it's UI will be in your language; the data will be stored where ever you like; and so on.
Please no. Enough with putting everyone into a box/label/profile. Have people be exposed to and interact with the multitudinal variety of the world!
Instead of having a web application with a typical frontend and backend, I have fantasized about thin UI/UX interfaces with an almost pure LLM backend. Just having one or more bots receive parsed http requests, CRUD-ing the data based on training and tool access, and responding back if necessary.
(I have a strong dislike for web development, so perhaps my fantasies are a form of escapism.)
Which is apparently impossible.
Who does Jony Ive work for now?
Sure you can do a Photoshop clone as in "Ps in 1990" if you just ask an LLM because then (and for years after) Ps itself got all this stuff wrong and people used it, professionally nevertheless.
But getting these things right requires, as-always, in-depth understanding of the theory behind it or the LLMs will gladly omit those parts.
Not least because the majority of OSS code dealing with those things gets it subtly wrong. And they've been trained on that.
A good start is btw. to ask your agent of choice to copy all theory/basics from OpenImageIO.
How do I know? I'm maintaining a closed-source, heavily LLM-assisted Rust crate that is the backbone of all image processing we do at my employer (kringers fossed it will be OSS eventually).
The amount of subtly-wrong- bites-you-eventually bugs I fixed (or had an agent fix, rather), despite tight specs and good tests, over the last 10 months, is ... noteworthy.
That said, for a lot of users it probably doesn't matter if interpolating between red and green means getting a muddy brown or that you get subtely wrong colors when you downsample and some (or quite a bit ) of aliasing when you do so more than 2× etc.
But while a lot of people want to prompt a clone of app X and an unexpected many also seem to have the patience for it: few have the background to get sth. out of that endeavour that will be genuinely useful in the end.
The CAD/parametric 3D modeling segment is another category I'm watching closely where a lot of people have the same issue w/o (yet) realizing.
And ofc, there are always exceptions where seemingly someone is behind the project who actually do know what they're doing. :)
I'll stick to gimp I guess.
What does this mean for the American economy, 80% of GDP attributed to services? Will every country have their own ecosystem like China?
What stops Canada from decoupling from US tech, and making their own software ecosystem? Considering the Europeans were already moving in this direction, can't they just recompile their own versions of software?
Is the future of software just cloud software? Advancements in local encryption like TPM?
I don't imagine that many of their customers are fans of taking unnecessary risks to save what isn't much money for most of them.
As a professional, there's no way I'd risk not using the real code. As a hobbyist, I can/have use something like Photopea.
https://github.com/scosman/freecell
So far it’s GPU accelerated (GPUI), cross platform, supports 95% of excel functions, supports charts, is about 40x faster than Numbers, and can render 240fps.
I thought I’d leave this process with a new appreciation for manual dev/details. I haven’t found that yet. I’m getting more into architecture details, writing more benchmarks, testing more. I know there are limits, but I’m still trying to find them.
It would be absolute garbage if I wasn’t already and engineer. It probably is absolute garbage in ways I don’t know because I haven’t read the code. But the app is… quite good.
Then
>can this be done” at all? (...) The mere existence of these tools is proof that it can be done.
Then
>DISCLAIMER: I obviously can’t know whether any of these projects were definitely “vibe-coded”, but it also doesn’t matter
..????
Opus et all are able to do everything needed client side
I’m forced to use Adobe’s apps because they are the golden standard at the moment but I wish with all my heart this to not be the case anymore.
Adobe fucking sucks.
Side-note to whomever attempts to build a new Photoshop: workshop better names. The ones on the article are woefully bad to the point of hilarity.
And how are they in a monopoly position? Is this about proprietary formats or something else? Genuinely interested to know about this if it wasn't just hyperbole.
Why is their throne unearned? They created and continue to maintain their software, which is, as you said, still considered the gold standard.
"An open-source, clean-room reimplementation of Adobe Photoshop in pure Rust".
They also have: VectorCraft Vector illustration; FilmCraft Video editing, color and sound; LightCraft Photo library and raw development; PrintCraft Reading, organizing and protecting PDF; EffectCraft Motion graphics and visual effects; DesignCraft Page layout and publishing
I've said it in other venues, but we're reaching a point where using someone else's software is like chewing someone else's gum.
If I have magic box that can give me anything, I'm not going to ask for tools and materials to build a house, I'm gonna ask for a house.
For now, while we are still riding this wonderful subsidized AI gravytrain, but how much will it cost in tokens/$$$ next year when investors finally want a return on their investment? Or if the AI bubble pops? I doubt running 7B models locally will suffice, even at the rate of improvement we are seeing.
For me, I just want to easily organize some folders, cull stuff, throw the culls into a marked directory, and process them to JPEG with some lighting adjustments since I shoot raw. Lightroom honestly is painful to use. I don't think gimp fills my needs since its more like photoshop. I'm happy to look at something else though!
But if I'm vibe-coding an app for myself, I only want it to what I want it to do. One product for one user.
SSR only really makes sense when you either want to optimize for fast page loads, or do PHP-style conditional rendering or whatever