Linked by Thom Holwerda on Fri 22nd Oct 2010 18:18 UTC
Thread beginning with comment 446945
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 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
More News »
Sponsored Links



Member since:
2010-03-08
But IME that abstraction becomes a hindrance because you have to work around it whenever it doesn't work reliably (which was far too often, also IME).
If that was their way of thinking, it was just idiotic, because as you said...
-Either network connections work/have minor issues, and systray icons are everything you need
-Or they don't work and you need to fix it, in which case you don't want over-abstractions of the computer network going in your way anyway.
Plus even if you consider network abstractions hiding the hardware, they can be done much better than with the Network Center way. See network manager on linux : the network abstraction is used, but it's complete with per-network settings like static/dynamic IP.
Contrast with Win7 : this summer, when I made a LAN on an ad-hoc wifi network, it was only to discover that I had to dive in the internals of the control panel to manually switch DHCP on and off when switching between the Internet router and the ad-hoc network.
Edited 2010-10-25 12:36 UTC