I just use fallocate to create a 1GB or 2GB file, depending on the total storage size. It has saved me twice now. I had a nasty issue with a docker container log quickly filling up the 1GB space before I could even identify the problem, causing the shell to break down and commands to fail. After that, I started creating a 2GB file.
Interesting! I did `fallocate -l 1G myfile` - very fast. Its all zeros but probably won't be compressed by the filesystem since its created with the fallocate() system call.
The pricing page for Claude literally says "More usage" for the $17/month pro plan. Doesn't really quantify anything. The usage is whatever they feel like it should be.
And then the very expensive plan says "Choose 5x or 20x more usage than Pro". It's all arbitrary.
Even if you try to get them to not, they will still overcomment the code. Or at least overcomment it from the perspective of a human. From the perspective of the LLM, I suspect the comments are necessary for it to be able to get the code output correct.
It's also a discoverability tool. If the code has good docstrings and decent naming for functions/variables it's a lot easier for the LLM to find the correct places to edit.
So we're getting a new console just to play AI-upscaled PS4 and PS5 "remasters"... and I suspect it’ll probably come without any support for physical media. The PS5 will be my last console. There's no point anymore.
Apple wants to make sure they get a 30% cut if you spend money on anything within their ecosystem — that's all they really care about.
There are several reports of people having their entire accounts banned, effectively losing access to everything they paid for. And it's basically impossible to get your account back.
reply