The Wonderful Awful Browser
database-programmer.blogspot.com
The Wonderful Awful Browser
1–10 of 17 posts
Re: The Wonderful Awful Browser
#2This isn't a bad article, even if it is rather obvious. One thing I would like to see though is an understanding that the application programmer understands that he is in a different environment, and therefore is the one that needs to adapt.
In many parts I got the feeling that the thesis was: It was like this on the desktop, so the web should change to be more like the desktop because that way I don't have to change.
That's the kind of thinking that gives us craptastic IE only business apps, and has actually stalled IE improvements over the last couple of years.
Re: The Wonderful Awful Browser
#3This isn't a bad article, even if it is rather obvious. One thing I would like to see though is an understanding that the application programmer understands that he is in a different environment, and therefore is the one that needs to adapt. In many parts I got the feeling that the thesis was: It was like this on the desktop, so the web should change to be more like the desktop because that way I don't have to change…
"It was like this on the desktop, so the web should change to be more like the desktop because that way I don't have to change."
Or "It was like this on the desktop, so my users demand that it be just that way on the web version, too, so they don't have to change."
Re: The Wonderful Awful Browser
#4This isn't a bad article, even if it is rather obvious. One thing I would like to see though is an understanding that the application programmer understands that he is in a different environment, and therefore is the one that needs to adapt. In many parts I got the feeling that the thesis was: It was like this on the desktop, so the web should change to be more like the desktop because that way I don't have to change…
"It was like this on the desktop, so the web should change to be more like the desktop because that way I don't have to change." Or "It was like this on the desktop, so my users demand that it be just that way on the web version, too, so they don't have to change."
That's a valid point. But it begs the question: Why are you not writing a desktop app then?
Re: The Wonderful Awful Browser
#5Ironic that the very attributes that allowed the web to be popular (HTML, easy navigation) have turned it into a nightmare for developing actual applications.
Re: The Wonderful Awful Browser
#6Ironic that the very attributes that allowed the web to be popular (HTML, easy navigation) have turned it into a nightmare for developing actual applications.
Well, the web was originally designed for documents, not applications. So I'm not sure where the irony lies.
Re: The Wonderful Awful Browser
#7Earlier quoted context omitted.
"It was like this on the desktop, so the web should change to be more like the desktop because that way I don't have to change." Or "It was like this on the desktop, so my users demand that it be just that way on the web version, too, so they don't have to change."
That's a valid point. But it begs the question: Why are you not writing a desktop app then?
because managing a stateful client is nasty and costly if users cannot or are not allowed to do it themselves.
Re: The Wonderful Awful Browser
#8This isn't a bad article, even if it is rather obvious. One thing I would like to see though is an understanding that the application programmer understands that he is in a different environment, and therefore is the one that needs to adapt. In many parts I got the feeling that the thesis was: It was like this on the desktop, so the web should change to be more like the desktop because that way I don't have to change…
I think he makes the point pretty clearly that heads down data entry simply comes with different requirements than web surfing. Try to order not one but 200 books a day from amazon and then let's talk UIs afterwards ;-)
Re: The Wonderful Awful Browser
#9This isn't a bad article, even if it is rather obvious. One thing I would like to see though is an understanding that the application programmer understands that he is in a different environment, and therefore is the one that needs to adapt. In many parts I got the feeling that the thesis was: It was like this on the desktop, so the web should change to be more like the desktop because that way I don't have to change…
I think he makes the point pretty clearly that heads down data entry simply comes with different requirements than web surfing. Try to order not one but 200 books a day from amazon and then let's talk UIs afterwards ;-)
I didn't take him to task for that. In fact I would agree. Point being, if that is such a requirement, and the web is so bad at it, why the heck are you trying to build a web app in the first place?
Either you learn how to make it work in the environment, or you change the environment.
Re: The Wonderful Awful Browser
#10Earlier quoted context omitted.
That's a valid point. But it begs the question: Why are you not writing a desktop app then?
because managing a stateful client is nasty and costly if users cannot or are not allowed to do it themselves.
You can't have your cake and eat it too. Software development is all about compromise.