... to add to your point, then take companies like Google who rely heavily on ML to improve the quality of the photos further and the distance between "RAW data off sensor" and "the best Samsung/Apple/Google can generate" is a HUGE gap.
Nothing to do with the project, but I read through it, so...
1. It's built natively on Jetty - very tight integration, not just some libs running in a Jetty container.
2. Web is inherently Request/Response - all of this can be handled with dramatically less resource requirements using Virtual Threads. Web is sort of the absolutely-best-use-case for Virtual Threads where as a Game Engine would be the opposite of that (one critical rendering thread and MAYBE a few extra long-lived threads for processing physics, audio, etc.)
3. I haven't tried debugging a Loom project but it's been in incubation for just under 100 years so I have to imagine this has been figured out.
I used an approach similar to Peter's here to both an old streaming parsing library as well as a GUI (event handling) library -- effectively, re-use the same instance of the event shell with new data every time an event fired and copy the data out if you need to retain it for a long-lived operation or persistence, otherwise calculate and move on... the reduction in object creation overhead was significant and performance increase was around +30% for doing this in the two individual use-cases... BUT, the API was like a loaded gun pointed at your face.
I knew what I was doing (with it) so it wasn't a problem, but if I over open sourced the API and provided it as a library I would envision a large portion of the population trying to handle the events in a multi-threaded context or throwing them into a List only to find the values changing on them during use (while the parser was still running on another thread).
Performance was so tempting, but usability-face-shot-gun was the greater evil.
Reusing your objects can be confusing for other developers. You need to be careful with anything exposed via an API, however internally you can me more optimised.
I would look at sys admin type jobs at law firms, small medical practices and other places that need a “tech guy” but don’t need to hire a full time developer.
This won't be successful - ETSY is a publicly traded company, unless corrective action can replace the loss revenue from ads/punishing duplication/aliexpress - it's not going anywhere.
This is exactly what happened to eBay for anyone that remembers when it was garage-sale mania, then it became publicly traded and effectively became Target.com with < 1% of personal things sprinkled in.
