Yes but... you destroy your book in the process. The ideal scanner would be one which allows a book to be scanned without destroying it and could correct for page distortion and other artifacts.
Considering security and putting it above all else are two different things.
The Linux kernel has quite strong security but if every single thing that went into the kernel had to justify its security first and foremost then development would slow to a crawl. If you want to see the kind of impact that might have then look at something like OpenBSD.
I don't see why you would assume that. It wouldn't be the first time a paid-for streaming / cloud service from a prominent, trusted source has gone titsup. Why might they discontinue such a service? They might if it proves to be expensive / unreliable / unprofitable / unpopular, or they get embroiled in rights / broadcast legal fights, or maybe someone like Netflix pays them a hatful of money for exclusive access.
So the plug could be pulled and that's that. The BBCs archive of programmes won't disappear but your access to them might.
Absolutely true. Because Windows (the desktop part anyway) and Android tend to give the user more freedom about the software they install on their own devices.
And with that greater freedom comes the freedom to do really stupid things like install warez and then act all surprised when it turns out to be a trojan of some kind.
Well the protection in this case is for browsers to stop shipping 32-bit only binaries when the OS is predominantly 64-bit. During the download / upgrade process, detect if the OS is 64-bit and install the 64-bit binary or at least ask the user to stop using the 32-bit binary and manually upgrade.
I expect the main reason 32-bit has been around for so long is the extra support effort of building two binaries and some issues with plugins and suchlike. Plugins are effectively deprecated these days (and besides the plugin runs in its own separate exe) so the aren't many reasons to stick with 32-bit.
It'd be interesting to observe if there is a performance difference between 32-bit / 64-bit. On the one hand a 64-bit binary doesn't have call through a Win32 thunking layer which could impact on rendering performance and the larger address space means it doesn't have to be so aggressive with garbage collection. But on the other it might consume more memory for the same content and the JS engine in particular might have different performance characteristics (JIT, pointer size etc.) which have to be finetuned.
There is a suspicion that Activision are doing this to move their corporate headquarters to Ireland. King is already in Ireland and the size of the acquisition could mean Activision would headquarter there and benefit from lower corporate taxes. It'll probably save them billions. Good for Ireland, not so good for the US.
Of course they might be doing it because of Candy Crush but I suspect King is grossly overvalued and Activision know it - but again, tax inversion.
The issuer (by here I mean Visa + Bank) skims 1-2% off every transaction in merchant fees to cover their costs. If someone is spending $20,000 on their card then the issuer has made $200-400 for simply moving money around between a few columns.
But obviously they'd prefer that if a card holder borrows $20,000 over the year and struggles to pay off the debt so they can charge them ursurious rates of interest and other fees.
That said, I'm sure it's a fine line and credit card companies have some kind of blended risk model to ensure that they're always maximizing their return and minimizing the number of deadbeats they attract.
More to the point, most terrorists, paedophiles and assorted other lawbreakers aren't computer geniuses. Even if they think they're practicing good security, chances are they're still making mistakes - their pattern of activity, the sites they frequent, the software they use, the people they converse with, their nuances of grammar and spelling. All things that can be exploited to find out who they are. Even computer hacking groups get busted from being careless - it only takes one slip-up and game over.
And that's the people who are practicing good security. Probably the majority of paedos and other evildoers are idiots who leave clues all over the place and given the nature of their crimes, the police / security services are sufficiently motivated to go after them.
As for the UK's laws, it's frankly preposterous and hopefully it fails because it is basically unenforceable.
One time pads aren't breakable. Not unless the random data isn't actually random, or because someone reused the same random data to xor more than one message.
Gateway were basically forerunners to Dell - offer a complete functioning solution for an affordable price (way lower than a store) but one assembled from cheap OEM components. My parents bought one and it worked fine but if you looked at any individual component it was very low spec stuff.
At the time (in the UK), the main alternatives were to order a computer from Dabs or Evesham Micro, or buy an execrable Packard Bell / Advent computer from PC world. None of these options were as cheap as a Gateway by a long shot so all things considered Gateway had a positive effect on the market. It's weird that they fell by the wayside but after reading the wikipedia page it's clear they were completely rudderless, sinking money on vanity projects and weird acquisitions.
Goto is a perfectly valid instruction providing you know when to use it. The typical use would be to jump into some teardown code at the bottom of a function or to escape out of some nested loop. Either way provdes more succinct and involves less code than the alternative. I assume every single kernel developer is capable of knowing when best to use it and they wouldn't have to worry about issues with c++ constructors either.
Well it could happen if there was a race condition (e.g. p is shared with another thread) and p changed from not-NULL to NULL between the first test & else jump. But if that were the case then there is something seriously screwed up with code, starting with the person who wrote it.
More ordinarily you have assume that the compiler generates correct code and if it doesn't, particularly on something as trivial as an if-else then really you shouldn't be using that compiler.
Atom is basically a clone of Sublime and Brackets. So if you like those other editors you'll probably like Atom.
I use it occasionally because I work on a very mixed project with lots of file types which it handles fairly well. But I don't see the attraction of these editors otherwise. If you edit code all day you should probably be using a proper IDE and if you're just casually editing some random file there are more lightweight editors around.
Then you're not looking very closely. The game doesn't feature a single "loading..." pause and all the cutscenes are in-game. The very first scene in a diner allows you to walk around and read the text off newspapers or stare closely into someone's face if you want. That's the level of detail throughout the game. The poly count is higher, the textures are higher, every cutscene is in-game and when you're out in the city standing on a rooftop you can see all the way to the other side. This is in stark contrast to earlier AK games where loading was a frequent occurrence, cutscenes were movies and every zone was conspicuously distinct.
The thing is, Android *does* run with a mouse and a keyboard and has done so for a very long time. Look at the likes of the ASUS transformer tablets which have been out for a long time. Lots of office apps exist on Android. I even recall plugging a mouse / keyboard into a MIPS set top box running Android some 6 or 7 years ago.
That said, keyboard / mouse support has always been basic. Part of the reason for this is that the Google didn't push the support and therefore many apps don't do much with it. If Google released a desktop mode for Android and APIs for hotkeys, tooltips, menus, tabbing, cursor shapes etc. then it's likely that devices in those form factors would be more prevalent and more apps like browsers, word processors etc. would add decent support for it.
It would certainly be less effort than writing and supporting an entirely different OS as Google have done with such limited success.
Google shouldn't have bothered with ChromeOS in the first place. It just confused everyone that they shipped two mutually incompatible operating systems that overlapped over the same problem space.
There is a vast difference in the engine apparent the moment you stand on a rooftop and look out for miles in each direction, or where you walk through a door and the game keeps going instead of stopping at a load screen. Or when there is a cutscene and rather than play a video, the cutscene happens within the game. There are a few moments where there are transitions, e.g. going down a lift where its obviously loading up something but generally it feels seamless.
So Batman doesn't need 12GB but its recommended to avoid paging. What should we make of this other than the fact that if you turn all the settings up to max it needs a lot of memory.
Yes I can imagine it - a rapid push to develop new early warning / detection and tracking technology that can counter such aircraft. Probably exactly what Russia and China will do in response to aircraft which can evade their existing systems.
I suppose I can see the benefit of modularity for maintaining a device if a piece of it breaks. But that adds bulk, and to the cost of the handset in total. And I doubt it makes the device reusable or future proof. The article even ends by expressing doubt about backwards / forwards compatibility on that score.
And for the price it should be exceptional. Fucking spectacular in fact. You don't even get a keyboard despite the absurd premium of the tablet. Personally I think I'd wait for other manufacturers to catch up and avail of the substantially cheaper prices for equivalent performance.
Slashdot Mirror
Yes but... you destroy your book in the process. The ideal scanner would be one which allows a book to be scanned without destroying it and could correct for page distortion and other artifacts.
The Linux kernel has quite strong security but if every single thing that went into the kernel had to justify its security first and foremost then development would slow to a crawl. If you want to see the kind of impact that might have then look at something like OpenBSD.
I'd be surprised if they manage to muster more than 2-300. And if they do anything remotely illegal it'll be the cops who get the lulz.
So the plug could be pulled and that's that. The BBCs archive of programmes won't disappear but your access to them might.
And with that greater freedom comes the freedom to do really stupid things like install warez and then act all surprised when it turns out to be a trojan of some kind.
I expect the main reason 32-bit has been around for so long is the extra support effort of building two binaries and some issues with plugins and suchlike. Plugins are effectively deprecated these days (and besides the plugin runs in its own separate exe) so the aren't many reasons to stick with 32-bit.
It'd be interesting to observe if there is a performance difference between 32-bit / 64-bit. On the one hand a 64-bit binary doesn't have call through a Win32 thunking layer which could impact on rendering performance and the larger address space means it doesn't have to be so aggressive with garbage collection. But on the other it might consume more memory for the same content and the JS engine in particular might have different performance characteristics (JIT, pointer size etc.) which have to be finetuned.
Of course they might be doing it because of Candy Crush but I suspect King is grossly overvalued and Activision know it - but again, tax inversion.
But obviously they'd prefer that if a card holder borrows $20,000 over the year and struggles to pay off the debt so they can charge them ursurious rates of interest and other fees.
That said, I'm sure it's a fine line and credit card companies have some kind of blended risk model to ensure that they're always maximizing their return and minimizing the number of deadbeats they attract.
And that's the people who are practicing good security. Probably the majority of paedos and other evildoers are idiots who leave clues all over the place and given the nature of their crimes, the police / security services are sufficiently motivated to go after them.
As for the UK's laws, it's frankly preposterous and hopefully it fails because it is basically unenforceable.
One time pads aren't breakable. Not unless the random data isn't actually random, or because someone reused the same random data to xor more than one message.
At the time (in the UK), the main alternatives were to order a computer from Dabs or Evesham Micro, or buy an execrable Packard Bell / Advent computer from PC world. None of these options were as cheap as a Gateway by a long shot so all things considered Gateway had a positive effect on the market. It's weird that they fell by the wayside but after reading the wikipedia page it's clear they were completely rudderless, sinking money on vanity projects and weird acquisitions.
Goto is a perfectly valid instruction providing you know when to use it. The typical use would be to jump into some teardown code at the bottom of a function or to escape out of some nested loop. Either way provdes more succinct and involves less code than the alternative. I assume every single kernel developer is capable of knowing when best to use it and they wouldn't have to worry about issues with c++ constructors either.
More ordinarily you have assume that the compiler generates correct code and if it doesn't, particularly on something as trivial as an if-else then really you shouldn't be using that compiler.
Vanity TV basically. It livestreams people playing games.
I use it occasionally because I work on a very mixed project with lots of file types which it handles fairly well. But I don't see the attraction of these editors otherwise. If you edit code all day you should probably be using a proper IDE and if you're just casually editing some random file there are more lightweight editors around.
Then you're not looking very closely. The game doesn't feature a single "loading..." pause and all the cutscenes are in-game. The very first scene in a diner allows you to walk around and read the text off newspapers or stare closely into someone's face if you want. That's the level of detail throughout the game. The poly count is higher, the textures are higher, every cutscene is in-game and when you're out in the city standing on a rooftop you can see all the way to the other side. This is in stark contrast to earlier AK games where loading was a frequent occurrence, cutscenes were movies and every zone was conspicuously distinct.
That said, keyboard / mouse support has always been basic. Part of the reason for this is that the Google didn't push the support and therefore many apps don't do much with it. If Google released a desktop mode for Android and APIs for hotkeys, tooltips, menus, tabbing, cursor shapes etc. then it's likely that devices in those form factors would be more prevalent and more apps like browsers, word processors etc. would add decent support for it.
It would certainly be less effort than writing and supporting an entirely different OS as Google have done with such limited success.
I guess you haven't played the game if you see no improvements in the graphics. It's one of the best looking games there is on the PC at present.
Google shouldn't have bothered with ChromeOS in the first place. It just confused everyone that they shipped two mutually incompatible operating systems that overlapped over the same problem space.
There is a vast difference in the engine apparent the moment you stand on a rooftop and look out for miles in each direction, or where you walk through a door and the game keeps going instead of stopping at a load screen. Or when there is a cutscene and rather than play a video, the cutscene happens within the game. There are a few moments where there are transitions, e.g. going down a lift where its obviously loading up something but generally it feels seamless.
So Batman doesn't need 12GB but its recommended to avoid paging. What should we make of this other than the fact that if you turn all the settings up to max it needs a lot of memory.
Apple has bought in a lot of stuff. Even iTunes started life as a product called SoundJam.
Yes I can imagine it - a rapid push to develop new early warning / detection and tracking technology that can counter such aircraft. Probably exactly what Russia and China will do in response to aircraft which can evade their existing systems.
I suppose I can see the benefit of modularity for maintaining a device if a piece of it breaks. But that adds bulk, and to the cost of the handset in total. And I doubt it makes the device reusable or future proof. The article even ends by expressing doubt about backwards / forwards compatibility on that score.
And for the price it should be exceptional. Fucking spectacular in fact. You don't even get a keyboard despite the absurd premium of the tablet. Personally I think I'd wait for other manufacturers to catch up and avail of the substantially cheaper prices for equivalent performance.