Not really. The more likely chain is that the police would receive information about the plot and would fabricate the start of the evidence chain. The common hypothetical is that they'd pull someone over for a traffic violation and 'discover' something in their car that would then give probable cause for a search of other things.
There are schemes like ZipCar that give you access to one of a fleet of cars for short periods. It wouldn't be much of a stretch to extend this to self-driving vehicles. I don't see taxi companies that have human drivers competing with ones that don't - the driver is a significant part of the total cost.
Yes, I too find it difficult to believe that a vehicle using sensors with centimetre precision on nearby obstacles and penetration through rain and fog, direct feedback from the wheels as to current grip levels, the ability to control the angle of the wheels to a single degree or better, and sub-millisecond response controller times, could possibly be better than a human.
Every morning, I turn on my shower and let potable water run down the drain while I wait for the it to heat up. The fact that I have hot running water, and can afford to let potable water go to waste like that without much thought places me not just in the wealthiest 10% of people currently alive, but in the wealthiest 1% of people who have ever lived. Spending a moment pondering that in the morning makes you feel very lucky to be born into a society that can take such things for granted.
Most pizza delivery motorcycles have a large enclosed box on the back that can hold a stack of pizzas. It's thick, insulated, plastic and so keeps them warm. You seem to be missing the grandparent's 'like the rest of the world' comment when you say that motorcycles 'just wouldn't work'. They do in a lot of places...
Given the amount of effort that Microsoft puts into killing competitors, and the hostility between Apple and Google, I'm surprised that IE and Safari don't come with ad blocking out of the box. Making sure IE users never saw Google ads would would hurt Google's revenues a lot more than anything else Microsoft has done.
As I recall, the FDIC limit protects individuals, not accounts. You are insured up to that limit as the total of all of your accounts, not per account. You'd need to split your money between different banks. Even then, the FDIC payout isn't immediate, so you still have the problem of companies losing liquidity.
Most people don't, but most companies do. The FDIC limits are pretty low and it's quite easy for a month's payroll for a medium-sized company to be over it. How many people would have suffered if their employers had suddenly not had enough liquid capital to cover their salary? How many businesses would have closed if they'd been unable to purchase anything for a few months?
Most cybersecurity jobs are in the private sector and don't require security clearance. They're related to ensuring that commercially sensitive information stays private (employees don't wander off with copies, competitors don't hack in, and so on). A lot of it is the same sort of task as the non-cyber variant: checking that the systems you think are secure really are, investigating when they're not, designing policies to make sure that they remain so if they are.
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.
Slashdot is not edited, it is user submitted snippets of info with links back to the source, more about the discussion of the subject than journalistic skills
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...
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.
You can fix it, but I agree that it usually puts it in the worst possible place. The problem is that TeX uses an elegant dynamic programming model to determine where to break lines in a paragraph, but uses a greedy algorithm to do page layout. Why? Because the PDP-10 didn't have enough RAM for the dynamic programming tables that would be required to do elegant page layout on a typical document. On a modern computer, even if it takes 2-3MB for the tables, you most likely have a single image in the document that is bigger than that (in early TeX, images had to be added afterwards in a separate compositing phase after you sent the typeset document to the printer, because computers weren't powerful enough to handle nontrivial images).
I tried implementing the TeX linebreaking algorithm for page layout in some naive (unoptimised) Objective-C a few years ago and ran it on a 900-page book that I'd written. Even then, it took under a second to run on the laptop I had at the time. There's no reason not to do it now.
I like rST, but Markdown seemed to get wider support so I gradually switched to using it instead because they're sufficiently similar that it's annoying using both and lots of things didn't support rST. They're both roughly equal for the sorts of things I use them for: blog posts, articles, doc comments in code. There's no way I'd write a scientific paper or a book in either though: LaTeX is still the king there.
Slashdot Mirror
Not really. The more likely chain is that the police would receive information about the plot and would fabricate the start of the evidence chain. The common hypothetical is that they'd pull someone over for a traffic violation and 'discover' something in their car that would then give probable cause for a search of other things.
Well, on the plus side, 90% of them are already dead...
There are schemes like ZipCar that give you access to one of a fleet of cars for short periods. It wouldn't be much of a stretch to extend this to self-driving vehicles. I don't see taxi companies that have human drivers competing with ones that don't - the driver is a significant part of the total cost.
Yes, I too find it difficult to believe that a vehicle using sensors with centimetre precision on nearby obstacles and penetration through rain and fog, direct feedback from the wheels as to current grip levels, the ability to control the angle of the wheels to a single degree or better, and sub-millisecond response controller times, could possibly be better than a human.
Every morning, I turn on my shower and let potable water run down the drain while I wait for the it to heat up. The fact that I have hot running water, and can afford to let potable water go to waste like that without much thought places me not just in the wealthiest 10% of people currently alive, but in the wealthiest 1% of people who have ever lived. Spending a moment pondering that in the morning makes you feel very lucky to be born into a society that can take such things for granted.
Microsoft's ad business is a tiny fraction of their total income though. They could easily afford to lose it. Google couldn't.
Most pizza delivery motorcycles have a large enclosed box on the back that can hold a stack of pizzas. It's thick, insulated, plastic and so keeps them warm. You seem to be missing the grandparent's 'like the rest of the world' comment when you say that motorcycles 'just wouldn't work'. They do in a lot of places...
Given the amount of effort that Microsoft puts into killing competitors, and the hostility between Apple and Google, I'm surprised that IE and Safari don't come with ad blocking out of the box. Making sure IE users never saw Google ads would would hurt Google's revenues a lot more than anything else Microsoft has done.
As I recall, the FDIC limit protects individuals, not accounts. You are insured up to that limit as the total of all of your accounts, not per account. You'd need to split your money between different banks. Even then, the FDIC payout isn't immediate, so you still have the problem of companies losing liquidity.
Most people don't, but most companies do. The FDIC limits are pretty low and it's quite easy for a month's payroll for a medium-sized company to be over it. How many people would have suffered if their employers had suddenly not had enough liquid capital to cover their salary? How many businesses would have closed if they'd been unable to purchase anything for a few months?
Most cybersecurity jobs are in the private sector and don't require security clearance. They're related to ensuring that commercially sensitive information stays private (employees don't wander off with copies, competitors don't hack in, and so on). A lot of it is the same sort of task as the non-cyber variant: checking that the systems you think are secure really are, investigating when they're not, designing policies to make sure that they remain so if they are.
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.
Slashdot is not edited, it is user submitted snippets of info with links back to the source, more about the discussion of the subject than journalistic skills
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 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.
You can fix it, but I agree that it usually puts it in the worst possible place. The problem is that TeX uses an elegant dynamic programming model to determine where to break lines in a paragraph, but uses a greedy algorithm to do page layout. Why? Because the PDP-10 didn't have enough RAM for the dynamic programming tables that would be required to do elegant page layout on a typical document. On a modern computer, even if it takes 2-3MB for the tables, you most likely have a single image in the document that is bigger than that (in early TeX, images had to be added afterwards in a separate compositing phase after you sent the typeset document to the printer, because computers weren't powerful enough to handle nontrivial images).
I tried implementing the TeX linebreaking algorithm for page layout in some naive (unoptimised) Objective-C a few years ago and ran it on a 900-page book that I'd written. Even then, it took under a second to run on the laptop I had at the time. There's no reason not to do it now.
The flamebait mods are obviously from people who use the other editor.
I like rST, but Markdown seemed to get wider support so I gradually switched to using it instead because they're sufficiently similar that it's annoying using both and lots of things didn't support rST. They're both roughly equal for the sorts of things I use them for: blog posts, articles, doc comments in code. There's no way I'd write a scientific paper or a book in either though: LaTeX is still the king there.
And if you ever talk to a British soldier, you'll find that they're even higher up the list of complaints than the food...