That Time I Recreated Photoshop in C++

&gt; &quot;It followed a set of five rules to benefit the end user: no installers, no archives, no registry keys, no additional runtimes and a single executable file.&quot;<p>Reading this sentence made me feel warm and happy. I get why the registry exists and things work the way they do today around the Windows software ecosystem but... damn, I really miss the days when most desktop software was more like this. These days I try to use portable installs whenever they&#x27;re available, I just wish it was more common. The time, inconvenience and uncertainty I&#x27;ll be able to fully restore all my preferences makes me actively avoid reinstalling Windows.

Photoshop has a million features though, a couple of image filters doesn&#x27;t really count as recreating.

Let&#x27;s get a direct link to this beauty in place:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;f055&#x2F;fedit-image-editor" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;f055&#x2F;fedit-image-editor</a>

&gt; But I didn’t promote it. A few months later, I landed a C++ job. So in the end all that effort paid off.<p>It&#x27;s interesting how instinctively we know our hard work deserves to be paid off, but it&#x27;s a shame how often open source developers put hard work into code that never really gets paid off, especially when it&#x27;s widely used in production. I guess this explains why so often they look for reputation credits, or why NPM added the &quot;maybe you should donate to the authors of these libs&quot; feature, or why GitHub built in Patreon. There&#x27;s got to be a better model than what we have now, that doesn&#x27;t take advantage of naive but hard working young thinkers.

There was a project called &quot;pixel32&quot; and later &quot;Pixel Studio Pro&quot; in the early 2000s. It looked really nice and was sold as early access. But became vaporware, people that paid became really pissed and the guy creating it turned from hero to villain quickly.<p><a href="https:&#x2F;&#x2F;discuss.haiku-os.org&#x2F;t&#x2F;pixel-studio-pro-in-past-called-pixel32-image-editor&#x2F;10979" rel="nofollow">https:&#x2F;&#x2F;discuss.haiku-os.org&#x2F;t&#x2F;pixel-studio-pro-in-past-call...</a>

Author of this article said he finished at Warsaw University of Technology - it was always considered to be one of the better ones here.<p>That being said, what also strikes me is how different the thesis were back in times. I did mine recently in another university of technology in some bigger city (without wanting to dox myself that much) and 90% of our engineering theses were of very subpar quality; mine included.

This is why I love Windows. There is a TON of small, open source software that serves a niche. Used to browse sourceforge.net and freshmeat (is that what it was called?) to find them!

A friend from Phonegap got acquired by Adobe a decade ago and ported Photoshop to JavaScript for entertainment purposes immediately afterwards.

The things people make and not tell the world about. Glad it’s on GitHub, this is so impressive.

Photoshop is a stretch.. that&#x27;s more like MS paint in terms of feature parity.

In my experience, when developing software the hard part is implementing the actual logic, not the UI.<p>In this case, replicating Photoshops UI seemed to be the hardest. Maybe using something like MFC, Qt, C++ Builder instead of straight Win API would have been easier.<p>I remember a long time ago when I was in high-school and tried to implement a paint program under DOS, that had windows using Borland C++ and BGI graphics library. How hard should it be to implement windows, buttons and dialogs, I thought? After all, with the power of OOP and C++, every problem is easy to solve, I thought.

Did it crash every 30 minutes?<p>If not, how much are you selling it for?

&quot;Straight from my previous project named Fiew I added a massive image library viewer. It really could quickly and easily scroll through massive amounts of pictures.&quot;<p>Which is now infuriatingly lacking in the entire domain of image editors. Thumbnail browsers used to be an expected feature of image editors, even shareware ones. Now? Fat chance. Good luck even finding a stand-alone one.<p>Recently one called FlowVision surfaced for Mac, and it&#x27;s pretty much the lightweight browser that many of us have been looking for for years. It has some rough spots, but the developer is responsive to issues. <a href="https:&#x2F;&#x2F;github.com&#x2F;netdcy&#x2F;FlowVision" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;netdcy&#x2F;FlowVision</a>

Slick. Runs pretty well under Wine!

It looks like you could have sold licenses to this or gone the startup route. Might have been slower and less glamorous than the gig you wound up getting, though.<p>The UX looks simple and reasonable. Frankly better than Gimp.<p>Really cool work!

no you didn&#x27;t

oh you did?

umm, what&#x27;s wrong with: <a href="https:&#x2F;&#x2F;affinity.serif.com&#x2F;en-us&#x2F;" rel="nofollow">https:&#x2F;&#x2F;affinity.serif.com&#x2F;en-us&#x2F;</a> ? Adobe is out-of-everything for decades..