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/).
HN user
connor4312
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.
@ VS Code we've been collaborating on this and plan to ship initial support for registries in our next release.
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.
Is your microbiome not "you"? It's as active a participant in your hormone balance as any other organ in your body.
You might say "I'm hungry", but it's not your rational brain deducing it's time to be hungry. Is an "I'm happy" triggered from the gut any less valid?
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.
Wow, amazing ASCII art! Are you selling an NFT of it?
Additionally, the language server used to power editors is long lived. TypeScript isn't just the compiler.
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.
When you said "some crazy canuck", I immediately knew it must be AvE
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.
1. https://www.newyorker.com/tech/annals-of-technology/how-to-s...
2. https://www.seattle.gov/Documents/Departments/Emergency/Plan...
3. https://www.fema.gov/press-release/20210318/emergency-manage... (a 2022 exercise is planned)
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.
Clicking the "security" tab on their website scrolls down at around 3 fps in Firefox running on a Ryzen 5900X and GTX 3080. (https://memes.peet.io/img/21-04-ed2a915e-f3cb-4372-ba3a-4a37...)
The solution to that problem is clearly to subscribe to their service so that I can stream from a less-anemic machine.
Joking aside, their white paper (https://raw.githubusercontent.com/zhuowei/nft_ptr/main/white...) is a must-read.
Recently sequences of of the COVID vaccines were released[1]. It's amazing to me how such a short sequence of data will make such an impact on the world.
I had the idea to print a couple posters for the occasion, so I made this tool. I linked a redbubble where I uploaded a couple of my favorite designs, but of course you're free to build your own with the tool and print them however you'd like.
1. https://github.com/NAalytics/Assemblies-of-putative-SARS-CoV...
+1. I run entirely Zigbee devices in my home. They don't have internet access and talk to the Home Assistant[1] instance running on my home server.
The downside of Zigbee is that, as a user, there isn't a strong ecosystem of DIY IoT solutions like there is with, for example, the wifi-connected ESP8266/ESP32 chips. And, of course, it requires a hub and some degree of knowledge to set up.
At the moment I'm evaluating launching a small IoT startup/side-business in an underserved market. As much as I love Zigbee, these devices will probably end up being wifi. I'm not an expert in the hardware side of things, and the ability to pay <$1 for an ESP chip that does everything I need off the shelf is great, and I don't want to create a hub or require users to buy a (often $80+) hub just for my set of (<=$5) devices.
Although it'll be wifi-based, I plan to make these guarantees:
- The cloud service (supported by a small yearly subscription) will stay online for at least 1 year after the last device is sold.
- When the service is shut down, its software and hardware will be released under an open source license.
- The subscription fee will never be increased faster than inflation rate.
- 3rd party analytics software won't be used and data will never be shared with 3rd parties (outside from Stripe during checkout). In all cases a minimum amount of data will be collected.
Maybe this'll make my product slightly less likely to appear on the @internetofshit Twitter account[2].
Webpack itself however does basically nothing
This is not the case. I love esbuild and hope to see it go far, but Webpack does out of the box most of what esbuild (today) does as well, with the notable exception of TypeScript /jsx transpilation. For more advanced scenarios, like dealing with css modules, you do need plugins -- but esbuild doesn't support most of these scenarios today at all.
It's like saying VS Code does nothing: you probably want extensions to help you out and let you do more complex things more easily, but it doesn't "do nothing" out of the box.
There are more options here. For example, you can attach to fully remote containers: https://code.visualstudio.com/docs/remote/containers-advance... or just attach to existing local containers that you can set up however you'd like.
So if I use Type Script that gets converted to JavaScript, the end result will be different than if I had done it like that to begin with
This isn't true for Typescript. TypeScript is a superset of JavaScript, and running JavaScript through the TypeScript compiler will produce identical output code[1]. If you add type annotations to that JavaScript to make it fully pass the strictest type checking settings, that will still be true provided you didn't otherwise rearrange or modify your program.
This makes me doubt their methodology on TypeScript at least, or wonder if they're running a tool like `ts-node` which compiles and runs at the same time, thus counting compile time in their execution time and energy.
1. As long as you're targeting the same language version as the original code was written for. For instance the compiler will downlevel async/await into slower async generators if you're targeting a version of JavaScript which doesn't support it yet.
Codespaces works on iPad already https://github.com/features/codespaces
It was a big undertaking :)
the simple internal data model was replaced by a dense and non-orthogonal data model with different types for leases, locks, transactions, and plain-old-keys
I maintain a (/the only?) etcd3 library for Node.js[0], and used etcd extensively on my former team.
None of these things are new to etcd3 API. All of these are present on v2 as well[1], whose API the author extolls, or are built within clients on etcd's base APIs (e.g. there's no 'lock' API, only leases). However, with etcd3 we get stricter typing, better performance, and better semantics (e.g. watch streams and lease streams over polling) thanks to GRPC.
In general these rich APIs allow 'average' engineers to build complex distributed apps more correctly. I've built reliable sharding, hash rings, elections, and so on based on etcd's API--none in more than a hundred or two lines of code (more in Go, less in Node.js). All of these are classic hard problems that etcd makes easy. Sure, there's innumerable standalone services for each of these things, but often there's no need to take the cost of many tools when one would work.
Exponential refers to c^N. N^c is quadratic. Small visualization: https://www.onlinemathlearning.com/image-files/exponential-q...
remember that the house always wins.
In a casino, it's the impetus of the establishment to make money. In the stock market, it's the impetus of the shareholders to make money. If the house always wins[1], shareholders are the house.
1. This is a tenuous metaphor for the stock market--true in the US over long periods of time, but perpetual growth is not guaranteed.
Also, you have to vote on a product to see its "creepiness" rating breakdown? I would supposedly be using this site before purchasing a product, how would I know how "creepy" it is? This site seems more akin to a Buzzfeed quiz than a Mozilla project.
That said I think this idea has a lot of potential, but this is perhaps not the best form for it to take.