Many years ago I used UltraEdit.

I usually simply don't answer any call that's not in my contact list, but that doesn't stop them. There are paid services on the internet that promise to remove your data from as many spam databases as possible, but I never tried.

Analog Devices maintain a github repo where they keep many drivers for their chips organized by category in different folders.

STM32 CubeMX can generate peripheral initialization code and HAL includes for the microcontroller's peripherals.

Depending on which kind of devices you are talking about, for some brands there are already some options.

I might be wrong indeed, but I think the final result still involves some memory being leaked, because if I delete the macro body and save the file, rust-analyzer becomes alive again, the memory usage stops growing, but it doesn't decrease. If I then put back the code it starts growing again.

By the way, I noticed that in the last 24h the number of issues on their repository is increased by more than 100. The people there must be quite busy nowadays. I am considering to try to contribute myself, but it would be a completely new field for me, since I normally play on the embedded field.

Plus, a work laptop might be often offline on a business trip. Being unable to use the search function to find an app on my PC because I'm on a bus without hotspot simply doesn't make sense for me.

The obvious reason behind this might be that Microsoft, for some reason, decided that if you are looking for an app not installed on the PC, you probably mean to look for it online. But hell, if you stop and think about it for a moment it's complete nonsense.

One thing I hate about it is that the search function, to find an app or a file on your own PC, where Windows is currently running, doesn't seem to work if you are not connected to internet.

I think usually it's done like `try_register` and `register`

Tell them that typescript says hello

I'll take a deep dive in its documentation, but it sure looks good, even though it's probably a bit overkill for a soft start. Thank you for the pointer!

Recently I realized that my approach to start writing a new fn in Rust is now this: start with "const fn ..." without thinking and then remove the "const" keyword after I realize it really can't stay.