digger250

This is a consequence of money getting more expensive. When rates are low, investors pile money into non-revenue producing startups in hopes that something will return 1000x. Now rates are up and the smart money is moving elsewhere.

Yes. As well as asbestos and occupational exposure to inhaled particles.

You'd still have your token though.

You are not affected, but there are people in the world besides yourself who do things differently than you.

Huh? I thought the title was a perfect description of the article. A dude who mostly uses ruby optimizes a piece of Python code. That's it.

I think AWS needs a good UX designer. I find that using AWS can be overwhelming at first. Here's a few suggestions:

1. Take "Amazon" out of every product name. Have a look at this list for example: http://docs.aws.amazon.com/general/latest/gr/aws_service_lim... This adds nothing but clutter to the page.

2. Stop calling everything "Simple". If it's simple, people will be able to tell for themselves. Calling things simple potentially makes people feel dumb if they have a problem with it.

3. The sheer number of offerings (over 18 groups with multiple items) on the "Services" tab of the AWS management console is overwhelming. I'd have a designer see if there was a better way of organizing things.

There are only 10 or so remaining issues in the beta milestone.

When I run the benchmark in C-ruby (2.0.0) I get:

  real	2m35.450s
  user	2m35.257s
  sys	0m0.139s

On jruby with invokedynamic:

  time ruby -Xcompile.invokedynamic=true file2.rb C-large-1.in

  real	1m17.711s
  user	1m15.618s
  sys	0m0.830s

In jruby without invokedynamic time ruby file2.rb C-large-1.in

  real	1m37.856s
  user	1m39.260s
  sys	0m0.854s

Salting the password should defeat the rainbow table, right?