Like all "social" networks, Google+ can't help itself from bothering me for more information. Do I know these people, where did I go to school, etc. Interstitial questions and unclosable boxes that want more personal info. As a result I rarely use the service at all. I realise this is a radical idea but a simple "stop bugging me" option might make me more inclined to use the service. I'm sure they'll still gather usage info when I'm on their site and of course make money from ad revenues. Just stop fucking bothering me.
Simple... Android.textbox.Draw, and Winforms.textbox.Draw usually don't have the exact same semantics. In fact, usually the APIs are structurally different. Often there simply isn't analagous functionality on one or other platform.
The same could be said of lot of emulation / compatibility layers yet they still exist. Apparently the Xbox One supports certain 360 games because they recompiled and linked the executables using a compatibility library - they run natively but think they're running on the 360.
Likewise wine / winelib allows Windows software to run on Linux or OS X (through commercial forks of Wine). And Wine didn't even have the benefit of being able to look at the Windows source. I actually looked at a Wine implementation of the comctl32 tooltip today because MSDN's documentation is so bad I couldn't figure out what I was supposed to pass in.
A closer example might be Blackberry porting Android to run over QNX on the Playbook and BB10. Somehow Blackberry can manage it but Microsoft can't? I see no reason to believe that. More likely they know it would be commercial suicide to support Android apps and killed the project.
Scrum is used all over the place and where it is used it tends to work fairly well - assuming its used in moderation. The problems for scrum is there are a lot of bullshit, harebrained concepts & jargon which heap process upon process and make the whole thing a pain in the ass - e.g. social contracts, waste snakes etc. Keep it simple and it's quite tolerable and productive.
Anonymous are more like basement dwelling assholes. Any reason to attack anyone will do as far as they are concerned. And if no reason exists they'll attack and then concoct one after the fact.
Of course it's difficult - assuming there are pedestrians and lots of turning. But El Camino Real is one of the straightest roads in San Francisco. It runs straight for about 30 miles, 3 lanes each way and there are very few pedestrians crossing because it is a hideously pedestrian unfriendly road to cross. Most will cross at lights if they bother at all.
But there is probably a grain of truth here. I bet Google is terrified of their vehicle being involved in a high profile accident so they make it crawl along knowing that even if it does screw up they can pretend it was a fender bender or suchlike. And a pedestrian hit by their car is obviously more likely to survive a low speed collision than a high speed one.
The problem with this, as found by the USAF with drones, is that when you automate too much it becomes impossible for the operator to keep sufficient attention on the drone's automation. And this is with professional pilots.
And that's why you don't automate too much. And you require the driver to hold the wheel and perform any other tests that measure alertness. And to prevent the driver getting lazy (e.g. letting the car slam the brakes on) the car "punishes" them by ringing an annoying alarm for 30 seconds.
"'without lobotomizing the vehicle' would be to go ahead and make it fully autonomous. Once it's fully autonomous it can also do things like pick you up at the door of your work, the mall, etc..."
Except such a thing is virtually impossible any time in the forseeable future. Ain't going to happen.
The best solution would be to allow a human to drive and have a computer to help with emergency braking, skid control, smart cruise control, lane tracking, safe overtake, parallel park etc., Assistance that makes driving safer and more convenient without lobotomizing the vehicle in the process.
I think the answer to that is obvious. I bet the engineers have to take over a lot because the car is acting stupid, or ignoring hazards or signs that a human would easily recognize.
But as a device it's a damned sight more useful to me than any tablet produced by Apple is. It's a proper PC that also happens to operate as a tablet.
Personally I'm somewhat surprised that neither Google nor Apple have produced something analogous - something which can be a desktop for professionals who need a desktop but also reverts to be a tablet for when someone is just browsing or doing something which doesn't require a keyboard / mouse. Google are supposedly trying to merge ChromeOS and Android which may eventually become their solution. I don't believe that Apple isn't doing something similar despite their noises about what a terrible idea it is.
Save games don't help you if you don't know how the guy died - if he ran off the cliff many hours ago for reasons unseen to you. Even if you find the point in time where the guy is alive you still have hours to repeat and hope he doesn't die again. It also wouldn't be the first time either that an ES / Fallout game has crashed because the save games themselves have become corrupted.
These games have a main and various major story arcs, many of which are interdependent. So it's not a free world. If you can't complete a major story arc because an NPC is dead, missing, or stuck in the wrong place, or because the item you're supposed to have didn't appear or whatever then the game IS broken. I can understand that it doesn't matter if some random encounter kills an NPC required for some minor sidequest but the bugs are always more serious than that.
That's why it's better to wait. If Bethesda can't be bothered to release well tested games then I'll wait until they release the fixes. In the meantime the price will drop and I end up with a less buggy experience that cost less.
I expect the main reason is there are only a handful of iOS devices to worry about, predominantly sold in a handful of core countries. Compared to the multitude of Android devices sold all over the place. It probably represents a smaller risk and development effort even if the Android game ends up being the long tale that sustains the game when it does get ported.
The new design sucks and it's hardly surprising that people don't know where to look for it. It's so anti-intuitive it reminds me of the way Facebook, Google etc. put links they'd rather you didn't use in places where people least expect them to be.
People never seem to learn and continue to preorder games when there is a serious likelihood that they will arrive broken.
This is especially true for Bethesda games where glitches seem to be given a free pass. Except you could be many hours and then suddenly the NPC you need to complete the game falls off a cliff and dies because of a glitch. Then you're fucked and have to start all over again.
It's better to wait until the game is heavily discounted and patched up.
Maybe you should read TFA. " After that warranty is up, owners will have the opportunity to trade it in, pay an additional $1,500 and receive a “real” mechanical TAG Heuer watch."
So no you don't get a mechanical watch for free. You get a mechanical watch if you drop another $1500. So $3000 in total. And which mechanical watch does it get you? It doesn't say.
I very much doubt it's "Swiss made" or even what that even means for a device whose innards were probably produced in some far East factory.
$1500 IS a lot for a watch. Especially one which will be bitrotten or obsolete within 2 years. It'll just be some worthless piece of crap gathering dust at the bottom of a drawer after that.
I'm sure a "robot" (meaning just some kind of programmable industrial machine) could be made to perform many repetitive tasks in the kitchen.
e.g. one that peels and chop a variety of vegetables - monotonous, boring, repetitive work where a limited amount of visual inspection (to find blemishes, rot etc.) could be programmed into it. The programming might involve washing, scrubbing, peeling and finally slicing / dicing the veg which is all fairly straightforward.
And devices could be made which can prepare a range of soups and sauces based up on some schedule of tipping ingredients into a pot, regulating the temperature of the pot, stirring etc. Again fairly straight forward. Also similar devices that baked, grilled or roasted items.
Anything which is repetitive, formulaic and generic in nature is a candidate for automation. It already happens on an industrial scale - ready meals and so on. But the problem of course is a kitchen is not a factory and it would fill with these damned appliances. You'd still need humans to feed the components into the machines, switch settings, inspect the meat / veg, serve, and plate up. Cleaning the machines would be a major pain in the ass. As would safety around these machines. As would making contingency plans when a machine broke.
I expect most chains would prefer that all of the above happened offsite on an industrial scale as they do already. They'd had a freezer full of chopped veg, sauces etc. that they just heat up. I expect most individual restaurants would only find a limited use for such devices for cutting potatoes or suchlike.
No, every day driving isn't filled with problems intractable for humans. Quite the opposite. The things which are hard for humans are reacting in time to apply brakes, anti-skid maneuvers and the usual foibles of tailgating, driving too fast etc. Which is why I said advanced driver assist is a better route to go and which does use the strengths of both human and computer.
Every day driving is filled with problems that would be intractable for a computer. Anyone who wasn't drinking the self drive koolaid would realise this in a second.
The best chance self drive has is on closed loops, e.g. airport terminal transfers where vehicles can drive separately than the other traffic in mostly predictable conditions. Even there there'll probably be some guy in a booth whose job it is to takeover if the car gets stuck, confused or breaks down.
On the public roads it would be better for vehicles to focus on advanced driver assistance - smart cruise control, emergency collision braking, hazard avoidance, lane tracking and niceties such as parallel park etc.
I read a lot of books from OpenLibrary (an awesome resource for old books). Most e-books are offered for download in EPUB and PDF format. The PDF is a direct book scan, the EPUB is OCR'd from the scan. Invariably the EPUB is filled with errors caused by OCR - hyphenated words not joined back together, page numbers appearing in the middle of text, words autocorrected to something else, chapter headings screwed up etc. Sometimes the OCR gives up entirely.
It's simply easier to read the PDF although the file size is enormous and you're basically looking at images of some yellowing old book which means lots of panning and zooming particularly on small devices. And forget reading it on an e-reader.
So yeah I think you could automate scanning of books, but the second step of getting it into EPUB format is the tricky part.
Slashdot Mirror
I moved back to My Yahoo when iGoogle disappeared.
Like all "social" networks, Google+ can't help itself from bothering me for more information. Do I know these people, where did I go to school, etc. Interstitial questions and unclosable boxes that want more personal info. As a result I rarely use the service at all. I realise this is a radical idea but a simple "stop bugging me" option might make me more inclined to use the service. I'm sure they'll still gather usage info when I'm on their site and of course make money from ad revenues. Just stop fucking bothering me.
You've made an effective and demonstrative argument why not to use a Perl.
Simple... Android.textbox.Draw, and Winforms.textbox.Draw usually don't have the exact same semantics. In fact, usually the APIs are structurally different. Often there simply isn't analagous functionality on one or other platform.
The same could be said of lot of emulation / compatibility layers yet they still exist. Apparently the Xbox One supports certain 360 games because they recompiled and linked the executables using a compatibility library - they run natively but think they're running on the 360.
Likewise wine / winelib allows Windows software to run on Linux or OS X (through commercial forks of Wine). And Wine didn't even have the benefit of being able to look at the Windows source. I actually looked at a Wine implementation of the comctl32 tooltip today because MSDN's documentation is so bad I couldn't figure out what I was supposed to pass in.
A closer example might be Blackberry porting Android to run over QNX on the Playbook and BB10. Somehow Blackberry can manage it but Microsoft can't? I see no reason to believe that. More likely they know it would be commercial suicide to support Android apps and killed the project.
Scrum is used all over the place and where it is used it tends to work fairly well - assuming its used in moderation. The problems for scrum is there are a lot of bullshit, harebrained concepts & jargon which heap process upon process and make the whole thing a pain in the ass - e.g. social contracts, waste snakes etc. Keep it simple and it's quite tolerable and productive.
Anonymous are more like basement dwelling assholes. Any reason to attack anyone will do as far as they are concerned. And if no reason exists they'll attack and then concoct one after the fact.
But there is probably a grain of truth here. I bet Google is terrified of their vehicle being involved in a high profile accident so they make it crawl along knowing that even if it does screw up they can pretend it was a fender bender or suchlike. And a pedestrian hit by their car is obviously more likely to survive a low speed collision than a high speed one.
The problem with this, as found by the USAF with drones, is that when you automate too much it becomes impossible for the operator to keep sufficient attention on the drone's automation. And this is with professional pilots.
And that's why you don't automate too much. And you require the driver to hold the wheel and perform any other tests that measure alertness. And to prevent the driver getting lazy (e.g. letting the car slam the brakes on) the car "punishes" them by ringing an annoying alarm for 30 seconds.
"'without lobotomizing the vehicle' would be to go ahead and make it fully autonomous. Once it's fully autonomous it can also do things like pick you up at the door of your work, the mall, etc..."
Except such a thing is virtually impossible any time in the forseeable future. Ain't going to happen.
The best solution would be to allow a human to drive and have a computer to help with emergency braking, skid control, smart cruise control, lane tracking, safe overtake, parallel park etc., Assistance that makes driving safer and more convenient without lobotomizing the vehicle in the process.
I think the answer to that is obvious. I bet the engineers have to take over a lot because the car is acting stupid, or ignoring hazards or signs that a human would easily recognize.
Gosh they're really putting the system through its paces then. It really shows how immature this tech is and will be for the foreseeable future.
It always contains bugs.
Personally I'm somewhat surprised that neither Google nor Apple have produced something analogous - something which can be a desktop for professionals who need a desktop but also reverts to be a tablet for when someone is just browsing or doing something which doesn't require a keyboard / mouse. Google are supposedly trying to merge ChromeOS and Android which may eventually become their solution. I don't believe that Apple isn't doing something similar despite their noises about what a terrible idea it is.
These games have a main and various major story arcs, many of which are interdependent. So it's not a free world. If you can't complete a major story arc because an NPC is dead, missing, or stuck in the wrong place, or because the item you're supposed to have didn't appear or whatever then the game IS broken. I can understand that it doesn't matter if some random encounter kills an NPC required for some minor sidequest but the bugs are always more serious than that.
That's why it's better to wait. If Bethesda can't be bothered to release well tested games then I'll wait until they release the fixes. In the meantime the price will drop and I end up with a less buggy experience that cost less.
... Komodo dragons.
I expect the main reason is there are only a handful of iOS devices to worry about, predominantly sold in a handful of core countries. Compared to the multitude of Android devices sold all over the place. It probably represents a smaller risk and development effort even if the Android game ends up being the long tale that sustains the game when it does get ported.
The new design sucks and it's hardly surprising that people don't know where to look for it. It's so anti-intuitive it reminds me of the way Facebook, Google etc. put links they'd rather you didn't use in places where people least expect them to be.
This is especially true for Bethesda games where glitches seem to be given a free pass. Except you could be many hours and then suddenly the NPC you need to complete the game falls off a cliff and dies because of a glitch. Then you're fucked and have to start all over again.
It's better to wait until the game is heavily discounted and patched up.
So no you don't get a mechanical watch for free. You get a mechanical watch if you drop another $1500. So $3000 in total. And which mechanical watch does it get you? It doesn't say.
I very much doubt it's "Swiss made" or even what that even means for a device whose innards were probably produced in some far East factory.
$1500 IS a lot for a watch. Especially one which will be bitrotten or obsolete within 2 years. It'll just be some worthless piece of crap gathering dust at the bottom of a drawer after that.
e.g. one that peels and chop a variety of vegetables - monotonous, boring, repetitive work where a limited amount of visual inspection (to find blemishes, rot etc.) could be programmed into it. The programming might involve washing, scrubbing, peeling and finally slicing / dicing the veg which is all fairly straightforward.
And devices could be made which can prepare a range of soups and sauces based up on some schedule of tipping ingredients into a pot, regulating the temperature of the pot, stirring etc. Again fairly straight forward. Also similar devices that baked, grilled or roasted items.
Anything which is repetitive, formulaic and generic in nature is a candidate for automation. It already happens on an industrial scale - ready meals and so on. But the problem of course is a kitchen is not a factory and it would fill with these damned appliances. You'd still need humans to feed the components into the machines, switch settings, inspect the meat / veg, serve, and plate up. Cleaning the machines would be a major pain in the ass. As would safety around these machines. As would making contingency plans when a machine broke.
I expect most chains would prefer that all of the above happened offsite on an industrial scale as they do already. They'd had a freezer full of chopped veg, sauces etc. that they just heat up. I expect most individual restaurants would only find a limited use for such devices for cutting potatoes or suchlike.
No, every day driving isn't filled with problems intractable for humans. Quite the opposite. The things which are hard for humans are reacting in time to apply brakes, anti-skid maneuvers and the usual foibles of tailgating, driving too fast etc. Which is why I said advanced driver assist is a better route to go and which does use the strengths of both human and computer.
I see the potential but this particular project has been popping in newspapers in one form or another for the last 30 years.
The best chance self drive has is on closed loops, e.g. airport terminal transfers where vehicles can drive separately than the other traffic in mostly predictable conditions. Even there there'll probably be some guy in a booth whose job it is to takeover if the car gets stuck, confused or breaks down.
On the public roads it would be better for vehicles to focus on advanced driver assistance - smart cruise control, emergency collision braking, hazard avoidance, lane tracking and niceties such as parallel park etc.
It's simply easier to read the PDF although the file size is enormous and you're basically looking at images of some yellowing old book which means lots of panning and zooming particularly on small devices. And forget reading it on an e-reader.
So yeah I think you could automate scanning of books, but the second step of getting it into EPUB format is the tricky part.