

Might as well bump it to 64 GB and an LLM chip since in 5 years’ time people might like Copilot & Friends spying a bit less on them.


Might as well bump it to 64 GB and an LLM chip since in 5 years’ time people might like Copilot & Friends spying a bit less on them.


What do you mean it’s not a review?
If a congressional comitee and a few invitees (such as POTUS) reviewing golf clubs together in a courtroom isn’t a judicial review, I don’t know what is.


This is where a man page comes in but alas, but some (perhaps even most) of them are fucking horrible. The core incantation is either too dumbed-down or (more often) too long-winded.
Some good ones I can praise are netcat, ghostscript and 7z. Special praise goes to the Library Funtions Manual entries like signal and exit.
Bad ones ones in my book are vim (too short), ffmpeg (a simple reordering of sections would make it quite a bit better, like moving the less common flags lower down the page) and git starts of strong but ends up being way too detailed and unstructured.
I could go listing examples for days, so I might as well stop now.


Well, duh. Do you think Mother Nature won’t “hold” new generations “accountable” once ours destroy the planet with fossil fuels?


If you want specific tasks for designers, here are some:
All of these require intensive input from designers and are a net-positive improvement, as opposed to the 4th redesign of the exact same scope.
Bigger is always better. For hardware.
On the other hand, less is always more for software.