Most of what they've done seems to be rearchitecting, not getting a simple speed boost from using an unmanaged language. They're bypassing the OS to get more locality and cache retention. Those problems would not be addressed by merely rewriting in C++.
They're also keeping more data in memory and eschewing relying on the the OS file cache. It seems like they're taking every opportunity to use the in memory representation to avoid using sstables. They try harder than Cassandra to update instead of invalidate that cache on writes.
What problem does this language solve? How can I make it precise?
How can I show it solves this problem? How can I make it precise?
Is there another solution? Do other languages solve this problem? How? What are the advantages of my solution? of their solution? What are the disadvantages of my solution? of their solution?
How can I show that my solution cannot be expressed in some other language? That is, what is the unique property of my language which is lacking in others which enables a solution?
What parts of my language are essential to that unique property?
Actually you're not supposed to copy and paste the code. That would definitely not be the hard way. You are supposed to retype the examples yourself, just like back when books were print only.
Right, economics lives in a world of games with artificial rules. Great for finding a strategy for a game with two colors of counters moving from column to column. Applying it to anything resembling real life is negligent at best.
According to TFA, it is already used in Ethiopia to denote sarcasm, and can be distinguished from the Spanish usage of the same character by its location at the end of a sentence rather than the beginning.
AppConstants.AUTH_KEY ? A salt that is Constant through out the App? That is not the same thing as a Random salt for every User.
The whole point of not storing plain text passwords is if somebody gets access to your DB. And in that case the only advantage of using one salt through out is that the attacker can't use a precomputed rainbow table for your hash function with out a salt. Instead they will have to compute ONE rainbow table for the one salt you used. When many salts are used rainbow tables are no longer useful. Just like GP said, two users with the same password will have the same hashed passwords in your DB, because they all use the same salt.
Again, if your not concerned about "Somebody getting a copy of my DB and getting the hash keys," then why are you bothering to hash the passwords?
Then you don't understand Godwin's Law. Sure actions can be reprehensible. But saying 'You know who else had evidence burnt? Hitler!' means the discussion has suddenly taken on a screeching tone and rational discourse is derailed. Far fetched comparisons to Hitler's regime are not constructive and you have not showed how they are.
Funny thing is though, PostgreSQL have been meaning to drop the SQL from their name and go back to just Postgre. In every joke there is a little bit of truth.
The team installed HookSafe on a machine running Ubuntu 8.04, and found the system successfully prevented nine real-world rootkits targeting that platform from installing or hiding themselves.
Of course they didn't detect any rootkits installing themselves, that's exactly what an installed rootkit would prevent them from seeing.
Slashdot Mirror
Most of what they've done seems to be rearchitecting, not getting a simple speed boost from using an unmanaged language. They're bypassing the OS to get more locality and cache retention. Those problems would not be addressed by merely rewriting in C++.
For one, they've replaced the OS network stack with an in-process one, where each thread gets its own NIC queue so they can have "zero-copy, zero-lock, and zero-context-switch[es]"
They're also keeping more data in memory and eschewing relying on the the OS file cache. It seems like they're taking every opportunity to use the in memory representation to avoid using sstables. They try harder than Cassandra to update instead of invalidate that cache on writes.
"The Computer made me do it."
Pretty funny that you would bring up twitter, since they migrated from ruby to scala because of the very same issues brought up in this thread.
http://marshallbrain.com/manna1.htm
The Darwinia and Multiwinia code has also been available (for a price): http://store.introversion.co.uk/product_info.php?products_id=66 , but this is the first I'm aware of the DEFCON code being released.
License linked from humble bundle: http://www.introversion.co.uk/uplink/developer/license.html
See here
Actually you're not supposed to copy and paste the code. That would definitely not be the hard way. You are supposed to retype the examples yourself, just like back when books were print only.
Reminds me of this short
Right, economics lives in a world of games with artificial rules. Great for finding a strategy for a game with two colors of counters moving from column to column. Applying it to anything resembling real life is negligent at best.
I think gp is refering to the nasa pix. A lot of the cloud formations in those pictures look doubled up.
obligatory xkcd
You might be surprised how many mundane scenes are actually CGI: http://www.youtube.com/watch?v=clnozSXyF4k
According to TFA, it is already used in Ethiopia to denote sarcasm, and can be distinguished from the Spanish usage of the same character by its location at the end of a sentence rather than the beginning.
AppConstants.AUTH_KEY ? A salt that is Constant through out the App? That is not the same thing as a Random salt for every User.
The whole point of not storing plain text passwords is if somebody gets access to your DB. And in that case the only advantage of using one salt through out is that the attacker can't use a precomputed rainbow table for your hash function with out a salt. Instead they will have to compute ONE rainbow table for the one salt you used. When many salts are used rainbow tables are no longer useful. Just like GP said, two users with the same password will have the same hashed passwords in your DB, because they all use the same salt.
Again, if your not concerned about "Somebody getting a copy of my DB and getting the hash keys," then why are you bothering to hash the passwords?
Created 2010-06-07 03:00AM
Tech cult No. 1: The Slashdot Samurai
Then you don't understand Godwin's Law. Sure actions can be reprehensible. But saying 'You know who else had evidence burnt? Hitler!' means the discussion has suddenly taken on a screeching tone and rational discourse is derailed. Far fetched comparisons to Hitler's regime are not constructive and you have not showed how they are.
That's not irony, that's corruption.
are you kidding? it says 27 all over the place... but it's not his age. He's actually 41
The previous record holder was 15 when he set the record. This guy is 27. And I don't think Scott had an arcade cabinet in his house in 1982.
Funny thing is though, PostgreSQL have been meaning to drop the SQL from their name and go back to just Postgre. In every joke there is a little bit of truth.
And what is the plan for people who don't have computers that meet the system requirements? stand by and let them buy an old game, used?
Did they learn nothing from that movie? A genetic screening may show propensity for a disease, but it will never measure the human spirit.
The team installed HookSafe on a machine running Ubuntu 8.04, and found the system successfully prevented nine real-world rootkits targeting that platform from installing or hiding themselves.
Of course they didn't detect any rootkits installing themselves, that's exactly what an installed rootkit would prevent them from seeing.