veroxii

I mean you can say the same for spinning magnetic platters. “The more bits you’re trying to squeeze into a fixed size HDD the less robust it is.”

I’m not saying these guys can do it, but dismissing higher densities of storage out of hand seems a bit glib considering the last 60 years of progress and innovation.

Invoice.doc

Bloody hell mate. A little bit of warning before so casually dropping Java Spring out there.

Where my turbo vision peeps at?

I mean reason 31 could be anything. CPU 3 could be feeling a little tired, be pranking you, or just not be the brightest of the CPUs.

Should be SunOS

Straight to production!

“fully functional”

As a SaaS founder I’m now wondering if this actually works. Will have to talk to the front-end devs on Monday.

It’s because of joysticks and typical flight controls. Pushing forward goes down and pulling backwards is “pulling up”.

Joysticks rules for a long time before the mouse came out. Home computers came standard with joystick ports.

Keyboard controls followed this convention and when mouse controls came into FPS games this was the first instinct… Moving the mouse “forward” looks down.

This is extremely cool.

Because of the federated nature of Lemmy many instances might be scanning the same images. I wonder if there might be some way to pool resources that if one instance has already scanned an image some hash of it can be used to identify it and the whole AI model doesn’t need to be rerun.

Still the issue of how do you trust the cache but maybe there’s some way for a trusted entity to maintain this list?