I don't know what Cold Harbor means in a Meta context, but its interesting that its named after the battle that exemplified Grant's strategy of attrition during the American Civil War. I suspect it means waves of engineers ground down against the defenses of OpenAI/Anthropic in the hopes of eventually finding a crack. Might be best to get out while you can.
> I don't know what Cold Harbor means in a Meta context
Cold Harbor is a reference to the TV show Severance.
Without going into any real spoilers it was the code name of a data classification project so mysterious that the people working on it weren't allowed to know what they were working on (and yes, the project in the show was probably named after the battle in the Civil War).
The Meta connection is that there are some humorous parallels between that project and a project involving people tagging data to train technology to replace themselves, and just the overall creepy dystopian vibe of both the fictional and real-world companies (and founders) involved.
I think we are also going to see a lot of new software that is less hungry on compute and RAM than before. Probably first with games not requiring new hardware anymore.
Because the consumers won't upgrade to new hardware as fast as before. People who buy their first gaming PC in 2027 might even get a lower spec in average than people who bought in 2025. So new games might require even lower hardware specs than before, to sell enough copies.
This is a wishful fantasy. Vibe coded applications like ChatGPT desktop and Claude Code routinely take 1~2GB of RAM to display <1kb of text. There is zero initiative to make better software, the software industry is just saying "fuck you" to the rest of the world until the bubble pops.
Sure, that's why I think it will start with games. You don't buy a game if you can't (properly) play it. Either you get a new gaming PC, or stop buying new games and keep playing old ones.
Doesn't seem to be mentioned in the page but if you're talking about request caching there's libraries like PlugHTTPCache or RequestCache.
Otherwise I usually use Nebulex (annotations are nice for Ecto queries) with ETS as it's faster than with Redis (if you don't care about losing the cache on deployment).