lol but starting a war to murder your neighbors and take their land isn't
fiah
so they just slapped it on the hull and called it a day as they moved on to the M4 Sherman
yep, but you can also easily tell from that photo that the M3 hull formed the basis for the M4 hull. Basically they wanted to build it like the M4 the whole time but couldn't, so the M3 was made on that platform as a stop gap solution
where was the victory parade on the 4th day of this special operation?
edit: lol I just got banned from the lemmy.ml world news for suggesting that it's way past a hexbear's bed time. I guess I should've known those mods are tankies
based working girl whisperer
yeah, you know what they say: first one's free
hah! The 1993 documentary The Nightmare Before Christmas already conclusively proved that Santa can't even evade regular ol' flak
But, you totally can? When you store all your dates as an ISO 8601 string (UTC, so with Z at the end), you can simply compare the strings themselves with no further complications, if the strings match, the dates match, if one string is less than the other, the date therein is before the other. Their lexical order is equal to their chronological order
I agree that it's a massive and unnecessary overhead that you should definitely avoid if possible, but for anything where this overhead is negligible it's a very viable and safe way of storing date and time
edit: I forgot, there's also a format that's output by functions like toUTCstring that's totally different and doesn't have any logical order, but I honestly forgot about that format because nobody in their right mind would use it
If only there was a summary of said article right here in the comment section, not even a click away
why not? assuming you're saving them all in UTC they should be perfectly sortable and comparable (before, equal, after) as strings, even with varying amounts of precision when you compare substrings. You can't really do math with them of course, but that's what I meant about how DBs interpret dates and time: if you use it do to math and then you also use your application's date library to do math, you'll likely run into situations where the two come to different answers due to timezone settings, environments, DB drivers and the like. Of course if I could rely on the DB to do the math exactly the way I'd expect it to, then having that ability is awesome, however that requires more knowledge about databases and their environments than I currently have
Personally, I would probably just store them as text, because I'm objectively a terrible programmer.
I don't know man, I'd far prefer storing a string and have whatever date library I'm using figure it out than have to deal with whatever the database thinks about dates and timestamps
it has been shown that the MATE-XT upper limb exoskeleton and the MATE-XB lumbar device can reduce users’ effort by up to 30 percent
I guess every little bit helps, but I thought they'd be shooting for something like 50+% at least
well good riddance then I guess