It's as frugal as your harness makes it. It's just a bunch of tools and a description of how to use them. Most mature harnesses do some kind of tool search and/or progressive disclosure. Many harnesses have some smarts to page out overwhelming results to a file so a model can grep/jq them easily. Some harnesses expose tool schema to models so their results can be directly transformed or even chained in [code mode](https://blog.cloudflare.com/code-mode/).
Copilot will prompt you before accessing untrusted URLs. It seems a crux of the vulnerability that the user didn't need to consent before hitting a url that was effectively an open redirect.
For the same reason government in general (e.g. the US military) isn't funded by one big GoFundMe. The marginal value any individual actor gains from their investment in public research or services is almost zero. It only works when it's prescriptive on a large scale. See: the tragedy of the commons.
Crowdstrike could have deployed the same broken code in their Linux or macOS agents. Nothing much for Windows to do if a kernel driver is segfaulting (when disabling it could be dangerous for users.)
That should work fine in the vscode debugger, you just want to make sure that the transpiler you're using is generating sourcemaps. Generally they do by default. If you have issues, open a github issue and I'll fix it :)
In the VS Code JS debugger, there's an option to "exclude caller" on a call frame that which prevents stacks with the given caller from pausing at a location. As mentioned elsewhere, browser devtools have something similar with "Never pause here." Do you think there's more than tools can do to make your process easier?
I maintain the vscode debugger and found both the article and your comment interesting--there's a large overlap between "programs with anti-debugger techniques" and "programs that are hard to debug."
Because your example is a breaking change, and breaking changes are hard to make in a runtime that needs to reasonably support two decades worth of web content.
For example, if you have a `binarySearch` function that returns -1 if an element isn't found, a developer might do something. `const result = arr[index]; if (result !== undefined) { ... }`. This would then start returning the last element instead of undefined at that index.
As I understand the blog post, the difficult (and buggy) part is not the addition of latency, but calculating how much latency to add and where to add it. I'm not sure how tc would help much here, and actually don't see anything to indicate they weren't using tc already.
I made the switch to a projector a couple years ago and advocate highly for them. The screen can disappear when not in use, and they're "dumb by default". New LED projectors have bulbs rated to last 10k hours or more.
This is a sad day for me. The obscurity of git.io, along with its nested obscurity of the ability to create vanity links, let me grab https://git.io/8. It looks like that'll go away one day, I wonder what will become of the domain itself; it's certainly a six figure property.
I recently bought a new Prius. Toyota even has bolt holes to allow easy installation of a "cat shield", and could install a nice steel plate there with minimal additional cost, but instead it was on me to buy and install an aftermarket product. Maybe it's a question of liability?
This is a little pessimistic.[1] As a percentage, few people are expected to die, and modern buildings are unlikely to collapse. At least in the Puget Sound region, buildings codes have been seismically sound for several decades, and old buildings and infrastructure have gradually been retrofitted[2]. There is _already_ preparation being made with the aforementioned programs, and notably the Cascadia Rising simulation excercise carried out between the Washington and Oregon governments and FEMA.[3]
This will be a huge disaster, but our government and institutions are not apathetic to it.
I noticed this as well visiting several years ago. For instance, even though the process for hotel check-in and most other services was automated with these fancy kiosks, they still had two people behind the desk in case you needed help.
In the west, humans are becoming less employable as they're displaced by automation--https://www.youtube.com/watch?v=7Pq-S557XQU is a good video if you haven't seen it, and it's from before AI/ML took off! Japan seems to have mitigated it by making automation an addition, instead of a replacement, in many cases. It's certainly not the efficient, capitalist thing to do, but maybe it's the better thing to do.