Right. It's a "push", "pull" (transport) layer. That will provide me the same "dynamic feel" that JavaScript does. I can provide a more responsive interaction with the client, and I can create an editor, for the Forum, and News/Blog.

At least that's been my understanding, while researching it.

--Chris

"Right. It's a "push", "pull" (transport) layer. That will provide me the same "dynamic feel" that JavaScript does."

No, that's not what JSON is at all.

JSON is a data format. That's it. Saying that JSON will provide you with a "dynamic feel" is like saying that Perl hash variables will provide you with a "dynamic feel".

Hashes are just a place to put data. If you want to do something interesting with that data (like provide a "dynamic feel"), then you need to write code to manipulate the data in the hash in some way.

Similarly JSON is just a data format. If you want to do something interesting with that data (like provide a "dynamic feel"), then you need to write code to manipulate the data in the JSON in some way. If you want that to happen in a browser, then that code probably wants to be Javascript.

use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name

Hello, tobyink, and thanks for the reply (clarification).

Boy! Did I get the wrong impression. When I went to the CPAN to examine JSON. That page led me to additional JSON resources: http://www.json.org/. Which had many additional JSON related links. One of which was JSON Editor Online. This was a few days ago, and the last association I had in my mind, where JSON was concerned. Unfortunately, the wrong association/impression.

Sorry for all the noise, and thank you very much for taking the time to respond.

--Chris

¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH

Maybe my reading comprehension skills are low but it sound like you have some serious misconceptions about what JSON actually is -- it's just string data -- a way of representing data -- similar to serialized Data::Dumper output. You still need Javascript to get the data to/from the browser/server (at least if you want it to happen asynchronously) and you still need Javascript to add client-side behaviour to the data. I wouldn't be so quick to dismiss the web2 frameworks. JQuery has pretty much won that battle and Bootstrap is a nice layer on top of it. Other battles are looming but I'll let some blood spill before choosing sides. There is nothing inherently wrong with writing all your JS from scratch but that's a lot of wheel to re-invent and I'd rather spend my time elsewhere.

-derby

I think you either don't understand what JSON is, or aren't explaining your intentions in a way that anyone seems to understand. If the former please read the wiki entry I link to again.

Update: Are you suggesting that your backend app (in perl?) will talk to your front end app (written in what?) using JSON?

From Re^2: Are there any issues with JSON: "Also, I'll be building a custom editor with it (JSON)."

Again, it's just a data format.

Right. While I'll address all the thoughtful replies.

I'll start here, by attempting to defend my horrible misunderstanding by pointing out the following link: JSON Editor Online. This was my last place of reference. From a couple of days ago. Which left me with the impression that I'd have the abilities mentioned above. But as anyone will note, by examining it closer (as I just did). They are using JavaScript libraries to create the editor.

Regrettably; my memory ain't what I wished it had been, regarding this. Ugh.

Thanks for taking the time to respond.
Sorry for the noise.

--Chris

¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH