By analyzing the patterns in AI humans can beat them. There are no AI's flexible or dynamic enough to adapt themselves in a way that would continually force humans to think more dynamically. AI's are very static, and to defeat them you need to find the flaws in their static nature. Continually playing against a Chess AI will of course develop your ability to play Chess, but you will be improving against the AI algorithms, finding ways to beat the computer specifically. That doesn't necessarily make you better against human chess players. Unless we want our children to think statically, like machines, this is not a good idea. You'd be better off teaching them AI theory and how to reverse engineer an AI through interacting with it than to have them take the uneducated, brute force, route method of playing games with the AI until they stumble upon its weakness.
While you're all training your kids to be machines I think I'll give mine a toolbox and some engineering and science themed kits. We'll see who changes the world.
NFC is an almost entirely unrelated technology. Granted BlueTooth and NFC share some common features, but NFC is for other things. We use it for digital payment here in Japan for example - that's something you don't want going over BlueTooth. NFC is also good for various physical hot-spot applications. NFC also allows for physical queuing - something some fast food restaurants use for example. BlueTooth on the other-hand handles headsets and other peripherals, as well as a variety of inter-device communications. My phone has both BlueTooth and NFC, as do most phones here in Japan. To have both makes perfect sense.
I'm not sure, but EV is a common term here in Japan and I myself assumed it was overseas. Take the MiEV for example, it has EV right in the name: http://www.mitsubishi-motors.co.jp/i-miev/ .
Actually the information just isn't available in English. Aside from the Celmet site there are numerous documents on prototypes, samples, and working production models if you simply search for the name in Japanese: .
They've made prototypes and samples, the information just isn't fully available in English. Documentation on one of the samples: www.sei.co.jp/tr/pdf/energy/sei10498.pdf
NO! Celmet is their brand of super-porous metals, Celmet being a brand name. The name is composed of Cell and Metal, thusly Celmet. http://www.sei-toyama.co.jp/2-3.html They have made working samples too, but only the briefs are in English: www.sei.co.jp/tr/pdf/energy/sei10498.pdf .
The point here is precisely that he is a Linux developer and not a BSD developer - as in if BSD doesn't get more developers porting their work between Linux and BSD and maintaining compatible builds BSD is just going to continue fading into obscurity.
I got modded down for this comment - perhaps because I made what could have been taken as a negative comment about the Ubuntu community. I use Ubuntu and am loosely a part of the community - which contains a lot of people with bad opinions who put in little to no effort to make things better. The thing is those people are for the most part just ignored. That was my point. I have nothing against Ubuntu - I love it (I also love Debian).
Community? If you consider this any sort of community I feel you are mistaken. I think half the Slashdot users simply signed up so they could bicker without being ignored for posting as AC... Oh, and we get mod points so we can use our invisible hands to raise up the opinions we agree with and demolish the ones we don't. Perhaps if you had said "The Ubuntu Community" you'd have something closer to "a lot of wannabes and not a whole lot of doers" but even then I don't know why you'd care about the wannabes in the first place - just count the doers.
I was going to point that out but you did it very well. Apple pioneered no notion that "users can write programmable code". As for locking things down, they did just that - there was a huge legal episode when people started modifying Apple firmware and the results of that ended up in the establishment of a variety of laws. That legal spat is why emulators bundled with any original firmware, modified or not, without a license and direct consent from the creator of said firmware is illegal. I really wish I remembered the specifics of the case, but it was a classic example of a Jobs driven Apple actively trying to lock out would-be-innovator hackers.
These are contact coolers, just putting them out won't do much for ambient temperature. On top of that they cool progressively, essentially taking heat from one side of the element to the other. You'd need to position the hot side against something, that something would have to be cooler than ambient temperature, and since they are contact coolers you'd need to have your cooling target touching the pad. You can calculate power x efficiency all you want, if you don't understand how the element operates or the thermodynamics involved you're going to end up with a whole bunch of expensive tiles with wires sticking out.
How is that not expensive? A buy it now price of $16 for a 4cm square plate... that's a 25x25 grid for a square meter coming out to an even $10,000 per meter!? Or do you intend to tape them to everyones forehead and hook them up to the grid with a bunch of wire?
Peltier elements are not only expensive, but not very effective at cooling areas. If you had an array of PV panels you'd be better off having them power fans.
Of course if you had unlimited resources or knew of where to get unbelievably cheap PV panels and massive and amazingly efficient and large Peltier elements a PV array roof with a Peltier cooled floor in the middle of an area like this would be pretty awesome. It's a shame it's probably economically impossible.
I didn't mean for my statement to be all encompassing. Obviously different models will be better suited for different projects and different people. That's the reason we have different models in the first place, isn't it? Choose what works for you, but don't claim a method like the Waterfall is sure to fail just because it hasn't worked for you.
It's obvious you know absolutely nothing of what goes into game programming. Console game engines are often copied and modified, but as console game engines are highly tailored to their games the term "reused" is massively inappropriate. And it's not like we have tons of available libraries or easy memory management or anything either - things are often built from the ground up. Game programming for console systems requires an extremely high familiarity with the hardware, patches are usually out of the question so you need to get it right the first time, and are often built from the ground up. In many ways it is significantly harder to develop for a restricted platform than on the desktop. It's obvious you have absolutely no idea what you're talking about.
I've worked on a lot of projects here in Japan and I can tell you with absolute confidence you are wrong. Most console games are developed under a Waterfall model for example. A lot of embedded software as well. The Waterfall model works if you have developers who actually implement according to the designs and do it well. The Waterfall works in getting products to market. I'm convinced this has a big part to do with social and developer culture in Japan.
Perhaps another factor is how the Waterfall model is implemented here. We have planners for example - they do all the planning and they deal with inconsistencies that arise during implementation. Planner work -under- designers, but planners work -for- programmers. Furthermore, the Waterfall model is just used for the core application - peripheral features and post-release enhancements [kakuchou - kaizen] are rarely handled using the Waterfall model. In addition the implementation step is usually broken up between departments with a set of joining critical-passes - basically becoming a separate process in and of itself.
Slashdot Mirror
By analyzing the patterns in AI humans can beat them. There are no AI's flexible or dynamic enough to adapt themselves in a way that would continually force humans to think more dynamically. AI's are very static, and to defeat them you need to find the flaws in their static nature. Continually playing against a Chess AI will of course develop your ability to play Chess, but you will be improving against the AI algorithms, finding ways to beat the computer specifically. That doesn't necessarily make you better against human chess players. Unless we want our children to think statically, like machines, this is not a good idea. You'd be better off teaching them AI theory and how to reverse engineer an AI through interacting with it than to have them take the uneducated, brute force, route method of playing games with the AI until they stumble upon its weakness.
While you're all training your kids to be machines I think I'll give mine a toolbox and some engineering and science themed kits. We'll see who changes the world.
Fully encrypted NFC has been available since well before BlueTooth.
EG: http://en.wikipedia.org/wiki/FeliCa
Encryption has been an integrated part of NFC systems since their inception in the 80's...
EG: http://en.wikipedia.org/wiki/FeliCa
NFC is an almost entirely unrelated technology. Granted BlueTooth and NFC share some common features, but NFC is for other things. We use it for digital payment here in Japan for example - that's something you don't want going over BlueTooth. NFC is also good for various physical hot-spot applications. NFC also allows for physical queuing - something some fast food restaurants use for example. BlueTooth on the other-hand handles headsets and other peripherals, as well as a variety of inter-device communications. My phone has both BlueTooth and NFC, as do most phones here in Japan. To have both makes perfect sense.
...A recent Google+ Post by Linus Torvalds...
When the fuck did this happen!?
I'm not sure, but EV is a common term here in Japan and I myself assumed it was overseas. Take the MiEV for example, it has EV right in the name: http://www.mitsubishi-motors.co.jp/i-miev/ .
Electric Vehicle
Slashdot UTF8 FAIL!
Actually the information just isn't available in English. Aside from the Celmet site there are numerous documents on prototypes, samples, and working production models if you simply search for the name in Japanese: .
They've made prototypes and samples, the information just isn't fully available in English. Documentation on one of the samples: www.sei.co.jp/tr/pdf/energy/sei10498.pdf
NO! Celmet is their brand of super-porous metals, Celmet being a brand name. The name is composed of Cell and Metal, thusly Celmet. http://www.sei-toyama.co.jp/2-3.html They have made working samples too, but only the briefs are in English: www.sei.co.jp/tr/pdf/energy/sei10498.pdf .
The point here is precisely that he is a Linux developer and not a BSD developer - as in if BSD doesn't get more developers porting their work between Linux and BSD and maintaining compatible builds BSD is just going to continue fading into obscurity.
I got modded down for this comment - perhaps because I made what could have been taken as a negative comment about the Ubuntu community. I use Ubuntu and am loosely a part of the community - which contains a lot of people with bad opinions who put in little to no effort to make things better. The thing is those people are for the most part just ignored. That was my point. I have nothing against Ubuntu - I love it (I also love Debian).
Community? If you consider this any sort of community I feel you are mistaken. I think half the Slashdot users simply signed up so they could bicker without being ignored for posting as AC... Oh, and we get mod points so we can use our invisible hands to raise up the opinions we agree with and demolish the ones we don't. Perhaps if you had said "The Ubuntu Community" you'd have something closer to "a lot of wannabes and not a whole lot of doers" but even then I don't know why you'd care about the wannabes in the first place - just count the doers.
So it took Debian threatening to kick him out that got Stallman off his ass?
Works for me.
If only you didn't post AC and I had mod points!
You sir (or madam?) have made my day.
A lot of really good companies make just that. Did you not bother to search?
I was going to point that out but you did it very well. Apple pioneered no notion that "users can write programmable code". As for locking things down, they did just that - there was a huge legal episode when people started modifying Apple firmware and the results of that ended up in the establishment of a variety of laws. That legal spat is why emulators bundled with any original firmware, modified or not, without a license and direct consent from the creator of said firmware is illegal. I really wish I remembered the specifics of the case, but it was a classic example of a Jobs driven Apple actively trying to lock out would-be-innovator hackers.
These are contact coolers, just putting them out won't do much for ambient temperature. On top of that they cool progressively, essentially taking heat from one side of the element to the other. You'd need to position the hot side against something, that something would have to be cooler than ambient temperature, and since they are contact coolers you'd need to have your cooling target touching the pad. You can calculate power x efficiency all you want, if you don't understand how the element operates or the thermodynamics involved you're going to end up with a whole bunch of expensive tiles with wires sticking out.
Excellent point.
How is that not expensive? A buy it now price of $16 for a 4cm square plate... that's a 25x25 grid for a square meter coming out to an even $10,000 per meter!? Or do you intend to tape them to everyones forehead and hook them up to the grid with a bunch of wire?
Peltier elements are not only expensive, but not very effective at cooling areas. If you had an array of PV panels you'd be better off having them power fans.
Of course if you had unlimited resources or knew of where to get unbelievably cheap PV panels and massive and amazingly efficient and large Peltier elements a PV array roof with a Peltier cooled floor in the middle of an area like this would be pretty awesome. It's a shame it's probably economically impossible.
I didn't mean for my statement to be all encompassing. Obviously different models will be better suited for different projects and different people. That's the reason we have different models in the first place, isn't it? Choose what works for you, but don't claim a method like the Waterfall is sure to fail just because it hasn't worked for you.
It's obvious you know absolutely nothing of what goes into game programming. Console game engines are often copied and modified, but as console game engines are highly tailored to their games the term "reused" is massively inappropriate. And it's not like we have tons of available libraries or easy memory management or anything either - things are often built from the ground up. Game programming for console systems requires an extremely high familiarity with the hardware, patches are usually out of the question so you need to get it right the first time, and are often built from the ground up. In many ways it is significantly harder to develop for a restricted platform than on the desktop. It's obvious you have absolutely no idea what you're talking about.
I've worked on a lot of projects here in Japan and I can tell you with absolute confidence you are wrong. Most console games are developed under a Waterfall model for example. A lot of embedded software as well. The Waterfall model works if you have developers who actually implement according to the designs and do it well. The Waterfall works in getting products to market. I'm convinced this has a big part to do with social and developer culture in Japan.
Perhaps another factor is how the Waterfall model is implemented here. We have planners for example - they do all the planning and they deal with inconsistencies that arise during implementation. Planner work -under- designers, but planners work -for- programmers. Furthermore, the Waterfall model is just used for the core application - peripheral features and post-release enhancements [kakuchou - kaizen] are rarely handled using the Waterfall model. In addition the implementation step is usually broken up between departments with a set of joining critical-passes - basically becoming a separate process in and of itself.