Live data from Hacker News

The Future of Web Apps - Single Page Applications

happyworm.com

61–65 of 65 posts

Re: The Future of Web Apps - Single Page Applications

#61
post #50

Earlier quoted context omitted.

Firefox 3.6.8 on Vista Home Premium x64 without js on. That's all. If I were in the market for a web framework, I would not take it on faith that I could rely upon interoperability features the site claims but does not demonstrate. And I wouldn't write the demo myself unless I had already ruled out your competitors. If you decide to drop it, I have no doubt you can still find a large potential market of developers ei…

There we go, without js, which you didn't identify at first. Rather, you just started to list things that seems like they weren't working. The best way to determine if something lives up to its claims is to try it. You can't look at sites done in NOLOH and then expect them to have implemented or turned on every feature. Furthermore, it's amazing that when our competitors 280north, or Sproutcore, or whatever else is "…

> There we go, without js, which you didn't identify at first.

I thought it was fairly obvious that someone on a technical forum complaining about anchors not leading anywhere and hidden divs appearing on the page is using NoScript, or otherwise has javascript disabled.

>Rather, you just started to list things that seems like they weren't working.

Well, they weren't, were they?

> As soon as we post something there's usually somebody that steers the conversation to a different topic and then criticizes us for one reason or another.

Mm, kinda like how you complain about your competitors instead of addressing issues about your javascript degredation?

If you bring up your product as a solution, it seems reasonable to expect us to describe why it isn't.

Re: The Future of Web Apps - Single Page Applications

#62
post #50

Earlier quoted context omitted.

There we go, without js, which you didn't identify at first. Rather, you just started to list things that seems like they weren't working. The best way to determine if something lives up to its claims is to try it. You can't look at sites done in NOLOH and then expect them to have implemented or turned on every feature. Furthermore, it's amazing that when our competitors 280north, or Sproutcore, or whatever else is "…

> There we go, without js, which you didn't identify at first. I thought it was fairly obvious that someone on a technical forum complaining about anchors not leading anywhere and hidden divs appearing on the page is using NoScript, or otherwise has javascript disabled. >Rather, you just started to list things that seems like they weren't working. Well, they weren't, were they? > As soon as we post something there's…

You clearly decided to pick and choose what you want to respond to. That's no way to have an adult discussion, as such I won't reply to you further, otherwise you can easily advance any conversation into any direction you like.

Re: The Future of Web Apps - Single Page Applications

#63
post #62

Earlier quoted context omitted.

> There we go, without js, which you didn't identify at first. I thought it was fairly obvious that someone on a technical forum complaining about anchors not leading anywhere and hidden divs appearing on the page is using NoScript, or otherwise has javascript disabled. >Rather, you just started to list things that seems like they weren't working. Well, they weren't, were they? > As soon as we post something there's…

You clearly decided to pick and choose what you want to respond to. That's no way to have an adult discussion, as such I won't reply to you further, otherwise you can easily advance any conversation into any direction you like.

Is it not normal to respond to only parts of a comment? That's why we developed quoting methods, right? Because, y'know, we may not have something to say about everything?

We have this fantastic thing called threaded discussion. There is not a direction for a conversation, but many, as is evidenced by the deeply-threaded messages on most technical boards (think Slashdot, not Digg).

Re: The Future of Web Apps - Single Page Applications

#64
post #57
post #46

Earlier quoted context omitted.

Server side session is a outcrop of the idea that the client is dumb philosophy, as such, the server has to "approximate" the client, this leads to many counter intuitive patterns like session. By far the worst evil is the fact that you have no guaranteed destructor because you have an approximation. So if the client wanders off, you have no way to clean up based on that event other than a brute force timeout. Furthe…

Sorry for replying to my own post but I did want to touch a little further on this subject. above I stated: So if the client wanders off, you have no way to clean up based on that event other than a brute force timeout. A common rebuttal to this is well just sprinkle in an AJAX call. Which in my opinion is the worst decision one can make. Now not only are you supporting a server model but you also have client mode sp…

By 'an AJAX call', do you mean having the client periodically ping the server, and then cleaning up the session if the ping times out?

Re: The Future of Web Apps - Single Page Applications

#65
post #64
post #57

Earlier quoted context omitted.

Sorry for replying to my own post but I did want to touch a little further on this subject. above I stated: So if the client wanders off, you have no way to clean up based on that event other than a brute force timeout. A common rebuttal to this is well just sprinkle in an AJAX call. Which in my opinion is the worst decision one can make. Now not only are you supporting a server model but you also have client mode sp…

By 'an AJAX call', do you mean having the client periodically ping the server, and then cleaning up the session if the ping times out?

No I mean wire an event to the unload of the page, that notifies the server that the client has abandoned the app.
Post reply on HN