In addition to the more obviously darwinnian examples of human evolution, there are also some that are more subtle.
The average height of the human population (especially in the western world) is increasing. IQ tests are renormed to be more difficult every year. Diabetes continues to become more prevalent as medical technology makes them more likely to be able to have kids.
All of these can be seens a selection (or lack of selection) in action.
This service would be much easier for somebody like google or altavista to provide. If a company starts making money at this, I'd expect the search engine boys to come in and offer to do the same thing for less.
Imagine trying to figure out how to design a good firewall in the days before the internet became popular.
Security measures must be tested. Who knows what works well? A few weak molecular bonds which break when exposed to sunlight? Something that crumbles when exposed to oxygen? Or will they simply be built to only consume a specific sort of 'food', normally found only in laboratories?
Having nanites more powerfull that nature's bacteria would be an intersting problem to have. But bacteria have been evolving for a long, long, time. I think it'll be a while before we need to start building antibodies.
You can. And when the legal dust settled, it would be determined that you had no right to _use_ the software. You might, in theory, get slapped with an injunction against continued use of the software.
Consider the case that you simply were not aware that the work was GPL'd. Upon discovering that you were using it without permission, you'd be legally obligated to do one of two things. Cease use, or start distributing the source. Going forward, either would be legal. (And the original action of using the code was illegal; ignorance is no excuse)
In their defence, there is some special technology involved in legal air-cellular. As mentioned elsewhere, there are technical problems with using normal cell phones in the air, both w.r.t. to aircraft operation, and w.r.t. cell phone operation.
w.r.t. cell phone operation, the FAA doesn't care about using cell phones in, say, a light plane, as long as the pilot doesn't mind. The FCC, on the other hand... the FCC license that is associated with a standard cell phone is for terrestrial use only. Having one on had as back up agains in-flight emergency is recommended. Just don't turn it on until it is an emergency.
Legal air cellular uses something to prevent you from bothering lots of cells at once. It is probably a specially directed antenna and/or more aggressive power reduction technology.
None of this is to say that $3.00 a minute is a fair price though.
The edge _is_ and atom wide. At least right after you break it. Over time the edge dissipates. For transmission electron microscopy, you need a realy thin sample, and such disposable "break and use once" knives are common. Stephenson is cool, but you shouldn't take his tech too seriously.
Now, STM is something totally different. It only works with conductive (and semi-conductive, for your advanced chip design research buffs) materials. SFM works with anything. Both SFT and STM can be seen as first draft nanotech manipulators.
Re:Try Both (thru PHP)
on
ASP or JSP?
·
· Score: 1
Server side Java should be more than JSP, which means that you need some plan and organization.
It is easy to put too much functionality in JSP. Think of it as a template language with various flavors of Java classes for the backend. It if is mostly Java code it should be a servlet. I don't know if there is an equivalent rule in MS land.
One division that was recommended by a senior guy, who recently came on board, and which makes a lot of sense to me, is to have JSP 'views' with a servlet 'controller'. (Ala MVC) The controller uses a ResourceDispatcher.include() to get the views that it needs, passing them data as request attributes. We'll be trying this. I liked when I heard about it, and it has only grown on me since.
This also means that specialized HTML/presentation people can hack the JSPs without being as likely to fsck things up.
Damascus steel is forged by folding, as are the traditional oriental blades. I think that this is a case of parellel evolution, but I'm not completely certain.
The oriental blades have two parts - a core and an outer skin. Both are folded multiple times. The outer skin is high carbon, (to hold an edge) the core is milder steel (for flexibility). This doesn't matter much for knives, but is essential if you want a katana that you can shave with and that doesn't crack when hitting a bone.
In addition to the mutiple types of steel, traditional blades are differentially tempered. A clay shell is put on the blade, the clay is thinnest on the edge. The entire unit is heated past the curie point and quenched. The Edge has the least amount of clay, so the quenching cools it the fastest. This makes the edge hard (and sharp) without making the rest of the blade brittle.
Continuing this lecture, for anybody still with us, the edge and the remainder of the skin have two distinct tempers with two distinct crystal structures. The boundary between these two areas is a visible temper line. Cheap imitations will have etched onto them something vaguely similar to a temper line for the sake of authenticity. The temper line is intentially wavy to help keep cracks from spreading.
Build a distributed fileshare in which each node uses it's neighbors as caches/redistribution point. Initially worry about automatic mirroring, then add support for file locks and such.
Besides a better distributed filesystem, this could also be seen as a napster/gnutella next generation. Go heavy on the fault tolerance and decentralization.
Slashdot Mirror
The average height of the human population (especially in the western world) is increasing. IQ tests are renormed to be more difficult every year. Diabetes continues to become more prevalent as medical technology makes them more likely to be able to have kids.
All of these can be seens a selection (or lack of selection) in action.
Seriously, don't they already have the database?
Security measures must be tested. Who knows what works well? A few weak molecular bonds which break when exposed to sunlight? Something that crumbles when exposed to oxygen? Or will they simply be built to only consume a specific sort of 'food', normally found only in laboratories?
Having nanites more powerfull that nature's bacteria would be an intersting problem to have. But bacteria have been evolving for a long, long, time. I think it'll be a while before we need to start building antibodies.
Consider the case that you simply were not aware that the work was GPL'd. Upon discovering that you were using it without permission, you'd be legally obligated to do one of two things. Cease use, or start distributing the source. Going forward, either would be legal. (And the original action of using the code was illegal; ignorance is no excuse)
w.r.t. cell phone operation, the FAA doesn't care about using cell phones in, say, a light plane, as long as the pilot doesn't mind. The FCC, on the other hand... the FCC license that is associated with a standard cell phone is for terrestrial use only. Having one on had as back up agains in-flight emergency is recommended. Just don't turn it on until it is an emergency.
Legal air cellular uses something to prevent you from bothering lots of cells at once. It is probably a specially directed antenna and/or more aggressive power reduction technology.
None of this is to say that $3.00 a minute is a fair price though.
The edge _is_ and atom wide. At least right after you break it. Over time the edge dissipates. For transmission electron microscopy, you need a realy thin sample, and such disposable "break and use once" knives are common. Stephenson is cool, but you shouldn't take his tech too seriously.
Now, STM is something totally different. It only works with conductive (and semi-conductive, for your advanced chip design research buffs) materials. SFM works with anything. Both SFT and STM can be seen as first draft nanotech manipulators.
Server side Java should be more than JSP, which means that you need some plan and organization.
It is easy to put too much functionality in JSP. Think of it as a template language with various flavors of Java classes for the backend. It if is mostly Java code it should be a servlet. I don't know if there is an equivalent rule in MS land.
One division that was recommended by a senior guy, who recently came on board, and which makes a lot of sense to me, is to have JSP 'views' with a servlet 'controller'. (Ala MVC) The controller uses a ResourceDispatcher.include() to get the views that it needs, passing them data as request attributes. We'll be trying this. I liked when I heard about it, and it has only grown on me since.
This also means that specialized HTML/presentation people can hack the JSPs without being as likely to fsck things up.
Damascus steel is forged by folding, as are the traditional oriental blades. I think that this is a case of parellel evolution, but I'm not completely certain.
The oriental blades have two parts - a core and an outer skin. Both are folded multiple times. The outer skin is high carbon, (to hold an edge) the core is milder steel (for flexibility). This doesn't matter much for knives, but is essential if you want a katana that you can shave with and that doesn't crack when hitting a bone.
In addition to the mutiple types of steel, traditional blades are differentially tempered. A clay shell is put on the blade, the clay is thinnest on the edge. The entire unit is heated past the curie point and quenched. The Edge has the least amount of clay, so the quenching cools it the fastest. This makes the edge hard (and sharp) without making the rest of the blade brittle.
Continuing this lecture, for anybody still with us, the edge and the remainder of the skin have two distinct tempers with two distinct crystal structures. The boundary between these two areas is a visible temper line. Cheap imitations will have etched onto them something vaguely similar to a temper line for the sake of authenticity. The temper line is intentially wavy to help keep cracks from spreading.
Build a distributed fileshare in which each node uses it's neighbors as caches/redistribution point. Initially worry about automatic mirroring, then add support for file locks and such.
Besides a better distributed filesystem, this could also be seen as a napster/gnutella next generation. Go heavy on the fault tolerance and decentralization.