Linked by Thom Holwerda on Wed 25th Aug 2010 19:21 UTC
Thread beginning with comment 438233
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2006-09-27
In my opinion, good window management and tab management should be part of the window manager. If any application thinks it has to implement tabs or any sort of MDI to be good, then the window manager has failed.
Agreed. That sounds like a typical case of the "inner platform effect": http://en.wikipedia.org/wiki/Inner-platform_effect But of course, in practice, using ION3 or dwm has its drawbacks, so browser tabs come handy.
The obvious solution is for the app to improve its support for multiple windows. Maybe the ultimate solution would be RAM data deduplication, which may also make it possible to use static linking where it wouldn't make sense at present.