This is a good idea in theory, but the big problem is that wine is a godawful mess which breaks every time you upgrade it.
Correct. Not only is it nearly impossible to install.NET Framework 3.5 under Wine, a pre-requisite for XNA-based games like Magicka, each subsequent version of Wine breaks things that were already working. e.g.: games like HALO don't work on Wine 1.1.25 or later because the memory manager changes broke things that depend on running at fixed addresses.
I think it's a chicken and egg issue, really: the sales figures are crap because there are comparatively few *nix versions to sell.
If you look at the first few Humble Bundle packs (in which all titles were available for Windows, linux and OS X) the figures were closer to 60% Windows, 40% linux and OS X. Unfortunately the more recent Humble Bundles are just clearance packs and 90% of the titles are Windows-only that are additionally past their shelf life. Very disappointing, Wolfire.
I'd be curious to see the per-platform breakdown of sales on places like GoG.
The minute we give robots the ability to develop emotions they're going to realise how inconsistent all us humans are, get frustrated and then go into a fit of rage to kill us all.
The thing is, PCIe SSDs don't load games or common application data any faster than current incumbents—or even consumer-grade SSDs from five years ago.
The SATA bus gets saturated for sequential reads and writes so of course PCIe SSDs can trump SATA SSDs here. But, generally speaking, the controller silicon on PCIe SSDs is no faster than their SATA counterparts so they offer no improvement for random reads and writes. Still orders of magnitude better than spinning rust, though.
Have you ever owned apple hardware?
I've modded more than a few devices, more than a few times, and Apple has no problem with it...
Have you ever owned an iMac from this decade? No screws on the outside with which to open it up - you have to buy a 3rd party cutter disc to cut the glue between the front glass and chassis so you can lift the whole unit out to work on it. The latest models can't even have their desk stands removed to put them on a Vesa mount - you have to preorder one with the Vesa mount fitted already!
Not necessarily. A larger car can have bigger crumple zones. If its crumple zones are twice the size of the small car, then the acceleration that you'll experience in the collision is a lot less and so there's a greater chance everyone will survive (assuming that the relative impact speeds will be the same).
Don't let facts get in the way of a good story.:) While survivability is about equal for SUV vs SUV and car vs car impacts, studies have shown that in SUV vs car impacts the passengers of the car are 7.6 times more likely to die.
Armed with this information an autonomous vehicle trying to protect everybody should: (a) choose the impact with the least inertia for all concerned (i.e.: go for the car travelling in almost the same direction as the autonomous vehicle as opposed a car travelling in an opposite direction) and (b) for a choice of head-on impacts, prioritize impacting the car with a mass closest to its own. An autonomous vehicle biased towards protecting its own driver should target the smaller vehicle... but this will inevitably lead to "I've got the biggest autonomous vehicle" wars with people trying to protect themselves from other vehicles as we've seen happen with SUVs.
"Stop using your ISP's DNS" is not always the right answer.
If I use Google's public DNS servers it breaks content distribution networks like Akamai. For example, if I use Google Public DNS then *.phobos.apple.com addresses for iOS and OSX updates resolve to IPs inside NTT (Tokyo, Japan) and downloads are exceedingly slow (high latency, dropped packets, etc.). If I use my ISP's DNS server it just so happens they host a set of Akamai nodes and the *.phobos.apple.com addresses will resolve to IPs only 2 or 3 hops away, so downloads will saturate my SDSL connection.
Comcast should just acknowledge that they've fucked up and fix their servers.
Just a casual browsing of the iTunes App Store makes me wonder what the real story is. If you click on Show All Versions for each of the free/paid iPhone/iPad versions of CandySwipe they were first published in May 2012 (not even close to 2010), abandoned, then there were updates to all of them around 27/28 Jan 2014, and now there is all this debate. Was there a PC/Android version published earlier?
Yeah, describing it as "handheld" is kind of misleading. The photo in TFA shows *just* the handheld part, there's a much larger piece of equipment attached via cable and worn backpack-style...
Should Jade Rabbit make a full recovery, it would cap another success for space exploration, which has seen NASA's Opportunity Mars rover, currently exploring the red planet, far outlast its expected lifespan."
Opportunity far outlived its projected 90 day operational lifetime. Jade Rabbit was supposed to go 3 months and has already gone belly-up just a month into it.
Or if you're me, the worst phone you could ever imagine (battery life, robustness, size, speech quality, too many button presses until i can do what i want to achieve).
Put a hardware driver author in front of a documentation pack and a compiler, and tell him to write a driver, and he'll tell you to fuck off.
My how things have changed. I remember being handed register documentation for StarPort 16-, 32- and 64-port serial cards and being asked to write FOSSIL drivers for them. And I had to supply my own compiler and logic analyser.
If you only use hashing then, yes, you are open to Rainbow Table attacks because common passwords can be immediately exposed.
But hashing is not salted hashing. Best practice uses salted hashing with a unique salt for each user, thus making Rainbow Table attacks useless - you have to generate a whole new set of Rainbow Tables for each known salt which is a whole lot more work for an attacker.
Warcraft: Orcs and Humans put real-time strategy on the map, and Diablo set the standard for action RPGs.
Bullshit. Warcraft launched in 1994, following Dune and Dune II (1992). The Dunes in turn were influenced by TechnoSoft's Herzog (1988) and Herzog Zwei (1989) on the Sega Genesis/Megadrive consoles. I'm sure there are plenty of other examples.
Don't tell all my iOS devices that then because they must have missed the memo. They're still using ActiveSync successfully to this very day... and on *free* Gmail accounts.
Slashdot Mirror
This is a good idea in theory, but the big problem is that wine is a godawful mess which breaks every time you upgrade it.
Correct. Not only is it nearly impossible to install .NET Framework 3.5 under Wine, a pre-requisite for XNA-based games like Magicka, each subsequent version of Wine breaks things that were already working. e.g.: games like HALO don't work on Wine 1.1.25 or later because the memory manager changes broke things that depend on running at fixed addresses.
Huge effort for nothing.
I think it's a chicken and egg issue, really: the sales figures are crap because there are comparatively few *nix versions to sell.
If you look at the first few Humble Bundle packs (in which all titles were available for Windows, linux and OS X) the figures were closer to 60% Windows, 40% linux and OS X. Unfortunately the more recent Humble Bundles are just clearance packs and 90% of the titles are Windows-only that are additionally past their shelf life. Very disappointing, Wolfire.
I'd be curious to see the per-platform breakdown of sales on places like GoG.
Thus the ASUS Transformer and its ilk.
The minute we give robots the ability to develop emotions they're going to realise how inconsistent all us humans are, get frustrated and then go into a fit of rage to kill us all.
The thing is, PCIe SSDs don't load games or common application data any faster than current incumbents—or even consumer-grade SSDs from five years ago.
The SATA bus gets saturated for sequential reads and writes so of course PCIe SSDs can trump SATA SSDs here. But, generally speaking, the controller silicon on PCIe SSDs is no faster than their SATA counterparts so they offer no improvement for random reads and writes. Still orders of magnitude better than spinning rust, though.
Have you ever owned apple hardware? I've modded more than a few devices, more than a few times, and Apple has no problem with it...
Have you ever owned an iMac from this decade? No screws on the outside with which to open it up - you have to buy a 3rd party cutter disc to cut the glue between the front glass and chassis so you can lift the whole unit out to work on it. The latest models can't even have their desk stands removed to put them on a Vesa mount - you have to preorder one with the Vesa mount fitted already!
Picard? Is that you?
Disappointing that the Star Trek tie-in was mentioned but the link was omitted...
National Ignition Facility provides backdrop for "Star Trek: Into Darkness"
I think you meant: W0rldP4assw0rdD4y!
Not necessarily. A larger car can have bigger crumple zones. If its crumple zones are twice the size of the small car, then the acceleration that you'll experience in the collision is a lot less and so there's a greater chance everyone will survive (assuming that the relative impact speeds will be the same).
Don't let facts get in the way of a good story. :) While survivability is about equal for SUV vs SUV and car vs car impacts, studies have shown that in SUV vs car impacts the passengers of the car are 7.6 times more likely to die.
Armed with this information an autonomous vehicle trying to protect everybody should: (a) choose the impact with the least inertia for all concerned (i.e.: go for the car travelling in almost the same direction as the autonomous vehicle as opposed a car travelling in an opposite direction) and (b) for a choice of head-on impacts, prioritize impacting the car with a mass closest to its own. An autonomous vehicle biased towards protecting its own driver should target the smaller vehicle... but this will inevitably lead to "I've got the biggest autonomous vehicle" wars with people trying to protect themselves from other vehicles as we've seen happen with SUVs.
REF: http://www.consumerreports.org.../p
"Stop using your ISP's DNS" is not always the right answer.
If I use Google's public DNS servers it breaks content distribution networks like Akamai. For example, if I use Google Public DNS then *.phobos.apple.com addresses for iOS and OSX updates resolve to IPs inside NTT (Tokyo, Japan) and downloads are exceedingly slow (high latency, dropped packets, etc.). If I use my ISP's DNS server it just so happens they host a set of Akamai nodes and the *.phobos.apple.com addresses will resolve to IPs only 2 or 3 hops away, so downloads will saturate my SDSL connection.
Comcast should just acknowledge that they've fucked up and fix their servers.
Just a casual browsing of the iTunes App Store makes me wonder what the real story is. If you click on Show All Versions for each of the free/paid iPhone/iPad versions of CandySwipe they were first published in May 2012 (not even close to 2010), abandoned, then there were updates to all of them around 27/28 Jan 2014, and now there is all this debate. Was there a PC/Android version published earlier?
Yeah, describing it as "handheld" is kind of misleading. The photo in TFA shows *just* the handheld part, there's a much larger piece of equipment attached via cable and worn backpack-style...
http://research.ict.csiro.au/events/event-gallery/cebit-germany/cebit-germany-2012/DSC_3736.JPG/image_view_fullscreen
Should Jade Rabbit make a full recovery, it would cap another success for space exploration, which has seen NASA's Opportunity Mars rover, currently exploring the red planet, far outlast its expected lifespan."
Opportunity far outlived its projected 90 day operational lifetime. Jade Rabbit was supposed to go 3 months and has already gone belly-up just a month into it.
Not that I really want to continue with AMD under linux, but Linus should give them the middle finger too.
Or if you're me, the worst phone you could ever imagine (battery life, robustness, size, speech quality, too many button presses until i can do what i want to achieve).
I see you've never owned a Motorola RAZR then.
The scaly texture conceals small holes in the material where water is sucked in.
I think the /. editors have been sucked in.
Put a hardware driver author in front of a documentation pack and a compiler, and tell him to write a driver, and he'll tell you to fuck off.
My how things have changed. I remember being handed register documentation for StarPort 16-, 32- and 64-port serial cards and being asked to write FOSSIL drivers for them. And I had to supply my own compiler and logic analyser.
You haven't met the unholy abortion that is iTunes 11. Wish I could revert that update.
Assuming you're actually serious, what happens when your page is requested with: ?id=0;%20drop%20table%20catalog;
Suddenly your query gets transformed to: select * from catalog where id=0; drop table catalog;
If you only use hashing then, yes, you are open to Rainbow Table attacks because common passwords can be immediately exposed.
But hashing is not salted hashing. Best practice uses salted hashing with a unique salt for each user, thus making Rainbow Table attacks useless - you have to generate a whole new set of Rainbow Tables for each known salt which is a whole lot more work for an attacker.
^^ This. You beat me to it.
Bullshit. Warcraft launched in 1994, following Dune and Dune II (1992). The Dunes in turn were influenced by TechnoSoft's Herzog (1988) and Herzog Zwei (1989) on the Sega Genesis/Megadrive consoles. I'm sure there are plenty of other examples.
Yes, Thunderbird + Google Contacts add-on is the duck's nuts.
Don't tell all my iOS devices that then because they must have missed the memo. They're still using ActiveSync successfully to this very day ... and on *free* Gmail accounts.