Slashdot Mirror

I think you need to read up on what the system does instead of blindly following it.

PHP used to use the crypt() function, which would generate a DES or MD5 hash. In PHP 5.5 they introduced the password_hash function to replace this, but it has a mode that generates backward-compatible crypt() style hashes, so if you pass the wrong arguments to it, you will be generating md5 (or worse) hashes.

I don't mean to sound rude (even though you did say you thought I knew "fuck all") but you really need to understand what you're doing. Saying "I used password_hash so I'm golden" just isn't good enough for security. This why I repeat, storing your passwords so they are not accessible is the only solution - as far as both of us know, you've been storing your passwords in something not far off plain text anyway.

To be fair you probably are using bcrypt, but don't keep thinking that's a done deal either - this guy shows you why you should not use bcrypt :-)

Modern ruby is the cleanest, most elegant, expressive and fastest of the big 4. It offers a bigger standard library (gems(40,000) vs cpan (25,000) vs pypi (1,022)), a wider selection of interpreters and platforms (IronRuby, JRuby, Rubinius,Cardinal, etc), not to mention much better documentation and educational resources.

Ruby is used by a wider group of people and in a wider area than it ever has been. Also, there's a lot of other really great languages out there you should consider before you idolize one language as perfect. Erlang and Haskell are amazing and certainly worth checking out. Not to mention node and the javascript revolutionaries (which some people abhor.) A lot of people get stuck on their first language I encourage you to branch out and try Ruby at least. You'll find a much different language than you seem to think.

1. AMOS Basic
2. Lattice C
3. Perl
4. PHP
5. Python
6. Ruby
7. Erlang

To be fair, FailWhale has not been seen by me of late, and the Twitter devs attribute their salvation to Scala. However, there are some pretty good arguments that the Twitter developers Mother of All Fail was initially trying to write their own hand-rolled message queue instead of simply using one off-the-shelf.

See this and leave off your trolling. Ruby has its problems, and performance is one of them, but scaling is not so long as you don't re-invent shitty event systems yourself (like Twitter did).

The problems they had were not due to Rails. The problems arose from poor implementation of their message queue... some bad engineering decisions.

http://unlimitednovelty.com/2009/04/twitter-blaming-ruby-for-their-mistakes.html

And some of their recent Scala noise might be due to the fact that Alex Payne just wrote a book about Scala that was just released, or is about to be.

Ruby does not have a problem scaling. Neither, for that matter, does even Rails. (As the companies that run Basecamp, Campfire, LinkedIn, Lighthouse, and many others will tell you.)

The fact is that the Twitter folks tried to write their own message queue in Ruby, when there was absolutely no reason to do so: there were plenty of pre-made message queues already available for Ruby, and already optimized. Not only did they choose to write their own, unnecessarily, they did it badly.

And not only that, but Alex Payne has a hidden agenda: he is trying to push Scala to boost interest in the book about Scala he just wrote!

Please get some facts before digging up this long-dead and well-buried "Ruby or Rails doesn't scale" bullshit again.

http://unlimitednovelty.com/2009/04/twitter-blaming-ruby-for-their-mistakes.html

This blog post takes the attitude that Twitter didn't move to Scala because ROR had a problem, but because the in-house messaging system Twitter created performed poorly. The author does not work at Twitter but many of the Twitter developers (including Alex Payne) respond in the comments. I found the article to be very interesting and the comments even more so. They give a sense of how much research Twitter did before this change.