I used Ente once, and it was great, but I am poor, so I just store my images locally now. Not that your service is expensive or not worth it because I think it is.
I used Ente once, and it was great, but I am poor, so I just store my images locally now. Not that your service is expensive or not worth it because I think it is.
Compare that to something like Go which includes all of that stuff out of the box—by and large everyone has just said "yep that seems to work" and stuck with the defaults.
I think the second problem is the browser still fundamentally wants to be a displayer of documents. Yes there has been continued additions of new APIs over the years that have made the SPA pattern much easier to work with, the fact of the matter is you can still save yourself about an order of magnitude of complexity if you can get away with your app being an "old school" multi-page affair.
my 2018 iPad Pro does OCR on images in Safari instantly. People only think OCR is slow because Adobe Acrobat still uses the same single-threaded OCR algo it’s had for decades now; then consider how blazing a GPU-based impl would be…
How so? I was looking for a photo of a grave I took some years ago. In Google photos I just searched for "grave" and if found 2 photos, including the one I wanted.
Without AI I would have to search all my photos. Maybe I could narrow it down by date and location but it would take a lot longer.