If you need to use ten year old hardware, do you need to use x86-64?
If you are using something like the DEC Alpha or the early Itaniums, then you will need 64bit support (albeit not x86-64). Then again, you won't be running Windows 2000.
actually you can get copies of every MS product right back to DOS 3 via technet.
Technet is not a retail channel for typical consumers to get a single product. Also, the older products aren't supported and generally don't work on the new hardware around today.
because some FOSS project is FAR FAR more likely to stop producing updates and go offline (because they got a life/job/girlfriend) then a company like MS or nvidia which has actual funding
NVIDIA has already shown they are willing to drop driver support for their products when they aren't interested anymore. And it's not just about the risk of if they will stop support, you also need to factor in the damage done - we don't have the option to fix the proprietary stuff ourselves even if we wanted to, but we could fix the abandoned FOSS stuff if we considered it worthwhile.
As most of you know KDE uses both Konqueror and Dolphin for file navigation.
Konqueror is a web browser, it just happens to support Dolphin as a plugin. So nope, no change here. It's other browsers, like Firefox, which insist on making local file browsing look like an autogenerated Apache index.
To be fair to the troll, this wasn't always the case. Konqueror was a web browser and file browser, then Dolphin came along later causing some overlap. This overlap has now been mostly resolved.
I just had a quick look at the NVIDIA website and it does say they need to be kept in sync:
Note: You can only install this driver if you have the installed the latest GeForce Graphics drivers v196.21.
I guess they started focusing on releasing new drivers since the 3D craze started up again. It also only seems to be supported on 8 series and above graphics cards, whereas they had support for the LCD shutter glasses (including brands other than NVIDIA) with older video cards a while ago.
See this thread as an example of NVIDIA dropping support for the older hardware.
I actually think the splitting of the campaigns is a good thing as it enables them to develop the story further and provide more content. I do however agree with the LAN issue - it seems most games I am interested in these days doesn't have a reasonable way of playing offline LAN games.
Until NVIDIA randomly stops supporting the drivers. I remember a while back when their stereo drivers and GPU drivers were separate downloads and had to be kept in sync, and they just stopped releasing stereo drivers when newer GPU drivers came out. Is this still the case?
Philosophically, the two systems are different. But from a practical perspective, the end result comes out to be the exact same.
Or am I totally off-base?
I wouldn't say the result is exactly the same, as a lot of the time system updates on Linux trigger a restart of the daemons to ensure the new version is loaded in memory. This isn't always the case, which means your point does have some merit.
There is also the chance that the user will finish using a particular affected application as they don't need it at that time, and then come back to it later. A slim chance of loading the patched binaries in this situation isn't bulletproof, but it's better than guaranteeing the files won't be patched until the reboot.
Firstly, what do you mean ? Secondly, how is this a security issue ?
A lot of Windows Updates require a reboot because in Windows land you can't overwrite files that are in use. This is a security issue as you are still vulnerable to the flaw it patched after you apply the update but before you reboot.
The smallest MacBook Pro you can get with the switchable graphics is a 15", which isn't much of a space saving over the OPs current 17" laptop when you consider they were thinking about netbook sized machines.
I've read that some tiling window managers can do this kind of thing, but I'd rather go with 'classical' window managers, like Openbox/Gnome/KDE or similar.
Awesome is indeed awesome, if you don't mind some manual editing of the lua configuration file.It should fit the OP's requirement nicely.
The requirement stated that they were aware of things like Awesome, but that option doesn't appeal. How does this fit the requirement, again?
I guess I'm a fool then. I can't stand the comma being at the start of the line, I feel it should be at the end. Also, I think your attempts at formatting didn't work correctly, I'm guessing the comma should be in the same column as the curly brace but on my screen it isn't (off by one space).
A single space is usually not enough indent to allow easy scanning of multiple nesting levels. Block-indentation has to be significantly different than intra-character indentation, or they start to blend too much (j and m are nearly half a space apart, depending on font face).
If you care about code indenting and aren't using a monospaced font, you have other issues to worry about here...
Except that DX10 hardware was around before Aero was released so what you needed was last generation hardware, not next generation, to get the feature. It also relied on newer drivers, the Intel 915 supported DX9 but didn't support Aero (the whole Vista Capable lawsuit). We're talking about new hardware supplying reasons to buy the hardware, not new software taking advantage of long existing hardware.
Of course it would be rigid, my point was that it would have to be strong to stay rigid without disintegrating. The person I was replying to suggested it could be weak.
Slashdot Mirror
If you need to use ten year old hardware, do you need to use x86-64?
If you are using something like the DEC Alpha or the early Itaniums, then you will need 64bit support (albeit not x86-64). Then again, you won't be running Windows 2000.
actually you can get copies of every MS product right back to DOS 3 via technet.
Technet is not a retail channel for typical consumers to get a single product. Also, the older products aren't supported and generally don't work on the new hardware around today.
because some FOSS project is FAR FAR more likely to stop producing updates and go offline (because they got a life/job/girlfriend) then a company like MS or nvidia which has actual funding
NVIDIA has already shown they are willing to drop driver support for their products when they aren't interested anymore. And it's not just about the risk of if they will stop support, you also need to factor in the damage done - we don't have the option to fix the proprietary stuff ourselves even if we wanted to, but we could fix the abandoned FOSS stuff if we considered it worthwhile.
so you'll need use a better example
So you'll need [to] use a better excuse.
As most of you know KDE uses both Konqueror and Dolphin for file navigation.
Konqueror is a web browser, it just happens to support Dolphin as a plugin. So nope, no change here. It's other browsers, like Firefox, which insist on making local file browsing look like an autogenerated Apache index.
To be fair to the troll, this wasn't always the case. Konqueror was a web browser and file browser, then Dolphin came along later causing some overlap. This overlap has now been mostly resolved.
Note: You can only install this driver if you have the installed the latest GeForce Graphics drivers v196.21.
I guess they started focusing on releasing new drivers since the 3D craze started up again. It also only seems to be supported on 8 series and above graphics cards, whereas they had support for the LCD shutter glasses (including brands other than NVIDIA) with older video cards a while ago.
See this thread as an example of NVIDIA dropping support for the older hardware.
I actually think the splitting of the campaigns is a good thing as it enables them to develop the story further and provide more content. I do however agree with the LAN issue - it seems most games I am interested in these days doesn't have a reasonable way of playing offline LAN games.
Until NVIDIA randomly stops supporting the drivers. I remember a while back when their stereo drivers and GPU drivers were separate downloads and had to be kept in sync, and they just stopped releasing stereo drivers when newer GPU drivers came out. Is this still the case?
The comparison was to Monster Cables, not Apple or Microsoft.
Na, it's just running an inefficient spinlock while waiting.
Philosophically, the two systems are different. But from a practical perspective, the end result comes out to be the exact same.
Or am I totally off-base?
I wouldn't say the result is exactly the same, as a lot of the time system updates on Linux trigger a restart of the daemons to ensure the new version is loaded in memory. This isn't always the case, which means your point does have some merit.
There is also the chance that the user will finish using a particular affected application as they don't need it at that time, and then come back to it later. A slim chance of loading the patched binaries in this situation isn't bulletproof, but it's better than guaranteeing the files won't be patched until the reboot.
I don't see people joining Greenpeace and saying "Hey now, Genetic Engineering's alright y'all".
I tried, and was rejected. Only difference is that I didn't say "y'all".
Firstly, what do you mean ? Secondly, how is this a security issue ?
A lot of Windows Updates require a reboot because in Windows land you can't overwrite files that are in use. This is a security issue as you are still vulnerable to the flaw it patched after you apply the update but before you reboot.
if your CPU can do at HD natively then that's optimal. Which is any C2D, though I guess that means at least a mATX case, not a dinky little ion box.
Tell that to my C2D E6300 in a mBTX case paired with a 7600GS. Even then it struggles at times with 1080p H.264.
Or more with switchable, like macbook pro.
The smallest MacBook Pro you can get with the switchable graphics is a 15", which isn't much of a space saving over the OPs current 17" laptop when you consider they were thinking about netbook sized machines.
Those IT guys control the firewall so probably didn't need to bother with making the business case.
I've read that some tiling window managers can do this kind of thing, but I'd rather go with 'classical' window managers, like Openbox/Gnome/KDE or similar.
Awesome is indeed awesome, if you don't mind some manual editing of the lua configuration file.It should fit the OP's requirement nicely.
The requirement stated that they were aware of things like Awesome, but that option doesn't appeal. How does this fit the requirement, again?
I guess I'm a fool then. I can't stand the comma being at the start of the line, I feel it should be at the end. Also, I think your attempts at formatting didn't work correctly, I'm guessing the comma should be in the same column as the curly brace but on my screen it isn't (off by one space).
I still think it is easier to configure my shell than it is to convince a large number of programmers out there to do exactly what I want them to do.
A single space is usually not enough indent to allow easy scanning of multiple nesting levels. Block-indentation has to be significantly different than intra-character indentation, or they start to blend too much (j and m are nearly half a space apart, depending on font face).
If you care about code indenting and aren't using a monospaced font, you have other issues to worry about here...
Made more fitting by this attempt of a first post not being first.
I think Ill increase my smoke break frequency from now on.
And the cigarettes will surely undo any minor benefits gained from walking outside.
Diamond is extremely stiff, but if used as armour it would probably just shatter like glass when struck by a bullet.
You wouldn't really need to alter the DNA. Just build the arm directly.
Twinkle twinkle little porn star.
Except that DX10 hardware was around before Aero was released so what you needed was last generation hardware, not next generation, to get the feature. It also relied on newer drivers, the Intel 915 supported DX9 but didn't support Aero (the whole Vista Capable lawsuit). We're talking about new hardware supplying reasons to buy the hardware, not new software taking advantage of long existing hardware.
Of course it would be rigid, my point was that it would have to be strong to stay rigid without disintegrating. The person I was replying to suggested it could be weak.