A stack trace (or even better, a minidump with the call stack!) is one of the most useful debugging things for me. Hell, the call stack in general is super useful to me!
I can look at a stack trace, go "oh, function X is misbehaving after being called by function Y, from function Z", and work out what's gone wrong from the context clues, and other debugger info. As a game developer, with codebases that are big, semi-monolithic codebases, it's essential, especially when code crosses the gameplay/engine and engine/kernel barriers.
It's funny, as my phone (A 2022 Moto Razr) can work as PC, if I plug it into a monitor with it's USB-C port. I can plug it into a monitor, and plug a mouse and keyboard into the monitor's inbuilt USB-C hub, and it works just fine. Has a desktop mode and everything! If the monitor doesn't have a hub in it, I can use the phone as a mouse/touchpad! Plus, if the monitor supports it, it'll even keep it charged rather than using the battery!
And I don't just use it as a gimmick, I use a HDMI/USB-C cable to use it with my TV as a streaming/light gaming setup. Nice to be able to plug it in, kick off a streaming app or Youtube, or play some Minecraft or something on my TV in bed, all comfy.
Knowing the UK, BT will ring up their Tory mates in power and ask them to remove the workers rights, so that they can get away with it. Hell, workers rights are already up on the chopping block, so they might not even have to bother ringing up.
I read through, and I (someone with no military experience) came to a pretty much identical conclusion. No point fighting if the objective can be secured with diplomacy. Granted, you always have to be ready for a fight, so having overwatch is paramount. But yeah, going for a hearts and minds approach seems the most sensible way of completing the objective with a minimum of fuss, given the situation presented.
It's funny, in that my (current) PhD hasn't felt anything like that. I dunno if it's my source of funding or whatever, but I've not had to do much more than the research I said I was going to do when I got the funding. I've had a module here and there, but otherwise, I've been able to 100% focus upon the research that I've been doing, which I've totally self directed. My supervisors have been great, supportive, etc, and I've benefited from links to industry as well. It's been a great 2.5 years, and I'll be sad once it's over, really.
They really aren't. The TB2 can loiter at 18,000 ft, or about 5.5km. 20mm guns max effective range is about 1,500m. 40mm are better, but still max out at about 7,000m. You're not going to be able to hit it. That assumes you can even see it, which you probably can't.
Not really. The low health tracks aren't just sped up, they're compositions in their own right. Because of that, a separate track ID makes total sense as they are different music tracks.
I can look at a stack trace, go "oh, function X is misbehaving after being called by function Y, from function Z", and work out what's gone wrong from the context clues, and other debugger info. As a game developer, with codebases that are big, semi-monolithic codebases, it's essential, especially when code crosses the gameplay/engine and engine/kernel barriers.