Assuming they use timed response averages to triangulate the devices position, it should be a simple matter to programatically fluctuate response times. This would at least make automatic proximity exclusion un-reliable (we don't want to drop the guys in white hats and we can't tell if this guy is wearing a white hat so we'd better not kill this connection). And as usual at this point i am rambling on.
I agree strongly with the majority of responses so far. Akira is fine the way it is. But, Narrington will make money on this flick. It is inevitatble, the Hollywood machine will continue to roll. Marketers will be there to hype the movie. Special effects artists will be there to "improve" the visual aspect of the movie. Etc. etc.. I for one will not watch this movie. But I strongly suspect that I will be able to read a review, here on/..
"...and writing thorough documentation for your programs is not nearly as satisfying or financially rewarding as designing and writing the code itself."
"According to one Microsoft insider, this has been the pattern at the company: "and let's
face facts. innovation has never been microsoft's strong suite. we're much better at
ripping off our competitors. For example, we did not invent either ASP [active server
pages] or IE, we bought them!" RX8" -- Civil Action No. 98-1232 (TPJ)
It seems I read somewhere that the big companies are planning on using voice over data more and more. Once this is mainstream it should allow for buffering of some sort that will reduce the effect these blind spots have.
"However, I somewhat got the feeling from the new version that QSSL is moving even more far away from a "desktop QNX." "
QNX as a company has no interest in the desktop market and all that it entails. (eg. tech. support, updates, etc.) It is mainly concerned with providing a realtime system for industry as well as providing a decent developement environment for the software that will go into those systems.
I found this tiny HTTP 1.0 complian web server while researching a project. Very interesting.
"It is based on the world's smallest implementation of a TCP/IP stack -- which is implmented on a small 8-pin low-power microcontroller.. using a mere 512 words of program ROM." There are many such resources out there (both software and hardware). And during my research I had the most luck when I included "embeded" in the search.
In my experience there is a simple scheme that allows everyone input as to the direction and layout of a project while keeping the project on the timeline. This scheme requires that the core developement/design (design/developement:)?) team agree on a majority rules veto system. This system is, stated simply: If a problem arises that extended discussion may hinder advancement of the project - If time permits continue discussion. - Otherwise take a vote on the issue, majority rules.
It seems to work for me. There have been some hurt feelings but in the long run the entire group has been more productive and Happy!
Slashdot Mirror
Assuming they use timed response averages to triangulate the devices position, it should be a simple matter to programatically fluctuate response times. This would at least make automatic proximity exclusion un-reliable (we don't want to drop the guys in white hats and we can't tell if this guy is wearing a white hat so we'd better not kill this connection). And as usual at this point i am rambling on.
Go ahead. Mod me down.
I agree strongly with the majority of responses so far. Akira is fine the way it is. But, Narrington will make money on this flick. It is inevitatble, the Hollywood machine will continue to roll. Marketers will be there to hype the movie. Special effects artists will be there to "improve" the visual aspect of the movie. Etc. etc.. I for one will not watch this movie. But I strongly suspect that I will be able to read a review, here on /..
I beleive I can fly!
"...and writing thorough documentation for your programs is not nearly as satisfying or financially rewarding as designing and writing the code itself."
"According to one Microsoft insider, this has been the pattern at the company: "and let's face facts. innovation has never been microsoft's strong suite. we're much better at ripping off our competitors. For example, we did not invent either ASP [active server pages] or IE, we bought them!" RX8" -- Civil Action No. 98-1232 (TPJ)
I put the 't' in load!
They must have just modified the headers acause it loatds too quick.
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
--Peter J. Schoenster
It seems I read somewhere that the big companies are planning on using voice over data more and more. Once this is mainstream it should allow for buffering of some sort that will reduce the effect these blind spots have.
How many clicks can a coder click if a coder could surf (cough cough). Um anyways... I wonder what the ratio between keystrokes to clicks is.
"However, I somewhat got the feeling from the new version that QSSL is moving even more far away from a "desktop QNX." " QNX as a company has no interest in the desktop market and all that it entails. (eg. tech. support, updates, etc.) It is mainly concerned with providing a realtime system for industry as well as providing a decent developement environment for the software that will go into those systems.
Where did all the good /. threads go?
Read this (http://dailynews.yahoo.com/h/nm/20011123/tc/bizcl oning_dc_1.html) story [yahoo.com].
I found this tiny HTTP 1.0 complian web server while researching a project. Very interesting. .. using a mere 512 words of program ROM."
"It is based on the world's smallest implementation of a TCP/IP stack -- which is implmented on a small 8-pin low-power microcontroller
There are many such resources out there (both software and hardware). And during my research I had the most luck when I included "embeded" in the search.
In my experience there is a simple scheme that allows everyone input as to the direction and layout of a project while keeping the project on the timeline.
This scheme requires that the core developement/design (design/developement:)?) team agree on a majority rules veto system. This system is, stated simply:
If a problem arises that extended discussion may hinder advancement of the project
- If time permits continue discussion.
- Otherwise take a vote on the issue, majority rules.
It seems to work for me. There have been some hurt feelings but in the long run the entire group has been more productive and Happy!
Just did a search on e-bay and found lots for around (US)$15. This was the machine I started hacking on.