I'm not a kid, kid. I know what's the difference. The Open Source definition was irrelevant back then, if you read the summary, you'll notice that the date there predates the day of the OSD and the various different rules it has - The source being available pretty much meant it was open source back then.
They do serve a purpose. My website isn't malicious. However, since I use a no-ip.org domain, MSN doesn't allow me to link to it in conversations. Similarly, I'm the programmer and owner of an IRC bots which distributes google results - Tinyurl helps me reduce the number of characters I write per URL, and therefore I can pack more results in a single message, reducing the chance of hitting flood protection.
Additionally, they are useful anywhere a huge URL looks out of place - Email conversations, in-line citations, etc.
It has nothing to do with broken build scripts. It's a feature against broken installers that check for the major version number. It has nothing to do with a corrupt development culture - It happens with freeware too.
No, that's wrong. 6.1 is used for backward compatibility reasons because some broken installers/programs used the first digit of the version as a check. If they didn't do that, Windows 7 would've been NT 7.
I don't know how they couldn't. The thing is so bloated and slow, and degrades system resources so much, you'd think people would go "Hey, WTF is going on here?"
No, they won't LimeWire hardly uses any significant system resources unless your computer is from the 90s.
Of course they don't. It's a firefox thing. You take them out of the system-wide-plugins directory and it goes away. It's only on every user account if you use the 1.1 version.
Well considering you're probably the only person on your machine who cares about an addon that doesn't do anything other than report CLR version for proper ClickOnce support, I guess that's a fair compromise.
Define "fine." Last I checked, you have to uninstall it separately in every user account on your machine, instead of just uninstalling it once.
Well considering you're probably the only person on your machine who cares about an addon that doesn't do anything other than report CLR version for proper ClickOnce support, I guess that's a fair compromise.
Because of this: http://tech.slashdot.org/comments.pl?sid=1367735&cid=29414697
You just havn't looked well enough. I see M$ everywhere.
The mirrors were the problem, actually. It's probably faster to download the latest ISO and install it from there.
Good going MS! Add a few hours to that and they might beat the time it took for a few people I know to upgrade Ubuntu!
So what? The RTM has been updating for weeks now. It'll be part of the first updates you install.
Well man, if she's a chimera too we're fucked.
Well if you read the summary it's obvious that open source was a bit different back then.
I make a distinction between open source, 'The' Open Source, and F/OSS. Maybe you don't, maybe I misread the summary and they don't. Oh well.
It was 1967's definition of open source. You're confusing open source with 'the' Open Source.
I'm not a kid, kid. I know what's the difference. The Open Source definition was irrelevant back then, if you read the summary, you'll notice that the date there predates the day of the OSD and the various different rules it has - The source being available pretty much meant it was open source back then.
I'm referring to the fact that the parent was talking about the FSF definition of Free Software, not that RMS invented "Freedom".
Open source means the code is available. Nothing else.
What you're looking for is GNU/Freedom.
I'm not sure how PayPal can be cheaper than $0. Do they give you money when you do transactions? Seems not.
They do serve a purpose. My website isn't malicious. However, since I use a no-ip.org domain, MSN doesn't allow me to link to it in conversations. Similarly, I'm the programmer and owner of an IRC bots which distributes google results - Tinyurl helps me reduce the number of characters I write per URL, and therefore I can pack more results in a single message, reducing the chance of hitting flood protection.
Additionally, they are useful anywhere a huge URL looks out of place - Email conversations, in-line citations, etc.
6.1 was chosen for backwards compatibility reasons. Some installers checked the major version number and used it as a version check. It's really 7.0.
It has nothing to do with broken build scripts. It's a feature against broken installers that check for the major version number. It has nothing to do with a corrupt development culture - It happens with freeware too.
No, that's wrong. 6.1 is used for backward compatibility reasons because some broken installers/programs used the first digit of the version as a check. If they didn't do that, Windows 7 would've been NT 7.
There are many copies!
I don't know how they couldn't. The thing is so bloated and slow, and degrades system resources so much, you'd think people would go "Hey, WTF is going on here?"
No, they won't LimeWire hardly uses any significant system resources unless your computer is from the 90s.
*sigh*
Of course they don't. It's a firefox thing. You take them out of the system-wide-plugins directory and it goes away. It's only on every user account if you use the 1.1 version.
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.6a1-candidates/build1/win32/en-US/
Setup version.
Then you uninstall the plugin the same way MS installed it - As a system-wide plugin.
Well considering you're probably the only person on your machine who cares about an addon that doesn't do anything other than report CLR version for proper ClickOnce support, I guess that's a fair compromise.
Define "fine." Last I checked, you have to uninstall it separately in every user account on your machine, instead of just uninstalling it once.
Well considering you're probably the only person on your machine who cares about an addon that doesn't do anything other than report CLR version for proper ClickOnce support, I guess that's a fair compromise.
Shorter instructions: 0. Tools - Addons 1. Select addon and click on "Disable".
The .NET plugin has been removable for quite some time now. MS released a fix shortly after 1.0 came out. So many people do not seem to know this.