If you have ever been to Manhattan, then you would know that there are large areas of it where cars and trucks just do not belong. Parts of it -should- be blocked off to general traffic, and only allow those vehicles which directly support the community. When parking your car costs much more than a night's hotel bill, you know that cars are simply out of place there. Treat the place more like a park, less like a parking lot.
I guess that the author never actually used any of these things, as some of the fact or impressions are a bit off.
First of all, the 8-track was a -terrible- design. Having the 4 channels run physically parallel on the tape led to awful tracking and crosstalk problems. Also, the way that the tape feed operated was awful. As the tape played, it would be peeled out from the center of the tape spindle, run over the head, and then reeled back onto the spindle. This horrible way of feeding the tabe resulted in tangling, unravelling, and twisting. It also contributed to wear and tear on the tape and shortened the cartridge's life.
I didn't see any place where they compared the Atari ST to the Amiga. I only saw the passing reference to Amiga as an "also ran." Although both of these machines had their RAM configured as 8-bit or 16-bit, both operated on a 32-bit model. It didn't matter, since the MC68000 had a linear memory model. Either one was a joy to use. I learned MC68000 Assembly on the Amiga. IMHO, the Amiga was more advanced, though the Atari was faster. And in spite of their brand differences, a lot of the same people designed the multimedia capabilities of both. In speed and capability, these boxes were remarkably similar.
By the way, TOS was, maybe unofficially, the "Tramiel Operating System." AmigaDOS was fun, somewhere between DOS and Unix. Maybe more like MP/M.
The pink noise from your FM receiver's discriminator or PLL when not tuned to a station is a great generator of medium-quality random numbers. In fact, a lot of military radios use this as a source of temporary keys. A reverse-biased zener diode is a great generator of white noise, too. And there is also the tunnel diode, the poor man's source of quantum effects.
Although being remote controlled makes them strictly not robots, I tend to agree. The latency would demand some scheduling and prediction to avoid the latency loop. Something would be needed to battle overcompensation (porpoising).
If you want to see a short clip (in color) of one of those devices in action, watch the George Pal version of "When Worlds Collide." (1951) In the script, one is used to verify the trajectory of the approaching planet.
But the LGPL must be enforced, else there is no reason for potential contributors to trust it.
Some people are not looking at this correctly. Individual authors, not some "WINE" corporation, have altruistically given their time and effort to Open Source software. Then they put the LGPL header on their source files. Remember, this is NOT public domain code. It is still theirs. The LGPL takes non-public code and confers very generous freedoms to downstream users of the code. Basically all they want is for those users to be equally generous to others. It should not be too burdensome for people to be honest and respect the terms of such a well-intentioned gift.
I trust that this will all pass, and it will end up with all parties happy.
Keep all of your decision-making on the server where it belongs. Let the client be a view to the server, and validate input. But don't trust the client with any control of the process. It only results in problems like this.
The first thought I had when they mentioned biodiesel, is that it is very dirty. One of the benefits of a piston engine is that it is constantly scrubbing itself clean of all the residue of the combustion. Won't the fuel cell elements get coated with a layer of gunk in only a few hours without some process (mechanical?) that periodically cleans them?
Along the same lines as not having the Cylons in disco-chrome shells, it is far cheaper to buy some props at Toys R Us than to hire someone to do CG special effects.
Whenever you bow to hysteria, fear, and hype like this, innocent people can and will get hurt. Any shrill screamer who uses the tired old phrase, "Isn't anyone thinking of the children?" should be sent to a camp somewhere for the safety of everyone else.
Well, with microwave ovens, it's the other way around. 2.4ghz is one of the major resonant frequencies of a water molecule, thus water absorbs waves of that frequency wonderfully. And since water absorption through air is so high, terrestrial long-distance communications on this frequency are not very efficient. Thus the frequency is left open as a "wasteland" that nobody wants. In the U.S., at least, the government like to use distance-limited communications for civilian "type acceptance," where devices do not need to be licensed individually, but their entire class is approved for unlicensed use.
Making the Cylons "look like real people" instead of shiny chrome disco bots was supposed to save them a bundle of money, while only discarding the most interesting part of the story. Wasn't that enough? Not to mention the money they saved by not buying Steadycams.
Our company finally got a new medium-size UPS, large enough to power two racks of servers and a router rack. It was placed on the floor in the midst of them, giving us a sublime sense of security and well-being. Trouble was, the manufacturer put the UPS's reset switch in the front, exactly at knee level. We had several instances of all of the servers rebooting in the evenings after everyone had gone home. Turns out that the cleaning crew was bumping into that switch while making their rounds. Took us a while to debug that problem. The fix: open up the UPS box and snip the reset switch wire.
The more you know about the context, and the more you know about the result to a given action, the less information you need from the environment (or from the other side of a communication channel). This is the Holy Grail of information theory and data compression, and it seems as if they are applying its principles here. Higher CPU and better expert programming will likely produce some nice results in the near future.
If China did any slamming, I bet it was the most polite ever done, with many a "please" and "thank you", and lots of curtsying. Is this title maybe a reflection of the author's own people skills? ^^
I have been a Java programmer ever since it existed, but have only delved into the EJB side of things recently. I started using JPA a few months ago, and have tried Hibernate and TopLink Essentials (the default engine in J5EE). Hibernate is large and all-powerful, but for my needs, I have found TopLink to be a light, fast, and very clean design. The Glassfish developers have refactored and cleaned up a lot of the legacy code, and have cherry-picked a lot of the best design features from the other implementations. I imagine that this new code contribution will be able to provide a lot of the add-on tools that the average guy needs.
At first I didn't know what Persistence could add to my app. But I have been very impressed by the speed increase that caching the business object tree on the server side provides over low-level SQL manipulation.
Slashdot Mirror
If you have ever been to Manhattan, then you would know that there are large areas of it where cars and trucks just do not belong. Parts of it -should- be blocked off to general traffic, and only allow those vehicles which directly support the community. When parking your car costs much more than a night's hotel bill, you know that cars are simply out of place there. Treat the place more like a park, less like a parking lot.
This lovely format had such a bright future, until the recording companies killed it.
I guess that the author never actually used any of these things, as some of the fact or impressions are a bit off.
First of all, the 8-track was a -terrible- design. Having the 4 channels run physically parallel on the tape led to awful tracking and crosstalk problems. Also, the way that the tape feed operated was awful. As the tape played, it would be peeled out from the center of the tape spindle, run over the head, and then reeled back onto the spindle. This horrible way of feeding the tabe resulted in tangling, unravelling, and twisting. It also contributed to wear and tear on the tape and shortened the cartridge's life.
I didn't see any place where they compared the Atari ST to the Amiga. I only saw the passing reference to Amiga as an "also ran." Although both of these machines had their RAM configured as 8-bit or 16-bit, both operated on a 32-bit model. It didn't matter, since the MC68000 had a linear memory model. Either one was a joy to use. I learned MC68000 Assembly on the Amiga. IMHO, the Amiga was more advanced, though the Atari was faster. And in spite of their brand differences, a lot of the same people designed the multimedia capabilities of both. In speed and capability, these boxes were remarkably similar.
By the way, TOS was, maybe unofficially, the "Tramiel Operating System." AmigaDOS was fun, somewhere between DOS and Unix. Maybe more like MP/M.
The pink noise from your FM receiver's discriminator or PLL when not tuned to a station is a great generator of medium-quality random numbers. In fact, a lot of military radios use this as a source of temporary keys. A reverse-biased zener diode is a great generator of white noise, too. And there is also the tunnel diode, the poor man's source of quantum effects.
Although being remote controlled makes them strictly not robots, I tend to agree. The latency would demand some scheduling and prediction to avoid the latency loop. Something would be needed to battle overcompensation (porpoising).
They say themselves in the article that it is not a space suit, but a pressure suit. There are other considerations, like Alpha radiation or esp Beta.
Actually, I think the equivalent would be to evaluate a given problem via a system of polynomial series, rather than a discrete computer model.
If you want to see a short clip (in color) of one of those devices in action, watch the George Pal version of "When Worlds Collide." (1951) In the script, one is used to verify the trajectory of the approaching planet.
I have always considered POVRay code to be very clean and elegant. One of the better examples on the Net.
With modern (hyper)sensitivities, ecologists will likely decry the damage to the lunar landscape.
But the LGPL must be enforced, else there is no reason for potential contributors to trust it.
Some people are not looking at this correctly. Individual authors, not some "WINE" corporation, have altruistically given their time and effort to Open Source software. Then they put the LGPL header on their source files. Remember, this is NOT public domain code. It is still theirs. The LGPL takes non-public code and confers very generous freedoms to downstream users of the code. Basically all they want is for those users to be equally generous to others. It should not be too burdensome for people to be honest and respect the terms of such a well-intentioned gift.
I trust that this will all pass, and it will end up with all parties happy.
So, when is this going to be on "How It's Made," one of my favorite TV shows?
Keep all of your decision-making on the server where it belongs. Let the client be a view to the server, and validate input. But don't trust the client with any control of the process. It only results in problems like this.
The first thought I had when they mentioned biodiesel, is that it is very dirty. One of the benefits of a piston engine is that it is constantly scrubbing itself clean of all the residue of the combustion. Won't the fuel cell elements get coated with a layer of gunk in only a few hours without some process (mechanical?) that periodically cleans them?
Along the same lines as not having the Cylons in disco-chrome shells, it is far cheaper to buy some props at Toys R Us than to hire someone to do CG special effects.
Whenever you bow to hysteria, fear, and hype like this, innocent people can and will get hurt. Any shrill screamer who uses the tired old phrase, "Isn't anyone thinking of the children?" should be sent to a camp somewhere for the safety of everyone else.
I was under the impression that all BBC employees were Oxford profs, who compose poetry during tea, and stand atop mountains to sing opera.
I stand corrected. I found out that my knowledge of the topic was totally wrong:
http://en.wikipedia.org/wiki/Microwave_oven
Well, with microwave ovens, it's the other way around. 2.4ghz is one of the major resonant frequencies of a water molecule, thus water absorbs waves of that frequency wonderfully. And since water absorption through air is so high, terrestrial long-distance communications on this frequency are not very efficient. Thus the frequency is left open as a "wasteland" that nobody wants. In the U.S., at least, the government like to use distance-limited communications for civilian "type acceptance," where devices do not need to be licensed individually, but their entire class is approved for unlicensed use.
Making the Cylons "look like real people" instead of shiny chrome disco bots was supposed to save them a bundle of money, while only discarding the most interesting part of the story. Wasn't that enough? Not to mention the money they saved by not buying Steadycams.
Our company finally got a new medium-size UPS, large enough to power two racks of servers and a router rack. It was placed on the floor in the midst of them, giving us a sublime sense of security and well-being. Trouble was, the manufacturer put the UPS's reset switch in the front, exactly at knee level. We had several instances of all of the servers rebooting in the evenings after everyone had gone home. Turns out that the cleaning crew was bumping into that switch while making their rounds. Took us a while to debug that problem. The fix: open up the UPS box and snip the reset switch wire.
The more you know about the context, and the more you know about the result to a given action, the less information you need from the environment (or from the other side of a communication channel). This is the Holy Grail of information theory and data compression, and it seems as if they are applying its principles here. Higher CPU and better expert programming will likely produce some nice results in the near future.
No.
(well, I can't think of a better response to such a silly question)
If China did any slamming, I bet it was the most polite ever done, with many a "please" and "thank you", and lots of curtsying. Is this title maybe a reflection of the author's own people skills? ^^
I have been a Java programmer ever since it existed, but have only delved into the EJB side of things recently. I started using JPA a few months ago, and have tried Hibernate and TopLink Essentials (the default engine in J5EE). Hibernate is large and all-powerful, but for my needs, I have found TopLink to be a light, fast, and very clean design. The Glassfish developers have refactored and cleaned up a lot of the legacy code, and have cherry-picked a lot of the best design features from the other implementations. I imagine that this new code contribution will be able to provide a lot of the add-on tools that the average guy needs.
At first I didn't know what Persistence could add to my app. But I have been very impressed by the speed increase that caching the business object tree on the server side provides over low-level SQL manipulation.