I've had similar problems but no amount of tweaking vm and vfs cache settings helped. Swap or not, both 32gb and 128gb of ram. Manually reclaiming memory would un-lock the system (/sys/fs/cgroup/memory.reclaim).
I don't think it is macabre at all. "Hang" just means suspended. A ball on a string is hanging instead of falling. Laundry can be hung out to dry. It's about something that would normally move that is not doing so. Also see "hung jury".
My understanding is this is for excess PV capacity. But I think they should address this! Their plan is to heat deep inside a big pile of dirt using resistive heating elements and then pump the heat out in pipes. Maybe it's hard or expensive to add solar heating into the system? But why couldn't they pump it in? Maybe they don't have extra space because the dirt mound is covered in PV panels.
The article is about accessing a service (nostr) through a hosted web app. The domain or server that is hosting the app could be compromised and serve a bad app.
Posts on nostr use a key pair so when you see a post from foo you know it's the same foo you knew from last week. Also, posts are shared to and stored on multiple independent servers (called relays).
A compromised app could serve you fake posts or censor stuff.
Google is famously a monorepo and is basically the gold standard of CI/CD.
What does happen is APIs are constantly upgraded and rewritten and deprecated. Eventually projects using the deprecated APIs need to be upgraded or dropped. I don't really understand why developers LOVE to deprecate shit that has users but it's a fact of life.
Second hand info about Google only so take it with a grain of salt.
Simple: you don't get promoted for maintaining legacy stuff. You do get promoted for providing something new that people adopt.
As such, developing a new API gets more brownie points than rebuilding a service that does a better job of providing an existing API.
To be more charitable, having learned lessons from an existing API, a new one might incorporate those lessons learned and be able to do a better job serving various needs. At some point, it stops making sense to support older versions of an API as multiple versions with multiple sets of documentation can be really confusing.
I'm personally cynical enough to believe more in the less charitable version, but it's not impossible.
I agree this is an overriding incentive that hurts customers & companies. I don't think there's an easy fix. Designing & creating new products require more relevant capabilities from employees for promotions then maintaining legacy code.
