How do you know it was written by a human? All we can do is to believe the author.
2,452 karma · joined August 20, 2013
I honestly think that all phones and even professional cameras should replace JPG with WEBP, we will have like 30% smaller photos.
The DNG format (for raw photos) allows JPEG XL compression (it used to allow only JPEG in the past). I wish some country made it mandatory for cameras to let user take photos in DNG (just like USB-C is mandatory in the EU).
I am happy that HEIC from Apple did not take off (as it was proprietary, protected by patents).
Github did take down this https://github.com/spooknik/Photopea-Appimage and other repos in the past, but now, I feel like I talk to a robot. I am happy to hear that they have real employee! :D
Honestly, I was a hoping that giving attention to this problem here at HN might lead to someone from Github actually noticing my problem and looking into it.
I think I will try solving it with a lawyer. But it would be really cool if I could spend my days writing code instead of dealing with lawyers and stuff.
I wanted to discuss the behaviour of Github without giving these "projects" even more attention.
1) About 30% of my original code is open-source as JS libraries: they end with ".js"-https://github.com/photopea?tab=repositories
2) WASM is not faster than Javascript "by default". Both can be fast or slow depending on how you write it. I don't think having everything in WASM would make Photopea significantly faster. Also, Photopea uses many libraries as WASM (WEBP decoding, ZSTD decoding, JPG decoding, Harfbuzz, ... JXL / AVIF encoding)
3) I never used any Framework, but if it is just a bunch of a JS code, I think I managed to write an equally good JS code for the UI over the past 14 years.
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...
- the software would run only on your own server and clients will access it remotely through an interface
- you will sell the software together with the hardware and a proprietary operating system, which does not allow anyone to get the ones and zeros of your software
So, the only way to prevent GTA6 being "decompiled" and "forked" by AI models is to run it remotely (with a video interface), or sell it together with a proprietary console :D
In this case, it was a clear copy-paste of my code, whith the variable names changed by the AI.
Thank you all for your support! Many repositories like this one exist on GitHub, I tried to report in in the past, but I was completely ignored by Github / Microsoft. I feel pretty powerless here :( I tried to call them out publicly - https://x.com/photopeacom/status/2106877355738140875
This "PhotoSuite" thing got me a bit angry, since the author presented it as an original work, when I clearly see that such a project can be made from my "pp.js" file in two hours using Claude. Also, I believe that their README.md did not mention Photopea before I wrote my first comment there.
Thousands of people shared "PhotoSuite" on social media and nobody minded the fact that they don't know who the creator is. The creator is still offering it on their website as their original work: https://www.photosuite.app/
We live in interesting times. AI can (or will be able to) de-obfuscate every bit of code that was ever published, convert binaries to readable C++ and so on. So, in theory, AI models will train on the source code that we consider "closed-source" now, and will be able to recreate this software if asked. But it wouldn't be possible if a real person did not spend thousands of hours of their life to write that software years sooner.
I have always been excided to see people make AI create something new, what didn't exist before. But so far, I mostly saw only "approximations" of expensive software, when AI tries to recreate each feature and each button according to what it thinks it should do, or "forks", when AI takes the full code of something and tries to "bend" it to hide the similarity with the original work.
And 54 lines of javascript: https://jsfiddle.net/06L845jx/127/
Original discussion: https://www.reddit.com/r/javascript/comments/9nihtw/a_simple...
When I run my website in any browser on iOS (iPad with 16 GB of RAM), my website can get 1.88 GB of RAM.
This much RAM might be needed only for a few seconds (computing a visual effect). A user is "focused" at just one app at a time. If a user uses my tool for hours, I think it makes sense to give them all the resources (CPU, GPU, RAM, ...)
This is the reason I never made a mobile version and all mobile users use it in a browser.
The biggest problem (bug) with this approach is that iOS limits the RAM usage to 2 GB per website. I have to tell many of my users to ditch their $1000 iPads and get a used $150 Macbook for better experience.
I think Apple does it on purpose https://bugs.webkit.org/show_bug.cgi?id=268816
Because of it, for the past couple of years, all new iPhones and almost all Android phones (mostly Samsungs) already contain a JPEG XL encoder / decoder (to generate these DNGs).
I think that you can learn music theory (to play an instrument or to compose music e.g. in a "piano roll tool" / MIDI editor) much faster if you skip the classic notation. And I think that it is even better to learn the notation AFTER you understand the music theory.
I even made my own guide to music :D https://www.jampea.com/learn
I wish I could use something better :D but it must be implemented in Javascript to run inside a browser, and the library should not be too large (mine is about 8 kB ZIPped). I would love to switch to ZSTD once someone implements a compressor in Javascript that is under 40 - 60 kB. Or do you think that bzip3 could be re-implemented easily in JS using some AI?
I really admire you for being so smart at such a young age :) I wish you best of luck in your scientific career! I visited Warsaw this year, but I am not sure if that is where you are from :D
Recently, I wrote https://www.jampea.com/learn , which is the music theory for "technical people". I believe it is the fastest way to get to understand the theory behind music (will take you 2 to 5 hours in total, 10% will be reading and 90% will be thinking about what you just read).