Trust me, that's why it's called JavaScript object "notation" -- it's not actually a JavaScript object. You still have the extra step of converting it out of string form when you get it from the server.
I'm pretty sure that most browsers today (that I'm aware of) still have to convert the JSON objects back and forth into strings to communicate with the server.
Hey, that's a bit harsh, don't you think? I develop for the web. Just because I don't use every trick of the trade, you shouldn't try to call me names (lawyer).
Should I not call you a "car driver" because you can't do the Nurburgring in 8 minutes? No, because that would be silly.
(Or, like has been said elsewhere, just open a web app in a new window/tab. Problem solved.)
Hey, I'll agree it's a bit of semantic fun to make fun of IE, but it's up to us to try and influence users to start using decent web tools (no, IE is not decent). It's not like web application designers are advocating the use of something superfluous (like Gnome over KDE or something) -- IE is a very, very poorly made browser (though, it's getting better, slowly).
Anyway, if a webapp opens in a new window, will it ever have a history to go "back" to? Will the back-button even be enabled in that case?
You make a good point (using a new window is how I do things). I guess I was just playing Devil's Advocate -- to be honest, I wouldn't even need this feature.:P
Unfortunately, there's very little you can do in the situation about an application's intelligence -- the web browser is basically your development environment for web apps (and one that wasn't originally intended to be such), and things like the back button are (almost) unavoidable frustrations.
And do you honestly think I'm choosing the web as a platform? It's what I'm told to do, so I do it.:P
There kinda is -- you hook into the "onunload" event on a web page, prompting the user with a dialog. It's how web apps like Meebo.com handle this problem.
You mistake IE for a modern browser. Be mindful of the fact that the only reason why you're still not using a seven year old release of IE6 is because Firefox lit a fire under their ass.
Do a lot of web development? This is one feature I would love -- users can completely destroy how a web app works just by clicking on the back button and asking "where'd all my data go?"
And nothing "traps" you in a page; just close the tab.
...who doesn't want cross-domain access? I'm perfectly fine with making server side code to parse whatever I need and then feed it to the browser via the local domain.
Am I missing something? Something about making a browser more independent of the server or something?
I'm also trying to figure out what the "particularly Internet Explorer" comment meant. Not that I read the article..
I'd assume it's a stab at IE's very poor Canvas graphics support (something I've heard about). I don't work with graphics so I wouldn't know for sure, however.
Cordwainer Smith often wrote about a world in which death had been eliminated, through a mixture of mechanical and biological means. If I remember correctly, however, the society that had achieved this eventually went back to having death, since existence without death eventually made humanity so mundane that everyone nearly lost their minds.
Problem is -- the users in question never "installed" those programs -- they just went to a web page and clicked an annoying message box to get it off their screen. We can thank Internet Explorer for that.
Slashdot Mirror
Dear god no. That was the _most_ basic example I was giving.
Uh... thanks?
Trust me, that's why it's called JavaScript object "notation" -- it's not actually a JavaScript object. You still have the extra step of converting it out of string form when you get it from the server.
I'm pretty sure that most browsers today (that I'm aware of) still have to convert the JSON objects back and forth into strings to communicate with the server.
It hasn't been adopted officially, hence the use of "eval()" to turn it into a JSON object. Otherwise, it's still just a string. :(
I'm gussing "Native JSON" would be able to accept a string from the server, automatically turning it into a JS object.
Aye, but isn't there the possibility of data loss if you go back in the history?
There's actually a feature in the TabMixPlus extension for Firefox that allows you to force this behavior. Try it out!
Never said you were. ;)
And yes, you can open an app in a new window. No history problems.
Hey, that's a bit harsh, don't you think? I develop for the web. Just because I don't use every trick of the trade, you shouldn't try to call me names (lawyer).
Should I not call you a "car driver" because you can't do the Nurburgring in 8 minutes? No, because that would be silly.
(Or, like has been said elsewhere, just open a web app in a new window/tab. Problem solved.)
Do you like all system applications to open in the same window, too?
What if you need to get information from another web page to use in the application page?
Hey, I'll agree it's a bit of semantic fun to make fun of IE, but it's up to us to try and influence users to start using decent web tools (no, IE is not decent). It's not like web application designers are advocating the use of something superfluous (like Gnome over KDE or something) -- IE is a very, very poorly made browser (though, it's getting better, slowly).
Anyway, if a webapp opens in a new window, will it ever have a history to go "back" to? Will the back-button even be enabled in that case?
You make a good point (using a new window is how I do things). I guess I was just playing Devil's Advocate -- to be honest, I wouldn't even need this feature. :P
Unfortunately, there's very little you can do in the situation about an application's intelligence -- the web browser is basically your development environment for web apps (and one that wasn't originally intended to be such), and things like the back button are (almost) unavoidable frustrations.
And do you honestly think I'm choosing the web as a platform? It's what I'm told to do, so I do it. :P
There kinda is -- you hook into the "onunload" event on a web page, prompting the user with a dialog. It's how web apps like Meebo.com handle this problem.
Well, if you're using a decently made web app it's going to have opened in its own personal tab/window anyway. No history concerns that way.
You mistake IE for a modern browser. Be mindful of the fact that the only reason why you're still not using a seven year old release of IE6 is because Firefox lit a fire under their ass.
Do a lot of web development? This is one feature I would love -- users can completely destroy how a web app works just by clicking on the back button and asking "where'd all my data go?"
And nothing "traps" you in a page; just close the tab.
...who doesn't want cross-domain access? I'm perfectly fine with making server side code to parse whatever I need and then feed it to the browser via the local domain.
Am I missing something? Something about making a browser more independent of the server or something?
I'm also trying to figure out what the "particularly Internet Explorer" comment meant. Not that I read the article..
I'd assume it's a stab at IE's very poor Canvas graphics support (something I've heard about). I don't work with graphics so I wouldn't know for sure, however.
...keep your art out of my code (and off my lawn)!
Native JSON should clearly be at the top of this list. I call shenanigans.
Cordwainer Smith often wrote about a world in which death had been eliminated, through a mixture of mechanical and biological means. If I remember correctly, however, the society that had achieved this eventually went back to having death, since existence without death eventually made humanity so mundane that everyone nearly lost their minds.
So I have "issues" if I admire Nelson Mandela?
Well, he was once the leader of Umkhonto_we_Sizwe. It's up to you to decide if that means anything, though.
Aye, but were they really intentional...?
Or, like an unexpected pregnancy, did they just come to love and cherish them after they were installed in their systems?
Oh, come on, anonymous Google employees -- is it really that bad...?
Problem is -- the users in question never "installed" those programs -- they just went to a web page and clicked an annoying message box to get it off their screen. We can thank Internet Explorer for that.