I wonder whether alternative solutions were discussed: like Google retaining integration but breaking off Maps division into it’s own entity that has to use same API’s as everyone else and use the same integration points. Would’ve been more user-friendly thing to do.
funny, on the same day we get a headline about Germany energy prices dipping into negatives mainly due to renewables… hmmm
the most dangerous assumption either camp is making is that AI is and end-solution. Whre 8n fact it’s just a tool. Like invented steam machines they can do a lot more than humans can but they are only ever useful as tools that humans use. Same here AI can have value as a tool to digest large chunks of data and produce some form of analysis providing humans with “another datapoint” but it’s ultimately up to humans to make the decision based on available data.
I’m not convinced what you run into is a specific podman issue. It’s a resource issue and configuration issue likely. “vanila” podman with proper rootless containers will run as much workload as machine can handle from my experience. My company costomers seem to be running production workloads with it just fine.
Oh wait, by rootless container you really meant running podman rootless? still don’t see an issue though. What specifically are you doing? I mean, what’s the configuration and what’s the workload?
we can only hope fb implodes sooner rather than later. I personally know multiple people working there who are very decent human beings who need to pay bills. I just hope their current trajectory will force employee action and paralyze fb long enough to hurt. Unlike other places it’s not so simple to just hire a load of IT professionals and have any meaningful results short term, esp. if they have not been ramped up to speed by their colleagues. So it’s not impossible, bowever tolerance threshold is kind of high for any action to take place. Wads of cash, unpaid mortgages and all. Employees of big tech are truly living in gold cages…