Memcached is a distributed in-memory cache implementation, it has nothing to do with noSql. See: http://code.google.com/p/memcached/
Incorrect
Memcached is a key/value store, which doesn't use SQL or RDBMS concepts and is therefore by definition a noSQL project.
The fact that it is an in-memory cache implementation is irrelevant.
Memcached is a distributed in-memory cache implementation, it has nothing to do with noSql. See: http://code.google.com/p/memcached/
Incorrect
Memcached is a key/value store, which doesn't use SQL or RDBMS concepts and is therefore by definition a noSql project.
The fact that is an in-memorty cache implementaion is irrelevant.
I try not to plug in more than one vaccuum cleaner.
You don't know what your missing. There's nothing more satisfying then vacuuming together with your mother/girlfriend. Using the same socket definitely adds to the excitement.
We've just bought our sixth vaccuum cleaner to expand our vaccuum cleaning parties.
Offer companies tax credits to reduce emissions and fine them for exceeding but letting them pay to pollute is a joke.
So what is the difference between fining them for exceeding and letting them pay for exceeding?
Why would you imagine that tubes would be easier or cheaper to build underground? Tunnels are expensive! No, our tubes will be mostly above ground, which will also provide a better view while we're using them.
They might provide a better view while we're using them but not while were not using them
Eventually, transportation will become a commodity that we will not consider worthy of spending our precious and rare ground-level space for.
Now that would be an interesting poll: how long before our cities get rid of these dirty, ugly & dangerous cars?
Agreed. The transportation of the future will not be in the air but underground where tubes can be kept at almost vacuum and "cars" can move very fast using magnetic leviation at very low energy consumption.
The future cities will be beautiful
"Uncompressed ASCII is universal."
Big endian or little endian? It's not as universal as you may think.
Endianness is irrelevant for ASCII. It only determines the order of bytes within multi-byte words. ASCII is 7-bit and therefore, there is no difference between "big endian ASCII" or "little endian ASCII".
No. They are not compiled and therefore lag behind the state of the code in almost every software project I have encountered so far. If you can choose between naming and commenting, use naming. For example, a parameter called ZeroBasedIntegerIndex will be in your editor's autocompletion and therfore visible where you use it. A comment is only visible where you define it, and therefore gets lost in usage. And if the ZeroBasedIntegerIndex happens to be defined as a string, you'd change it immediately. The comment would probably stay wrong for a very long time.
So you are actually promoting the use of variables named like ZeroBasedIntegerIndex?
That name really sucks, dude. I understand that you want to clarify the advantage of good variable naming, but ZeroBasedIntegerIndex is NOT a good example. Names should describe what the variable means semantically.
Why isn't this ranked informative?
Cause the moderators have learned what "Le" means?
Well, that's stupid.
Rule #1. 0
I didn't post the whole algorithm for the sake of brevity and humor.
You must be new here
"Why should we subsidize intellectual curiosity?" -Ronald Reagan