If you're asking an art professor about HCI, then you're doing it wrong. Try looking over in cognitive psychology for people who can give useful input.

Last time I had a story accepted, it was edited. By which I mean they deleted random bits and introduced a typo. If they're going to modify things, they could at least improve them...

Have you ever tried breathing in a city like New York or London? If I lived in either, I'd be advocating socialised buying of EVs for anyone who wanted one...

New York has both state and city sales taxes. Sales taxes are generally regarded as regressive, so poor people definitely do pay tax there...

Stopping in the middle of the street in NYC is largely impossible, as the precondition - moving in the street in NYC - is almost never met.

I think he's fine with them only killing peasants.

Drivers don't kill people, firmware kills people.

Can we apply the same standards to human drivers too please?

No, they're automobiles because they move themselves and don't need a horse attached to the front.

Which makes the 'I don't own a car, you insensitive clod' option an obvious omission. The poll poster must have been American (and presumably not live in New York, San Francisco, or one of several other big cities) to believe owning a car is unavoidable. I've never felt the need to do so, and here there is so much of the city that you aren't allowed to drive in (unless you're driving a bus or a taxi) that a car is slower than cycling in almost all cases and slower than walking in some. There are busses or taxis if I'm too lazy to cycle. Why would I want all of the expenses involved in owning a car?

I don't shoot anymore (it's fun for a while, but it gets boring after a bit), but I never had problems getting access to shotguns or target rifles (including some fully and semi automatic) as a teenager in the UK. Handguns became illegal around this time, although there were some exemptions, such as for black-powder revolvers that kept most hobbyists happy (they take ages to reload, but you get half a dozen shots before you need to, which lets you put some holes in a target) and many of the rest moved to air pistols or carbines.

Collaborative editing is often easier. This isn't necessarily a property intrinsic to online office systems, but offline ones are typically intended for offline editing. Even with a decent revision control system (is there one that can merge OO.o or MS Office docs? No idea), you periodically get sets of changes from other people and have to merge them. If you've got something that allows live editing by multiple people, you can see what other people are doing at the same time as you and avoid conflicts.

There's no reason that an office application couldn't support this, it just seems to be a feature they haven't implemented. You'd probably want a single server for your organisation that would track all of the changes (allowing every desktop to accept connections for peer to peer editing would give network security people nightmares, especially considering the security record of MS Office), and it would be great if the server could push change sets out to some revision control system so that they could be synchronised with other documents (maybe push live editing into a branch and then have a merge step as part of hitting save).

I don't know about you, but I consider being able to leave the office and work outside on a sunny day or in the pub on a rainy one to be a feature. I have friends who have an hour-long commute on a train or bus each way in London and Silicon Valley, and they're very happy that they can count this time towards their working day, rather than as personal time.

The best test of whether you understand something is whether you can explain it to someone else. If you can't write good documentation, then you probably don't really understand your code, which means that you're not a programmer you're a code monkey (and not a very good one, at that).

WYSIWYG is a terrible way of writing, but it's a great way of editing. The problem is that most modern tools conflate the two. When I write, I prefer to use vim and minimise the distractions - I see the words, I focus on the words and the markup describing their meaning, and I worry about the typesetting later. For articles, actually I don't worry about the formatting at all, my publisher sorts all of that out and so there's no reason for me to bother. I don't care what it looks like - that's not my job as a writer - I care that it's coherent and fluid prose. For books, I use LaTeX, and then I typically have a few rounds of iterations at the end of each chapter when I do the tweak-recompile-check cycle. I structure my environment such that I can build each chapter independently, which speeds up the build times, but it's still painful getting the style tweaks in correctly. I'd be much happier if I could get LaTeX to do a first formatting pass and then use a visual WYSIWYG editor to tweak everything and have those changes preserved the next time I do a formatting run from the source text.