You can have a memory leak when items are still in scope in some loop or when you have a reference count cycle. The latter happens with the Rc/Arc types in rust.

An example for the former can be a web server that keeps track of every request it's ever received in memory. You will eventually run out of memory. But you did not violate any memory rules (dangling pointer, etc.). Memory leaks can be caused by design issues.

You did your link backwards. The text is the url and the url is set to "these".

Php has gotten fairly advanced compared to what it used to be so it counts. Html doesn't count since it's a markup language not a programming language. You can't control logic with it, but JavaScript does count.

I knew someone who did this but swapped out the physical hard drive each time. I wouldn't dual boot because then it's much more obvious to IT what you've done.

This is only realistically feasible though if the hard drive is easily accessible. If it's something like a Mac or soldered in dual booting is your only choice. As others have said, this could get you in a lot of trouble with your company. Check the docs you've signed

File a complaint with the labor board. They can investigate and if they find out they used your solution you can get paid and they can get a fine on top of that.

They likely get repaired/replaced when they die. When the batteries die the brake locks shut so you can't move it. No idea how long they last though

It shouldn't break if you just install packages from the main app installer. It's more of a concern if you're trying to install anything from source.

Also make sure to try a live cd or live USB to make sure the OS is compatible with your hardware. VM is not sufficient for this last one. This is usually only an issue if you have very new hardware.

I assumed those were for hobbyists. I would be surprised if that was used in a major product given how many cycles you lose to python implementation.

Maybe too late now but do you have any pics of what the connections looked like when it failed? Also any chance anything at all could have shorted on the motherboard or PSU?

Data on the disks wouldn't cause this but maybe something shorted on one of the drives. I think that's unlikely and more likely is something somehow shorted against the motherboard itself. You have standoffs on the motherboard, right?

I really prefer rust's approach. The function signature is the contract. It makes it much easier to debug compared to overly generic pure functional code or c++ templates where everything is auto and perfect forwarded.

The only time in rust where this isn't true is with async functions. That's because the compiler adds a ton of sugar to make it easier to write.

I didn't intend to imply that only one server changes something. I was intending to imply that the protocol should be updated (after review, ratification, etc.). I'm sure there's edge cases I haven't considered.

I'm using Jerboa on Android and it's really, really nice. Reminds me of Boost.