jakjak123

I have 100s of grave photos. Browsing by location would be way simpler

I work on a similar product, and honestly the AI parts dont really matter wrt privacy. Its uninteresting. The EXIF information is way more private and useful, but exif data is also what makes the product usable. If you strip exif, you might as well chuck all your photos in a single folder and call it a day. We also dont sell your data to anyone and we dont run analysis on your data

I concur, the slow drip feeding is adequately explained by coming from a place of war ineptitude and domestic priorities rather than a conscious strategy.

Its also a difficult problem. They need the right digger and the right crew at the right time and possibly the right weather to get the job done. Many times there will be weeks of juggling around schedules and suddenly the digging started three weeks after the road was finished

Actually started laughing seeing that

Well, Go bundles its own runtime with the executable. JS has to work on probably millions of different combinations of versioned runtimes.

Why is it gtk3? No Gtk4?

"Kill orphaned child process"

Yeah, i was thinking more about why it looks like it works so fast when you browse your photo library

It pre processes your photo library while charging

Yeah, its not much I agree. But it is an agreement the company can wave that they at least have future buyers for their non-existing power generators if they were to build them!

I dno, but delete works most places I have worked, just because it saves money

A good PM will understand that to get to C, we need to build and support A + B before we can build C, and plan for this. Like, if we built B to be a terrible barely working mess, they understand that this will make C basically worthless. But in my experience, this ability is surprisingly rare.

Well, sometimes they want fewer bugs!