As has been explained a million times already, many distros up their major version number when they break binary compatibility. Mandrake 9.x uses KDE3 whereas Mandrake 8.x uses KDE2, as an example. And before you harp on about KDE, KDE3 uses Qt3, which isn't binary compatible with Qt2. KDE3 is largely source compatible with KDE2.
I seem to recall there being a number of forgive-and-forget cases when it came to companies nicking GPL code. Hell, anyone remember the NVIDIA kernel module thing?
Err...Unreal was originally written as a software rendered engine. Glide happened to be close enough to how the Unreal engine worked (at the time) for Epic to quickly code in Glide support before they shipped.
Err...did they forget about DS9? Let's see, major change of mission at the end of season 2 (From helping establish Bajor to the first line of defence), new and powerful enemy (The Dominion), ship designed for war (The Defiant), new uniforms and hair styles in later seasons.
I'm sorry, but this is by no means "a first for Trek", unless you buy into the B&B revised history.
Simple; modern English is essentially a mixture of many languages, most from Europe. Back in ye olde days, the English language wasn't that sophisticated, so the solution was to hack bits of foreign language onto English, the end result being the somewhat "interesting" modern English.
The state of 1.4 is a lot better than what the 0.9.x releases were. The 1.0 branch took so long because it was their first stable release and they wanted to get it right. Since then, the changes have been more on the side of enhancements and performance imporovements rather than architectural change, so the code is already in pretty decent shape.
Mozilla and Firebird (And probably other Mozilla-based browsers) have options to disable Javascript-based window resizing. I must say I'm surprised Opera doesn't support it.
I think he means keeping the thread busy until the end of its quantum. A thread blocking before the end of its quantum leads to more contex switches per second, meaning more overhead and lower performance.
The reason that people say the keyboard and mouse controls are better simply because if you take 2 people of equal skill level, give one a kb + mouse and the other an XBox controller, the kb + mouse player will trounce the XBox controller player.
The problem with upping the -j count beyond (number of procs + 1) is you're going to get more and more overhead from caches being flushed and general overheads of context switching.
Well, that is interesting, seeing as my CVS tree doesn't have those files, or that directory. It's the tree I do my source builds from so I know it works.
Wrong wrong wrong wrong wrong. When using X, Win32 and MacOS APIs, there's no mouse driver code in Mozilla, except to handle things like mouse-over events and button presses, and this sort of stuff gets put in XPToolkit because that's just what toolkits do. Whether the mouse is PS/2 or USB is of no significance to Mozilla at all.
What was wrong with the old method of stamping the frequency on the chip? My old K6-200 had "200MHz" (or sommat) stamped on one of the corners. You couldn't change it or remove it without making it obvious it had been tampered with.
So, you think we should move to 64-bit after we hit the major limitations of 32-bit, rather than before? Why? After all, there's an awful lot of code that isn't 64-bit clean, so there is going to have to be a transition period. It's better to do that while there's still breathing room left in 32-bit architectures.
This machine, my home computer, has 1GB of RAM. This time last year, it had around 512MB. The year before it was around 256MB. Judging from that pattern, I'll hit 4GB in 2005.
No, I don't need 1GB, but it makes things much more comfortable. I can simply stop working on my latest project and play a few rounds of UT2003 without everything going swap mad or having to shut down all my programs. I've got plenty of disk cache to increase performance of disk-IO intensive operations and I've got breathing room for when I want to do something really memory intensive, I won't have to worry about my system grinding to a halt from swapping like mad.
And one final thing, my housemate's 3rd-year compsci project was seriously hampered because his computer and the workstations in the labs were only 32-bit. He was working on an awfully large problem space and fitting the arrays required into 4GB was nigh-on impossible without re-architecting the entire program, which would likely result in results that aren't easily comparable to previous work.
Err...what? Copyright isn't like trademarks, you can enforce selectively. After all, they can hand out a beta saying "you can't distribute this" and sue anyone who breaks that agreement. They can chose not to and it won't hurt them one iota in a future case.
It's ironic you complain about misunderstandings that "get blurted out here on slashdot time and time again" when you yourself are doing it.
Slashdot Mirror
As has been explained a million times already, many distros up their major version number when they break binary compatibility. Mandrake 9.x uses KDE3 whereas Mandrake 8.x uses KDE2, as an example. And before you harp on about KDE, KDE3 uses Qt3, which isn't binary compatible with Qt2. KDE3 is largely source compatible with KDE2.
I seem to recall there being a number of forgive-and-forget cases when it came to companies nicking GPL code. Hell, anyone remember the NVIDIA kernel module thing?
Err...Unreal was originally written as a software rendered engine. Glide happened to be close enough to how the Unreal engine worked (at the time) for Epic to quickly code in Glide support before they shipped.
Which is where the train comes in...
Eh? It's an 1800+ that does 166*12.5, which is what a 2600+ is. Ergo, it performs just like a 2600+.
Err...did they forget about DS9? Let's see, major change of mission at the end of season 2 (From helping establish Bajor to the first line of defence), new and powerful enemy (The Dominion), ship designed for war (The Defiant), new uniforms and hair styles in later seasons.
I'm sorry, but this is by no means "a first for Trek", unless you buy into the B&B revised history.
Simple; modern English is essentially a mixture of many languages, most from Europe. Back in ye olde days, the English language wasn't that sophisticated, so the solution was to hack bits of foreign language onto English, the end result being the somewhat "interesting" modern English.
I got an 1800+ that does 2600+. It cost me less than 80 quid. This was a couple of weeks ago. Where's my 80 quid 2600+?
Opera's DOM engine is largely slower than both Mozilla and IE's.
See http://www.greymagic.com/dagon/results.html for details.
Show me one comprehensive report demonstrating Opera has better CSS support than Gecko.
The state of 1.4 is a lot better than what the 0.9.x releases were. The 1.0 branch took so long because it was their first stable release and they wanted to get it right. Since then, the changes have been more on the side of enhancements and performance imporovements rather than architectural change, so the code is already in pretty decent shape.
Mozilla and Firebird (And probably other Mozilla-based browsers) have options to disable Javascript-based window resizing. I must say I'm surprised Opera doesn't support it.
I think he means keeping the thread busy until the end of its quantum. A thread blocking before the end of its quantum leads to more contex switches per second, meaning more overhead and lower performance.
But they're source and binary compatible...
The reason that people say the keyboard and mouse controls are better simply because if you take 2 people of equal skill level, give one a kb + mouse and the other an XBox controller, the kb + mouse player will trounce the XBox controller player.
The problem with upping the -j count beyond (number of procs + 1) is you're going to get more and more overhead from caches being flushed and general overheads of context switching.
Actually, BitTorrent scales very well, so it could probably withstand a Slashdotting just so long as the torrent file is accessible.
Well, that is interesting, seeing as my CVS tree doesn't have those files, or that directory. It's the tree I do my source builds from so I know it works.
Wrong wrong wrong wrong wrong. When using X, Win32 and MacOS APIs, there's no mouse driver code in Mozilla, except to handle things like mouse-over events and button presses, and this sort of stuff gets put in XPToolkit because that's just what toolkits do. Whether the mouse is PS/2 or USB is of no significance to Mozilla at all.
I strongly recommend you read the parent post. He was claiming snipers are cheaters. I questioned that assertion and you just proved my point.
Oh pleas, how can snipers be cheats when they're part of the design of the game? It's like saying skiers are cheats in Tribes 2.
What was wrong with the old method of stamping the frequency on the chip? My old K6-200 had "200MHz" (or sommat) stamped on one of the corners. You couldn't change it or remove it without making it obvious it had been tampered with.
So, you think we should move to 64-bit after we hit the major limitations of 32-bit, rather than before? Why? After all, there's an awful lot of code that isn't 64-bit clean, so there is going to have to be a transition period. It's better to do that while there's still breathing room left in 32-bit architectures.
This machine, my home computer, has 1GB of RAM. This time last year, it had around 512MB. The year before it was around 256MB. Judging from that pattern, I'll hit 4GB in 2005.
No, I don't need 1GB, but it makes things much more comfortable. I can simply stop working on my latest project and play a few rounds of UT2003 without everything going swap mad or having to shut down all my programs. I've got plenty of disk cache to increase performance of disk-IO intensive operations and I've got breathing room for when I want to do something really memory intensive, I won't have to worry about my system grinding to a halt from swapping like mad.
And one final thing, my housemate's 3rd-year compsci project was seriously hampered because his computer and the workstations in the labs were only 32-bit. He was working on an awfully large problem space and fitting the arrays required into 4GB was nigh-on impossible without re-architecting the entire program, which would likely result in results that aren't easily comparable to previous work.
A number of ISPs seem to be introducing download quotas, placing a per-MB charge on [A]DSL connections. Thus, spam will end up costing those folks.
Err...what? Copyright isn't like trademarks, you can enforce selectively. After all, they can hand out a beta saying "you can't distribute this" and sue anyone who breaks that agreement. They can chose not to and it won't hurt them one iota in a future case.
It's ironic you complain about misunderstandings that "get blurted out here on slashdot time and time again" when you yourself are doing it.