We changed to jemalloc first on a jvm service which we could never get to run in its kube memory limit. with jemalloc its been dead stable for years, and we made it the default for all jvm services
NGL, its a little annoying and disheartening that many can now partially build with an LLM tool what I spent so many years learning. It does not cover all cases, but there is an element of this.
Yeah, I have stopped basically all consumption except from youtube, which itself also has a tendency to expand to fill all available time. I dont use shorts that much, but there is just much good content being released as well.
yeah, now that you mention it i remember a similar issue for us on postgres where we transitioned tables without primary key to being primary key serial.
we have 7 coworkers we have been trying to re-instate for nearly 4 months now. All using the same google workspace sso, so there really was no special reason to ban them...
its not a drop in. There is no reasonable way of replacing a huge existing cassandra cluster with scylladb. You have to transition as it was a new database.
its actually quite doable. any cosmic rays will not be present in two pictures in a row. any permanent damage will be exactly the same in all pictures.
Did you read the post? Nothing is hijacked, but its a trick where they render the normal button in a ui element for secret data, which is blanked by the system on screenshot, revealing the logo underneath. Its a reasonable feature, so its hard for apple to control it better or remove this.
Especially writing code has rarely been very hard the past 10 years. It was always reading existing code and understanding its implications that was the hard part, and understanding how to adapt new requirements together with the existing ones.