I believe one of the major distro lines (redhat or debian, I forget which) uses systemd-cron, where cron is just a thin wrapper around systemd. You get more power from writing the unit files directly, but if all you ever need is a simple cron job, you have the old interface still available.
There's a reason I don't write mobile apps, and it's all the flaming hoops you have to jump through: both in the build system and from the random whims of reviewers.
Happens all the time with long term dev branches, which tend to arise when the PR review process is such a bottleneck that work piles up. Anything cherry-picked out of those branches tends to run into similar conflicts. ReRe is pretty handy in those circumstances.
The passenger is no more liable than they would be if it were a human driving. No one's suggesting anything even like that. MJ Rathbun is more like someone gave the taxi explicit instructions to run people over.
The big attacks of today are spread across several package ecosystems: TrapDoor and Shai-Hulud have been hitting npm, pypi, composer, and crates with the same malware.
I'm not saying wedging doorstops under the fire doors is a good thing, I'm just saying look at the situation that's making people put the doorstops there. Or something, it's not a great analogy. I'm just saying that shaming the user belongs with obscurity in the list of security mechanisms that don't work out in practice.
A tool that pushes people into permissions fatigue is in fact the proper recipient of the blame. The tool in question here is the entire system though, including the OS with insufficient permission boundaries in userspace, not just the agent
I just delegated to AI like 99% of the work in a task that was mostly grunt work: writing tests. It wrote the tests, ran them, and when they found bugs, I had it fix them. The authority might have been delegated, but “agent” is definitely the right word for the amount of initiative I let it have.
“Clanker” is a tad cutesy, but fitting regardless. It brings to mind an archaic and clumsy whirring automaton with no reasoning or awareness of its context, an apt metaphor for slop submissions entirely generated neither by or for humans.
Excessively verbose syntax to express concepts is something I can let an LLM paper over, but a language that does not even function properly without the ceremony is still a non-starter. I want to refactor chains of operations without having to check for errors myself after each step, and I want that with or without an LLM.
The state of Hawaii was the most recent to be expropriated from its natives at the behest of corporate landlords, so they're probably a bit raw about it.
The mac started out without using extensions at all, the type was embedded in the metadata. That's still possible now, but it's largely derived from extensions first. I believe Finder shows all extensions by default. It certainly does in details mode.
I've worked for a few Fortune 50 companies, and they all had "shadow IT" that would crank out scripts and tools with no official sanction to work around the cumbersomeness of the official tools (or sometimes their complete lack). That's what corporate hackers are.
Ternary was made non-associative in 8.0, so it requires parentheses. It will become right-associative in 9.0. But there’s not much use case left for nested ternaries in PHP since the `match` operator was added in 8.0.
Ah I misremembered one thing, nothing broke because it wasn’t even an existing domain when they used it. That was a different Microsoft domain I was thinking of.
Any Pi extensions you'd specifically recommend? I'm just starting out with Pi, but I've had mixed results with extensions. I'm using Pi with gemma4 26b locally, so anything that's friendly to small local models would be appreciated. I think the only extension I'm using right now is pi-total-recall.
You can write entirely imperative OO code in Scheme, it just has syntax that's weirder than you're used to. Not everything has to be functional abstractions, syntax macros, or twisty mazes of call/cc. If SICP is too abstruse, give HTDP a try, but if you know other languages, you already know most of scheme.
Whether Kildall actually blew IBM off at that meeting or not, what was definitely the case was that CP/M didn't have a 16-bit version ready to meet IBM's schedule, and that's what ultimately took them out of the running.
It's hard to remember many details from almost 20 years ago, I just remember coming across it in email spools while writing anti-spam analysis scripts. Only mention I can find nowadays is https://www.experts-exchange.com/questions/22812691/What-is-....