4 ms·

> basic, essential function Simply not true.

rektide 4y ago
> a basic, essential function required for webapps to be able to have elementary cross-tab capabilities Simply get out of here. Clipping my argument down to fit a contrite cheezy meanspirited vacuous soundbite rebuttal is gross & lacks respect. My statement is absolutely true. Go spread empty misleading hate somewhere else.
- robertoandred 4y ago
  "Cross-tab capabilities" are not basic or essential either.
  - rektide 4y ago
    I think the answer is, it depends. It's been a pretty common-sense part of the web for a decade, powers a lot of experience, & allows developing much better user experiences in many cases. If you have an experience that needs to work across tabs, the alternatives are barbaric & crude & difficult, fault prone, & often waste network traffic. As usual, the Apple fanboys show up to defend the prison they're locked into. By crudely rejecting basic longstanding technology. Typical. I'd like to see a little more high-road in some discussions, something beyond snide defensiveness.
    - robertoandred 4y ago
      And what kind of experience needs to work across tabs?
      - rektide 4y ago
        A spreadsheet. A chat app. A document editor. A map editor. Anything where information is on screen & needs to be live. Aka, what a huge part of the web today does.
        robertoandred 4y ago
        Except all that information is on screen, shared live, via the web. A chat app talking to the next tab in the window isn’t worth much.
        postalrat 4y ago
        So what you do when your users have 20+ tabs open to the same service? Have each tab keep just itself up to date?
        robertoandred 4y ago
        Is 20+ tabs of the same service, each needing the exact same data, a common scenario?
        rektide 4y ago
        It depends. Sometimes, yes, users do have many different conversations going & tabs for different conversations. Or they might be flipping between different sheets in the spreadsheet. And perhaps those sheets have cross relationships. Or perhaps the user changes which sheet they're looking at & has old data. Whether or not it's common doesn't change that it's a concern that good developers strive to develop for, and it's something that ought be expected. Tabs are part of the web, are something that support user-agency, and it ought to be common that they are well supported. Now, we can start doing the job we ought to do.
        postalrat 4y ago
        The "exact same data" is often some change. Like user statuses in Slack. It's not terribly uncommon. Opening a bunch of tabs is up to the user. I develop web apps for business users and often they open many tabs. But even me on reddit or hn I'll open a bunch of tabs to basically queue up reading.
- dang 4y ago
  This kind of flamewar comment will get you banned here. I don't want to ban you, so please stop posting like this. More at https://news.ycombinator.com/item?id=31682131 https://news.ycombinator.com/item?id=31682131.

> a basic, essential function required for webapps to be able to have elementary cross-tab capabilities Simply get out of here. Clipping my argument down to fit a contrite cheezy meanspirited vacuous soundbite rebuttal is gross & lacks respect. My statement is absolutely true. Go spread empty misleading hate somewhere else.

robertoandred 4y ago
"Cross-tab capabilities" are not basic or essential either.
- rektide 4y ago
  I think the answer is, it depends. It's been a pretty common-sense part of the web for a decade, powers a lot of experience, & allows developing much better user experiences in many cases. If you have an experience that needs to work across tabs, the alternatives are barbaric & crude & difficult, fault prone, & often waste network traffic. As usual, the Apple fanboys show up to defend the prison they're locked into. By crudely rejecting basic longstanding technology. Typical. I'd like to see a little more high-road in some discussions, something beyond snide defensiveness.
  - robertoandred 4y ago
    And what kind of experience needs to work across tabs?
    - rektide 4y ago
      A spreadsheet. A chat app. A document editor. A map editor. Anything where information is on screen & needs to be live. Aka, what a huge part of the web today does.
      - robertoandred 4y ago
        Except all that information is on screen, shared live, via the web. A chat app talking to the next tab in the window isn’t worth much.
        postalrat 4y ago
        So what you do when your users have 20+ tabs open to the same service? Have each tab keep just itself up to date?
        robertoandred 4y ago
        Is 20+ tabs of the same service, each needing the exact same data, a common scenario?
        rektide 4y ago
        It depends. Sometimes, yes, users do have many different conversations going & tabs for different conversations. Or they might be flipping between different sheets in the spreadsheet. And perhaps those sheets have cross relationships. Or perhaps the user changes which sheet they're looking at & has old data. Whether or not it's common doesn't change that it's a concern that good developers strive to develop for, and it's something that ought be expected. Tabs are part of the web, are something that support user-agency, and it ought to be common that they are well supported. Now, we can start doing the job we ought to do.
        postalrat 4y ago
        The "exact same data" is often some change. Like user statuses in Slack. It's not terribly uncommon. Opening a bunch of tabs is up to the user. I develop web apps for business users and often they open many tabs. But even me on reddit or hn I'll open a bunch of tabs to basically queue up reading.
dang 4y ago
This kind of flamewar comment will get you banned here. I don't want to ban you, so please stop posting like this. More at https://news.ycombinator.com/item?id=31682131 https://news.ycombinator.com/item?id=31682131.