Bah... my intent was certainly to be vulgar, and I stand by that. But if it's going to be interpreted as specifically offensive towards women (an implication not present in UK English) then I'll certainly apologise to all that were thus offended, because that was not part of the plan.
Looks like it's too late to delete it, so we're stuck with it forever.
Right - and in America you're not even allowed to cross the road! To the extent that when a self-driving car runs somebody over, "but but they were in the road" is somehow an adequate defence!
If you want to consider this a cultural misunderstanding, fine. What can I do about that? Nothing. But please, before I go, because I can tell I'm not making much of an impact here, let me say it again: drive carefully, and for fuck's sake don't kill anybody.
If they want to abbreviate "pedestrian", why not "person"? I've never seen anybody use the term "ped" anything other than disparagingly! How should we respond to this attitude? I know what I think, that's for sure: it's crap, and people in charge of operating motorised vehicles should take more care over how they think about people on foot, to ensure that they never behave too carelessly in the heat of the moment.
Anyway: I think I've set out my stall here to the extent necessary. You and anybody else may make of it what you will. Drive with care, and for fuck's sake don't kill anybody.
Sorry about that, I thought my lead-in was obvious and you were playing the straight man :(
Still, I stand by what I said.
EDIT: OK, OK, so after snoozing on it for ten minutes, perhaps I can see why it might appear that I'm more right than you are to a lesser extent than is truly the case. Even though there's nothing for me to apologise for, perhaps I should at least have taken the high road.
What can I say? I'm just reluctant to sit by and stay silent when people seem to blaming the victim so enthusiastically.
Yes, sorry for being unclear. I'm English, so I tend towards the mealy-mouthed. What I'm trying to say is that sushisource is being a cunt for dehumanizing the person that was killed.
Right, but since the driver has seen there's somebody on foot on the pavement, how come they haven't slowed down already? Perhaps the person could trip and fall into the road. Perhaps the person could have a fit and fall into the road. Perhaps the person is just crazy and is contemplating leaping into the road. Perhaps the person is drunk, hasn't seen you, and just fancies crossing the road there and then. It really doesn't matter. These are not capital offences.
What if that person were your son, daughter, wife, husband, parent, or whatever? Would you be so blasé over their losing their life, and all because somebody couldn't even be bothered to just move their foot a bit and press a pedal?
If you can't tell that somebody isn't going to throw themselves under the wheel of your car, you need to drive more slowly, so you've got time to stop when it happens.
My car has cruise control with brake functionality. Not sure if I've ever seen it actually do it - I only really use cruise control on the motorway, where I expect wind resistance is a major factor - but apparently it will apply the brakes to maintain the set speed when necessary.
At town speeds I would expect it to use the brakes a lot more readily. At 30mph in 3rd (2000rpm) or 4th (1500rpm) there's not really all that much engine braking, and wind resistance won't slow it much either.
(Mine is a 2010 model, but I think this stuff was introduced in 2004-6, something like that... it's not exactly new technology.)
Hmm... I have to say the APIs and command line tooling is not where Perforce shines ;)
I found the APIs generally a disaster, and rapidly gave up on them. It was much easier to just run p4.exe and scrape the output. But... oh god. That's not saying much. The command line client was shit too. It eventually proved possible to get everything I wanted, but the data was never quite in the right format, the available queries were never quite suitable, and the results were never quite normalized enough. In the end I had to run p4.exe several times, discarding a lot of redundant data while doing this, and then cross-referencing the multiple sets of results afterwards to get what I wanted.
(One thing I had hopes for initially was p4's supposedly Python pickle-friendly output. But this was no good either! - since, from memory, p4 produces multiple pickles'-worth of data in one go, but Python will only read one pickle at a time, so you couldn't actually read it in from Python without a bit of work. Really made me wonder whether anybody actually tested any of this stuff. Really felt like the thing had been coded by a bunch of Martians, working from a description of the process made by people who'd never used Python and weren't even programmers in the first place.)
When you've got a lot of people, you've got a lot of changes - that's the long and the short of it. This is one thing the check in/check out model (as exemplified by Perforce, among others) is really good for managing. When you go to check out a file, you find out straight away if someone else has it checked out.
If you're just going to make a quick tweak, you'll probably risk it. Either they check it in first, and you've got a very minor merge, or you do it first, and they've got a similar minor merge. Not a big deal, in either case. (And when your gamble doesn't pan out, tough luck. No sympathy from anybody. You knew the risks.)
But, if you're going to make a very large, sweeping change, you'll probably be a bit more cautious. And that's fine: you can go over and talk to them, or message them, or email them, or whatever, to find out what they're doing, and coordinate your modifications appropriately.
I've literally never once found this less than somewhat useful. It's, like, the source control analogue of static typing: a huge pain in the arse if you're not used to it, but, if you've seen it play out, it's a mystery how anybody gets any work done in its absence.
(Of course, if you use git, maybe you can just email/Slack/etc. everybody on the team before you go to edit a file, just in case, and then wait for anybody to mail you back before proceeding... well, I don't deny that would work, assuming everybody checks their mails/Slack/etc. regularly enough. After all, I hear people get work done in dynamically typed languages too! But just think how much better things could be, if the version control system could look after this for you!)
I don't know how many committers have been on the average project I've worked on, but it's probably 25+, and I've worked on several with 50+ - and I don't know how you'd even make Git work at that sort of scale. Obviously people do actually do this, so I assume it must work somehow; I just don't see how it's going to work particularly well.
The larger projects I've worked on have typically used Perforce, but I used Alien Brain (which is pretty terrible) for some of the older ones. The check in/check out workflow, which is the same in each case, is basically what makes it all work once you get past a handful of people. Just simply being able to see who else is working on a (almost certainly perfectly cleanly mergeable) file that you're contemplating modifying is a big time-saver.
(I've used SVN, at a much smaller scale. It has similar Lock/Unlock functionality, which is a good start, but the performance in general of that seemed to be really bad. Locking a few hundred files might take a full minute, for example. Meanwhile, Perforce will check out 1.9 gazillion files in ten seconds, and that's only because it takes nine seconds to change NTFS permissions for that many files.)
I copied the 6510 illegal opcode behaviour for the SY6502A emulator for my BBC Micro, and I've yet to see a problem from it. If they didn't all have the same PLA, then perhaps the differences didn't cause any useful effects...
(Some BBC Micro games definitely do use illegal opcodes, but I didn't take very careful notes when I was writing ver 1, rather a long time ago. For the current version, I just made sure the Lorenz 6502 test suite ran to completion.)
Looks like it's too late to delete it, so we're stuck with it forever.
Please still do drive carefully!