Over the last day or so, I have spent a great deal of time re-investigating updating the QuickMaps interface on the WiredPages Dining & Travel page.

I have researched this over and over, since Google introduced their dynamic mapping tools-- and I keep coming up with the same issue-- not backward compatible with browsers running on several of my older systems.

My interface currently uses Google static maps. Updating to use dynamic maps would not be difficult-- simply not sure if I want to code around browsers and operating systems-- to insure I handle old and ajax capable browsers.

I often get errors when surfing the net. Browser outdated-- "upgrade your browser". Last spring I updated Firefox on my Macbook which I believe caused hardware issues in the fall. Even before that I was reluctant to update software on that platform.

Flash another tool that outdates quickly.

This is why I like Java and non-Jquery/Ajax sites. You will find that for the most part-- tools on my sites work with most old browsers. The new YouTube Music Search tool [installed on the Arts & Entertainment page] works on all of my old systems-- however YouTube is a little persnickety with the old Safari browser.

I could do a lot with JQuery and AJax. I can do a lot with what I am using now. What I cannot do-- is create the interactivity of Google Maps without Ajax and JQuery-- neither of which work with all of my old browsers. Normally I am really good-- about putting in a work around for old browsers. I have not been so forthcoming in this regard where JQuery and AJax are concerned. Think the problem is-- I also act as my own lawyer and I do not want to have to explain to a client the technical issues for why it did not work on x, y or z. And believe me.. a lot of sites do not work on my systems and it is not because of my connection. I have Verizon FiOS.

I will probably update the QuickMaps interface and develop a work around for old browsers wherein I use the static maps I am currently using.

That said, I am [QiSoftware is] not going after business that requires Jquery or Ajax support. It doesn't always work. In addition, the only guarantee I have found that something using JQuery or Ajax will work for a given period of time-- is 3 years.

Backward compatible used to be important to programmers or those who purchased software. I cannot guarantee backward compatibility with JQuery, Flash nor Ajax. Have you noticed this too?

I think programmers should again be more concerned with backward compatibility issues. No I am not paranoid a client wants to sue me for defective work based on the fact it did not work with this browser or that browser- I simply do not like leaving a door like this open. It is too easy for others to pretend ignorance on this issue -- and I often pay for the ignorance of others. By the way I have no clients. If you feel I [QiSoftware does] do--contact the FBI. I am simply explaining why I do not take this type of development work.