3 ms·
That was then, and this is now. In the old days, seperate profiles were used to seperate Moms browsing from Dad's browsing. Now, we need different profiles to
by mverwijs 10y ago
That was then, and this is now.
In the old days, seperate profiles were used to seperate Moms browsing from Dad's browsing. Now, we need different profiles to browse: one for shopping, one for banking, one for work...
Seems to me that coders forget that people evolve. Same with Moxie saying that it is fine for WhatsApp not ticking the 'tell me when the key changed'-box by default because that confuses people. Perhaps it /did/ confuse people, when security was not a known issue. People tend to learn, in my experience. You can't say: "Well, we did an A/B test in 2002 and now we're done for the next millenium."
- WorldMaker 10y agoUh, right, people could use one for shopping, one for banking, one for work, etc... but they'd like them all to be in the same window so they can switch between them as tabs... (It's funny when you realize that the old ProfileManager predates tabs.) Which is where we arrive today with Mozilla's work on "container tabs". The code and UX evolve, too. I'm not sure what your complaint here is, mverwijs? That Mozilla should test Firefox starting up with the ProfileManager again? Like I said, I think "container tabs" might be a good way to do this in a way that mainstream users might pick up and this will be interesting to watch. (I guess one trick that might be interesting if there was a way to easily "graduate" from I know/love "container tabs" to "oh, the next thing I can try is profiles to do more complicated things", but I think the answer is that profiles will adapt more to work with "container tabs" UX than "container tabs" UX will adapt to the old profiles UX. Given "incognito" tabs in other browsers can be seen as a specialization of a "container tab"/"profile tab", I suspect mixing profile tabs in a single browser window is a UX that is here to stay.)