As I read your reply. I ultimately hear you say; Keep It Simple Stupid (KISS).
Frankly, hard for anyone to resist. After all. Aren't we all inclined to the Least Line Of Resistance? Hell, some might even say "lazy". But seriously. I'm trying to balance the 2 areas I believe you refer to. 1) keeping it simple, and based on standards with a long history, and good "legacy" support. Will surely be considered a safe route to take. But OTOH, I'd like to think I could also add to my application(s) (FutureFul). I believe the direction I've chosen caters to both. HTTP hasn't changed [significantly] for some 20yrs. Perl? OK this one will likely receive contrasting opinions; but suffice to say, where P5 is concerned, it's LegacyProof. XML, has been around for quite some time now, and shows little sign of 1) going away, anytime soon. 2) will likely get additional features for the foreseeable future.
In the end I think the route I've chosen makes it relatively FutureProof. I think it is also simple enough to not become completely derailed, as standards, and technologies change.
I'm not suggesting you're attempting to argue against my chosen direction (altho perhaps that's true). I also get the impression that you may be suggesting that JS is a better approach. My personal observation is XML delivers nearly on-par w/JS. So unless I require Mosaic. I think I'm covered -- and XML is less fragile too. :)
Thanks again, Your Mother, for taking the time to reply!
--Chris
¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH
In reply to Re^6: Are there any issues with JSON
by taint
in thread Are there any issues with JSON
by taint
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |