Subverb

Please try kagi.

Not saying it’s you, but some people that think paying for Search is silly have forgotten how wonderful clean searches with actual answers are.

I totally came to say this. Google has become designed to tarpit you into staying on the site longer. They no longer have the goal of giving you what you want quickly, they want you to see more ads.

Google makes $307/yr. per user. They are strongly motivated to tarpit us. If we want a clean search experience we need to be open to the idea of paying.

As an embedded systems dev that searches a lot of obscure stuff, I use Kagi and love it. Go try its free searches and see for yourself.

If you value your time and mental stability, please do yourself a favor and go see what clean, high quality search results look like on Kagi.

Anyone who uses this should be considering switching to Linux though.

I was just reminding you that many of us have jobs or software tools that preclude us from using Linux day-to-day regardless of how much we might like the idea. Having a more comfortable windows experience has value to us.

I’m locked on windows because of very expensive embedded systems dev tools. Give people some credit for having considered linux; not everyone can switch.

I’d love to switch to linux but it just doesn’t make sense for me.

I’m an embedded systems developer and my proprietary toolchain is windows only. Additionally I use several Adobe product routinely (illustrator, photoshop, premier).

Sucks.

Every kernel update (and there are tons) requires me to rebuild my third party modules, but you need to do it in a toolbox and the kernel headers version must match the running kernel version, which is actually more annoying than it sounds.

Boy, I doubt that.

My Windows 11 machine doesn’t require any of that.

I’m using kagi as well and have been very pleased with it.

Having a language dependent on indentation is absurd on the face of it. It’s a ridiculous idea that should have been ridiculed from the outset.

echo “calories” >> .gitignore

The malicious code was written and debugged at their convenience and saved as an object module linker file that had been stripped of debugger symbols (this is one of its features that made Fruend suspicious enough to keep digging when he profiled his backdoored ssh looking for that 500ms delay: there were no symbols to attribute the cpu cycles to).

It was then further obfuscated by being chopped up and placed into a pure binary file that was ostensibly included in the tarballs for the xz library build process to use as a test case file during its build process. The file was supposedly an example of a bad compressed file.

This “test” file was placed in the .gitignore seen in the repo so the file’s abscense on github was explained. Being included as a binary test file only in the tarballs means that the malicious code isn’t on github in any form. Its nowhere to be seen until you get the tarball.

The build process then creates some highly obfuscated bash scripts on the fly during compilation that check for the existence of the files (since they won’t be there if you’re building from github). If they’re there, the scripts reassemble the object module, basically replacing the code that you would see in the repo.

Thats a simplified version of why there’s no code to see, and that’s just one aspect of this thing. It’s sneaky.

Oh I agree. But my god the embedded industry is slow to update toolchains.

I would love to have Rust as an option for my ARM development, but that’s years off. ARM is only now about to come out with a visual studio based toolchain for their Keil C compiler instead of the proprietary IDE.

As an embedded systems programmer I’d like to point out that that’s not true at all.

I meant faster than Python, not faster than Rust. Rust is fast.

Nevermind that the C++ program is two orders of magnitude faster when completed.

I would love to learn and use Rust but I’m a embedded systems guy. Everything of consequence is C and C++.

I have a 1984 Model M. Love it.

I bought mine here but there are other places that restore them.

I actually use caps lock fairly regularly as a embedded systems programmer. With my large hands CTRL-ESC is pretty easy for me.

I’m happy as a clam with my 1984 loud as fuck IBM Model M keyboard in Windows.

Think you need a Windows key? CTRL-ESC. I use CTRL-ESC even on modern keyboards.

I write embedded firmware for my own business’ products and I fall into this trap myself.

I wanted to whip out a basic little product for my business thinking it would take two months of hardware design and a couple weeks of C.

A year later it’s a neat little product…

AKschually, thumbs aren’t fingers.