I don't think the 'business world' make their decisions based on Slashdot news articles either... although that could be a mistake. Maybe SCO would've made some better choices if they did.
In the same way that 1 + 1/2 + 1/4 + 1/8 + 1/16 +... is less than 2.
Every single bit you add on to the end is smaller than the last bit and if it's small enough then it'll never be as big as 2. While we can't ever say what it is equal to we can say with absolute certainty that it's less than 2 and we can say with even more certainty that it's less than 42 and since both 42 and 2 are finite then the sum must be.
It shows beyond a shadow of a doubt how stumped Microsoft are.
They must've sat for hours thinking of how to solve their problem and simply could not come up with an answer. Their software model cannot cope with this sort of thing so their only advice is to avoid using the internet properly.
It's something we've all known all along. Open source works better.
The whole point of a naming convention is that your convention is the same as my convention. This means if you need to read my code for some reason you can easily fit in with where a Class appears and where a var appears. Maybe I decide to use CAPITAL_LETTERS for any public field whereas everyone else is using it for a constant.
Confusion ensues. It's the out side of Postel's Law. When you're writing code you should take the time to make your code use a sensible naming convention. Case-sensitivity is just one way the compiler can encourage you to pick a good one.
Slashdot Mirror
I don't think the 'business world' make their decisions based on Slashdot news articles either... although that could be a mistake. Maybe SCO would've made some better choices if they did.
In the same way that 1 + 1/2 + 1/4 + 1/8 + 1/16 + ... is less than 2.
Every single bit you add on to the end is smaller than the last bit and if it's small enough then it'll never be as big as 2. While we can't ever say what it is equal to we can say with absolute certainty that it's less than 2 and we can say with even more certainty that it's less than 42 and since both 42 and 2 are finite then the sum must be.
It shows beyond a shadow of a doubt how stumped Microsoft are. They must've sat for hours thinking of how to solve their problem and simply could not come up with an answer. Their software model cannot cope with this sort of thing so their only advice is to avoid using the internet properly. It's something we've all known all along. Open source works better.
The whole point of a naming convention is that your convention is the same as my convention. This means if you need to read my code for some reason you can easily fit in with where a Class appears and where a var appears. Maybe I decide to use CAPITAL_LETTERS for any public field whereas everyone else is using it for a constant. Confusion ensues. It's the out side of Postel's Law. When you're writing code you should take the time to make your code use a sensible naming convention. Case-sensitivity is just one way the compiler can encourage you to pick a good one.
Firebird does it already. Even using Shift+Enter for a .net address and Ctrl+Shift+Enter for a .org.
Firebird Keyboard Shortcuts