Linked by Fran van der Merwe on Mon 5th Jul 2010 18:13 UTC

Thread beginning with comment 432529
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.
RE[4]: Comment by Captain Halibut
by Moochman on Mon 5th Jul 2010 23:13
in reply to "RE[3]: Comment by Captain Halibut"
my point was simply that when big important rewrites like that happen, it's pretty common to leave out little-used features in order to reduce the potential for bugs... honestly any PC running Windows Vista or 7 that has a FireWire port should have an Ethernet port and likely Wi-Fi as well, all of which let you make point-to-point connections and share documents.... so I don't see what the big deal is.
FireWire is great, but FireWire networking on Windows was certainly never a "killer feature". On the Mac on the other hand the Target Drive Mode actually is something of a killer feature, it just sucks that MacBook (not Pro) owners are missing out on it these days.
RE[5]: Comment by Captain Halibut
by dumdiddydum on Tue 6th Jul 2010 08:45
in reply to "RE[4]: Comment by Captain Halibut"
honestly any PC running Windows Vista or 7 that has a FireWire port should have an Ethernet port and likely Wi-Fi as well, all of which let you make point-to-point connections and share documents.... so I don't see what the big deal is..
having wifi, ethernet or whatnot for network connectivity is sure enough unless you need/want more network interfaces for, let's say, some ad hoc connections. which i frequently do.
also, about microsoft axing FW networking: it's the very fact that ms tries to make all users happy (which often leads to bloated UIs and config overkill) which contradicts that theory.
Member since:
2007-06-12
yeah, cause MSFT can't afford the resources to do firewire networking and because Vista wasn't delayed or anything and had so much time to add it.
Edited 2010-07-05 23:04 UTC