Windows ARM builds are available on their CDN.

Are the switches bad? I recently replaced the switches on my mouse as I had the dreaded double click problem and it was unusable. Then they stopped responding. So I just did something similar to the OP, desoldered and soldered new switches and the mouse was as good as new.

there is, it's called governments. however this technology is so slow that using it in mission critical systems (think communication / coordinates during warfare) that it is not feasible IMO.

the parent post is right, confidential compute is really what we've got.

Cursor does. It tells you how many tokens right above the chat box in the upper right hand corner.

Who is better for that tab completion?

I think most package systems are going to start, if not already, facing real supply chain attacks. The node ecosystem, from an attacker's lens, had quite a heavy leaning ratio of non-security conscious users which makes a better breeding ground for exploitation.

I have largely avoided the entire typescript / JavaScript ecosystem specifically because I don't want to deal with node or its ecosystem. It's just so confusing with yarn, npm, npx, then the build systems gulp, grunt, webpack, etc etc - felt very overwhelming.

Yes, if I spent more time learning these things, it would become simple but that seemed like a massive waste of time.

I hate on Tiobe as well but it is a good benchmark for world wide adoption commercially.

It's basically just the number of Stack Overflow questions / Google hits there are about a language, it's a pretty poor benchmark

I disagree. It's an important project. It's not about Windows per se, but it's amazing to have a source available implementation of Windows internals. There are some really interesting use cases for it that are pretty important.

Ghidra is actually a suite of reverse engineering toolkits, including, but not limited to a disassembler, a decompiler and a debugger interface that interfaces with many debuggers, among other neat things.

A disassembler takes compiled binaries and displays the assembly code the machine executes.

A decompiler translates the disassembled code back to pseudocode (e.g. disassembly -> C).

A debugger lets you step through the disassembly. Windbg is a debugger which is pretty powerful, but has the downside of a pretty unintuitive syntax (but I'm biased coming from gdb/llvm debuggers).

Both the MCP servers can probably be used together, but they both do different things. A neat experiment would be to see if they're aware of each other and can utilize each other to "vibe reverse"