Speed cameras are a joke. I drive past 5 of them on a daily basis along with 2 red light cameras. Speed cameras produce a safety bubble. People slow down way under the speed limit when they pass them and speed back up as soon as they are out of the line of sight. It is $75 if you get pinged going 12mph over.
My town had a big controversy over one camera where the road went from 40 to 25. It was making a lot of money on this major thru road from one county to the other. They moved it a block down so people could slow down, still gets a lot of people.
Best one was when they installed one right off I-95 and 90% of my co-workers got multiple tickets within the first week of it being active.
Mobile speed cameras are also fun. I got good at spotting the white SUVs randomly parked in the construction zones on the side of the road that could take a photo of any lane.
OH and my town also has FAKE speed cameras! Yes they randomly move a fake camera box around and place it in locations that real ones are not allowed to slow down traffic.
The side view cameras are on cars already. Half the comments here act like this is science fiction.
My 2014 Honda Odyssey has a camera on the passenger side mirror and also has the back up camera. When I turn on my right hand turn signal, my large display in my center console shows the video feed. I also can turn on the camera anytime with a click of the button. The video feed has "perceived" distance lines on it so you have some idea how far an object is away.
The downfall to cameras is mother nature. Sun glare, water and mud on the lens, and snow build up. I wish they had a wiper on the rear camera, it always has water on it. The side mirror just has issues when the sun angle is just right, seems like that has less problem with water because of the angle. The fear of ice build up or snow could be fixed by heating the camera like most side mirrors do these days
Nice thing about the cameras is lack of blind spots. I can see things with the back up camera that I can not see with a rear view mirror since it is low to the ground.
Yeah, adding stuff to the clipboard is nothing new. You could do it without a prompt in browsers in the past with a couple lines of JavaScript. TinyUrl does it with IE.
I was always worried about a script that could read what is on the clipboard and send it to some host server. Target your competitor and see if you can get sensitive data!
I thought it was common knowledge that the slowness is only to the ISP, guess I should have stated that.
The whole point is you need to realize that there is a difference between dialup, DSL, Cable, and localhost that a lot of developers tend to forget. I have seen people ask why it was so fast in development and sluggish in production. That is why I brought up the point.
Some people think that slapping an XHR on a page is going to be a beam of light from the skies to end all of their troubles. Ends up it can be even more trouble if they do not account for all of the minor issues.
There are a lot of good points posted in here. Caching on the client on the server are two big things for a good application that is using the XHR. A good database design is also key if you do not want to use "like" which slows down the search. In Ajax In Action as discussed on Slashdot here. In chapter 10, the project talks about how to limit post backs with an auto suggest by using the clientside efficiently. The basic idea examines the results returned. If it is under a certain number, it uses JavaScript regular expressions to trim down the dataset instead of hitting the server. Plus there is a limit on number of results returned so it speeds up response time.
One thing I can not get through people's minds enough when I do my talks is Ajax is not going to be a "client-based app" on the web. The main reason is going to be network traffic getting in the way of your request. Imagine a dial up user in India with your server sitting in the United States. The request is going to have to travel to the other side of the world and back with the slow speeds of dial-up. Testing on your localhost is going to look great until you get on an outdated shared server hosting multiple applications with a full network load. Yes we are talking small requests pinging the server, but 1000 users with a 10 letter word could mean death if you designed the system badly!
I love XHR, cough Ajax, but you need to look at what you are dealing with. The design of an XHR app can kill you if you do not think it out fully.
My 2 cents,
Eric Pascarello
Coauthor of: Ajax In Action
Ajax in Action will be available in ebook version shortly. If you buy it from Manning.com directly, you can get the MEAP subscription. The MEAP subscription allows you to get the chapters as we finish them.
Slashdot Mirror
Speed cameras are a joke. I drive past 5 of them on a daily basis along with 2 red light cameras. Speed cameras produce a safety bubble. People slow down way under the speed limit when they pass them and speed back up as soon as they are out of the line of sight. It is $75 if you get pinged going 12mph over.
My town had a big controversy over one camera where the road went from 40 to 25. It was making a lot of money on this major thru road from one county to the other. They moved it a block down so people could slow down, still gets a lot of people.
Best one was when they installed one right off I-95 and 90% of my co-workers got multiple tickets within the first week of it being active.
Mobile speed cameras are also fun. I got good at spotting the white SUVs randomly parked in the construction zones on the side of the road that could take a photo of any lane.
OH and my town also has FAKE speed cameras! Yes they randomly move a fake camera box around and place it in locations that real ones are not allowed to slow down traffic.
The side view cameras are on cars already. Half the comments here act like this is science fiction.
My 2014 Honda Odyssey has a camera on the passenger side mirror and also has the back up camera. When I turn on my right hand turn signal, my large display in my center console shows the video feed. I also can turn on the camera anytime with a click of the button. The video feed has "perceived" distance lines on it so you have some idea how far an object is away.
The downfall to cameras is mother nature. Sun glare, water and mud on the lens, and snow build up. I wish they had a wiper on the rear camera, it always has water on it. The side mirror just has issues when the sun angle is just right, seems like that has less problem with water because of the angle. The fear of ice build up or snow could be fixed by heating the camera like most side mirrors do these days
Nice thing about the cameras is lack of blind spots. I can see things with the back up camera that I can not see with a rear view mirror since it is low to the ground.
I can not wait to see that video. :)
Super Mario, Mario Kart, WolfenFlickr 3D, 3D Chess: http://www.nihilogic.dk/labs/javascript-games/
Spacius: http://scriptnode.com/lab/spacius/
Space Invaders: http://www.rebelideas.co.uk/games/invamars/
Yeah, adding stuff to the clipboard is nothing new. You could do it without a prompt in browsers in the past with a couple lines of JavaScript. TinyUrl does it with IE. I was always worried about a script that could read what is on the clipboard and send it to some host server. Target your competitor and see if you can get sensitive data!
If you want to see how they voted to remove the language from the bill, go here: http://www.mdchamber.com/blog/2007/11/how_they_voted_sales_tax_expan.php
I thought it was common knowledge that the slowness is only to the ISP, guess I should have stated that.
The whole point is you need to realize that there is a difference between dialup, DSL, Cable, and localhost that a lot of developers tend to forget. I have seen people ask why it was so fast in development and sluggish in production. That is why I brought up the point.
Some people think that slapping an XHR on a page is going to be a beam of light from the skies to end all of their troubles. Ends up it can be even more trouble if they do not account for all of the minor issues.
Eric Pascarello
There are a lot of good points posted in here. Caching on the client on the server are two big things for a good application that is using the XHR. A good database design is also key if you do not want to use "like" which slows down the search. In Ajax In Action as discussed on Slashdot here. In chapter 10, the project talks about how to limit post backs with an auto suggest by using the clientside efficiently. The basic idea examines the results returned. If it is under a certain number, it uses JavaScript regular expressions to trim down the dataset instead of hitting the server. Plus there is a limit on number of results returned so it speeds up response time.
One thing I can not get through people's minds enough when I do my talks is Ajax is not going to be a "client-based app" on the web. The main reason is going to be network traffic getting in the way of your request. Imagine a dial up user in India with your server sitting in the United States. The request is going to have to travel to the other side of the world and back with the slow speeds of dial-up. Testing on your localhost is going to look great until you get on an outdated shared server hosting multiple applications with a full network load. Yes we are talking small requests pinging the server, but 1000 users with a 10 letter word could mean death if you designed the system badly!
I love XHR, cough Ajax, but you need to look at what you are dealing with. The design of an XHR app can kill you if you do not think it out fully.
My 2 cents,
Eric Pascarello
Coauthor of: Ajax In Action
Ajax In Action Sample Chapter Released! http://www.theserverside.com/articles/article.tss? l=AjaxinAction_CH4_PT1
Ajax in Action will be available in ebook version shortly. If you buy it from Manning.com directly, you can get the MEAP subscription. The MEAP subscription allows you to get the chapters as we finish them.
Eric Pascarello
co-author of Ajax In Action