Hacker News Reader

Comment by run4yourlives | Hacker News Reader

This 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.

View on HN

"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.

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.

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.

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.

Reply on news.ycombinator.com