Not "on Windows". In PowerShell 5. PowerShell core removed the curl alias 9 years ago.
But PowerShell 5.1 is still the one that ships with Windows.
Readit Newsfourthark commented on Copy-Item is slower than File Explorer til.andrew-quinn.me/posts... · Posted by u/hiAndrewQuinn
fourthark commented on `satisfies` is my favorite TypeScript keyword (2024) sjer.red/blog/2024-12-21/... · Posted by u/surprisetalk
TypeScript codebases I've seen generally seem to have the widest demonstration of skill gap versus other languages I use.
For example, I don't ever see anyone using `dynamic` or `object` in C#, but I will often see less skilled developers using `any` and `// @ts-ignore` in TypeScript at every possible opportunity even if it's making their development experience categorically worse.
For these developers, the `type` keyword is totally unknown. They don't know how to make a type, or what `Omit` is, or how to extend a type. Hell, they usually don't even know what a union is. Or generics.
I sometimes think that in trying to just be a superset of JavaScript, and it being constantly advertised as so, TypeScript does not/did not get taken seriously enough as a standalone language because it's far too simple to just slot sloppy JavaScript into TypeScript. TypeScript seems a lot better now of having a more sane tsconfig.json, but it still isn't strict enough by default.
This is a strong contrast with other languages that compile to JavaScript, like https://rescript-lang.org/ which has an example of pattern matching right there on the home page.
Which brings me onto another aspect I don't really like about TypeScript; it's constantly own-goaling itself because of it's "we don't add anything except syntax and types" philosophy. I don't think TypeScript will ever get pattern matching as a result, which is absurd, because it has unions.
It will get pattern matching when JS does. Not certain yet but in progress.
You actually can protect against it, by tracking context entering/leaving the LLM, as long as its wrapped in a MCP gateway with trifecta blocker.
We've implemented this in open.edison.watch
True, you have to add guardrails outside the LLM.
Very tricky, though. I’d be curious to hear your response to simonw’s opinion on this.
I see an enormous threat here, I think you're just scratching the surface.
You have a customer facing LLM that has access to sensitive information.
You have an AI agent that can write and execute code.
Just image what you could do if you can bypass their safety mechanisms! Protecting LLMs from "social engineering" is going to be an important part of cybersecurity.
Yes that’s the point, you can’t protect against that, so you shouldn’t construct the “lethal trifecta”
fourthark commented on Open-source communications by bouncing signals off the Moon open.space/... · Posted by u/fortran77
The moon is so useful.
We probably wouldn’t be here without it!
Deleted Comment
fourthark commented on How I use every Claude Code feature blog.sshh.io/p/how-i-use-... · Posted by u/sshh12
I've found the latency of /compact makes it unusable. Perhaps this is just the result of my waiting until I have 0% context remaining.
Fun fact, a large chunk of context is reserved for compaction. When you are shown that you have "0% context remaining," it's actually like 30% remaining that's reserved for compaction.
And yet, for some reason I feel like 50% of the time, compaction fails because it runs out of context or hits (non-rate) API limits.
Weirdly, I’ve found that when that happens I can close Claude and then run `claude --continue` and now it has room to compact. Makes no sense.
But I have no idea what state it will be in after compact, so it’s better to ask it to write a complete and thorough report including what source files to read. Lot more work but better than going off the rails.
> It’s a lot easier than working with actual people because you don’t have to worry about offending or discouraging them
But you have to worry much more about confusing LLMs by introducing contradictory ideas or talking about too many things at once.
They will not call you out and they will not recover.
You don’t need to reboot your coworkers.
I couldn't agree more. And using Plan mode was a major breakthrough for me. Speaking of Plan Mode...
I was previously using it repeatedly in sessions (and was getting great results). The most recent major release introduced this bug where it keeps referring back to the first plan you made in a session even when you're planning something else (https://github.com/anthropics/claude-code/issues/12505).
I find this bug incredibly confusing. Am I using Plan Mode in a really strange way? Because for me this is a showstopper bug–my core workflow is broken. I assume I'm using Claude Code abnormally otherwise this bug would be a bigger issue.
So you either need to be very explicit about starting a NEW plan if you want to do more than one plan in a session, or close and start a new session between plans.
Hopefully this new feature will get less buggy. Previously the plan was only in context and not written to disk.