Regardless of the side, if the convicts have proper training, supplies and aren’t used as pure cannon fodder I don’t have any issues with it personally.

Honestly, I am surprised that Ukraine wasn’t doing it sooner. Unfortunately, the front has been somewhat slow for the last year or so (with an exception or two) and that means both sides are dug in fairly deep.

If Ukraine decides to push back harder and start retaking large portions of land, their losses are going to skyrocket. Regardless is you agree or not, using convicts to push the lines makes sense and doesn’t risk better trained troops.

That is just how wars of this type work and the offensive side will need to absorb more damage.

Personally, if I had the option of fighting or rotting in prison, I would fight and would probably volunteer for some of the hardest work. The thing is, it would need to be my choice and I hope that any convicts, Russian or Ukrainian, get a choice in that.

Ukrainian convicts are probably going to get decent training first. It’s also likely they are going to go into some of the worst spots. Ukraine is outnumbered and they can’t afford to lose anyone, criminal or not, but it doesn’t mean they are going to have it easy.

Russia/Wagner hardly gave their convicts any training, maybe gave them guns and supplies and sent them to the front blind to find artillery locations. They were cannon fodder, pure and simple. Bakhmut was a slaughter.

There are some major differences here.

I am not sure where y’all evolved, but you skipped a few thousand years and a whole bunch of sharpened sticks.

Oh yeah. They are totally cool with it. A gay neo-nazi Republican on Reddit told me so.

(First sentences: Joke. Last sentence: I wish I was joking.)

It’s also illegal in 14 states (plus D.C.) due to mag capacity.

I have heard a few things, TBH. Everything in the range from simply vaporized and hot to the vaporized metal being in a near plasma state. Shrug.

Wikipedia gives a few numbers ranging from 660K to almost 1200K (copper melt temp is 1358K) from testing it quotes. It seems to be dependent on the cone alloy and the explosive type.

In practice, it’s probably is all over the place in regards to temperature. If you can round up a few RPGs, I would totally be down for some testing…

I am going to need your 50 point summary of those obvious points in the longest form possible by this afternoon so I can be completely convinced that I have already made up my mind in the correct way. Thanks.

That is a photoshopped picture, btw.

I can’t imagine that keyholing like that would be even be slightly tolerated and it’s not too difficult to get stable flight unless there are serious issues with the firearms.

If a bullet is tumbling out of the barrels, those barrels are seriously fucked. They are shot out, are using bullets that are too small or there are serious defects with the bullets.

A bad twist rate or extremely poor load generally won’t cause tumbling until much later. If the bullets start at slightly at supersonic and slow to subsonic quickly, that might do it.

I would like to see those videos of the keyholing you described, which is why my brain seems to have vomited all over this comment. (This has got me super curious, is all.)

As an example, RPGs use shaped charges to send a jet a molten copper through armor steel. Even though the devices may seem antiquated, they are extremely effective at burning holes through tanks. If that molten jet happens to come in contact with ammunition, it’s generally game over.

Mine probably did too, TBH. Why I didn’t use it is anyone’s guess.

I don’t get it. The key still gets declared, but it’s value is null. “name” in an empty object would return undefined, not null, correct?

(Yes, this joke whooshed, but I am curious now.)

Two??? Lol!

Really? I thought they would be sitting back drinking mojitos while watching the show.

That weapon seems to have a full-brrrt, so this is just standard recoil mitigation and you can hit targets at 50, 100, 500 and 1000 yds with one burst.

Lulz.

It was on old 3.5" drives a long time ago, before anything fancy was ever built into the drives. It was in a seriously rough working environment anyway, so we saw a lot of failed drives. If strange experiments didn’t work to get the things working, mainly for lulz, the next option was to see if a sledge hammer would fix the problem. Funny thing… that never worked either.

I used to take failed drives while they were powered on and kinda snap them really with a fast twisting motion in an attempt to get the arm to move or get the platters spinning.

It never worked.

Seriously though, blurred glasses seems like a recipe for a nasty headache. You would probably be better off with nothing, like eye covers for sleeping.

Did you get bad sectors? Weird things can absolutely happen but having sectors marked as bad is on the exceptional side of weird.

Maybe? Bad cables are a thing, so it’s something to be aware of. USB latency, in rare cases, can cause problems but not so much in this application.

I haven’t looked into the exact ways that bad sectors are detected, but it probably hasn’t changed too much over the years. Needless to say, info here is just approximate.

However, marking a sector as bad generally happens at the firmware/controller level. I am guessing that a write is quickly followed by a verification, and if the controller sees an error, it will just remap that particular sector. If HDDs use any kind of parity checks per sector, a write test may not be needed.

Tools like CHKDSK likely step through each sector manually and perform read tests, or just tells the controller to perform whatever test it does on each sector.

OS level interference or bad cables are unlikely to cause the controller to mark a sector as bad, is my point. Now, if bad data gets written to disk because of a bad cable, the controller shouldn’t care. It just sees data and writes data. (That would be rare as well, but possible.)

What you will see is latency. USB can be magnitudes slower than SATA. Buffers and wait states are causing this because of the speed differences. This latency isn’t going to cause physical problems though.

My overall point is that there are several independent software and firmware layers that need to be completely broken for a SATA drive to erroneously mark a sector as bad due to a slow conversion cable. Sure, it could happen and that is why we have software that can attempt to repair bad sectors.