I wouldn’t use Beehaw as the standard, they are way too strict on their moderation in many’s opinion.
I’ve used them for extension, as it allows you to attach a second, regular USB cable to it.
I may sound cynical, but protecting jobs is hardly ever a good argument for blocking new technology in my opinion. You’re at best delaying the inevitable. Society is more likely better off learning early how to use the workforce for new and better tasks. Of course, this needs a healthy and working society, so I of course understand the individual concerns.
Safety on the other hand is a very valid reason to hold back new technology.
Man I can’t wait to get 100% out of gmail.
AMD and Nvidia are basically on par for now, especially so for RTX 4090 vs 7900XTX.
These are day-1 results and must be expected to change significantly through the next six months of driver and game updates.
Upscaling was not tested.
I literally have nothing to hide, but conveniently have just reset my phone whenever I’m flying into the US.
This bug has created havocs for me. We had a “last synchronized” time stamp persisted to a DB so that the system was able to robustly deal with server restarts / bootstrapping on new environments.
The synchronization was used to continuously fetch critical incident and visualize them on a map. The data came through a third party api that broke down if we asked for too much data at a time, so we had to reason about when we fetched data last time, and only ask for new updates since then.
Each time the synchronization ran, it would persist an updated time stamp to the DB.
Of course this routine ran just as the server jumped several months into the feature for a few minutes. After this, the last run time stamp was now some time next year. Subsequent runs of the synchronization routine never found any updates as the date range it asked for didn’t really make sense.
It just ran successfully without finding any new issues. We were quite happy about it. It took months before we figured out we actually had a mayor discrepancy in our visualization map.
We had plenty of unit tests, integration tests, and system tests. We just didn’t think of having one that checked whether the server had time traveled to the future or not.
I’ve always found this classic the best measurement:
When was cryptocurrency meant to be untraceable? It literally had the complete ledger out in the public.
I had better luck after I started searching for specific communities no matter which instance they were on, and blocking communities and bots.
Okay but could you not cross post to 10 communities or something? I hoped to leave that behind at Reddit.
I just wouldn’t feel ok knowing that some poor camel was forced to haul my new dishwasher through Egypt.