[deleted]
The Wonderful Awful Browser
11–17 of 17 posts
Re: The Wonderful Awful Browser
#12Earlier quoted context omitted.
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.
The actual reason I gave in the OP was easy distribution. This is huge.
I think also that my OP could have been stronger pointing out that the job is completely doable (in fact I've done it), with a sort of "here are the problems you will face" feel.
Re: The Wonderful Awful Browser
#13Earlier quoted context omitted.
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.
You can have your cake and eat it too, and you don't have to compromise. All you have to do is recognize where the browser's original intent may be different from your own (doc mgmnt versus transactional database mgmt). Making the browser do the job is very doable, but it is much easier if you recognize why it seems hard.
Re: The Wonderful Awful Browser
#14Earlier quoted context omitted.
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.
Agreed, but what he complains about is that web programmers are telling him that the way he makes it work is somehow objectionable. I think it's pragmatic.
Re: The Wonderful Awful Browser
#15Earlier quoted context omitted.
You can't have your cake and eat it too. Software development is all about compromise.
You can have your cake and eat it too, and you don't have to compromise. All you have to do is recognize where the browser's original intent may be different from your own (doc mgmnt versus transactional database mgmt). Making the browser do the job is very doable, but it is much easier if you recognize why it seems hard.
That's a very different view that what's being argued in this thread, and I agree with it.
Of course, as I already alluded to, I understood you post to push this point, but felt that you sometimes got a little too close to making the suggestion that there was something inherently wrong with the way the web is set up.
Thanks for clarifying.
Re: The Wonderful Awful Browser
#16This guy should look into XUL Runner:
Re: The Wonderful Awful Browser
#17This guy should look into XUL Runner: http://developer.mozilla.org/en/docs/The_Joy_of_XUL
Actually I have, it is extremely cool. For my own case I don't know where it will fit in yet, as I currently do fine without it, but its one of those things I follow.