you can get the same effect with whatever is a plus lens for you, though. So if your normal rx is -1.5, do close work without glasses.

With plus lens therapy, you only wear the plus lens while doing close work. If you were wearing the plus lenses while looking more than a few feet away, you wouldn't be doing plus lens therapy.

DHH said there are things about the "large tent" aspect of rails that are annoying. That's not the same thing as being unhappy with the overall direction of the project.

Are you implying that there wasn't controversy over the Big Dig? I remember plenty.

I read the article as having a strongly anti Chinese bias. So I think Shivetya's point was a fair one which is "Should this be a story on government mishandling of big projects" as the lead and move away from the Chinese bashing? Or is there a legitimate angle for the overall story about the fact the cheapest bid also happened to be a Chinese company.

The communication problems detailed in the article, coupled with the pre-construction work that was completed in China and then shipped across the Pacific, makes a difference when it comes to the management of the project.

That's not to say that these are unique problems because the contracting firm was Chinese, rather than, say, French. However, in this case it is relevant to the overall narrative that the challenges exist, because they make it that much harder to proactively address quality deficiencies.

The second doesn't follow from the first. At most, you could say that people MAY calculate that running a tor relay is no longer worth it, but you could also say that without bringing up the (almost completely unrelated) daycare example.

If only that were true! My first employer was a large organization that explicitly embraced the waterfall methodology that we all rightfully deride.

Tried Etymotic earbuds? They come with a bunch of adapters to fit different sized ears. My model is of course discontinued but the mc5 looks closest. http://www.etymotic.com/ephp/mc5.html

edit: unlike any other earbuds I have tried, they are engineered to survive the inevitable wax-plugging. Just replace the filter & you're back in business.

Took me a couple months to reliably understand my first landlord in Boston, a 3rd or 4th generation American of Italian ancestry.

Unless there are multiple secured domains hosted on that IP address, in which case knowing the domain would be extra information.

You can't have multiple secure domains on a single host which don't require the user to know a non-standard port without exposing the domain in plain text as part of SNI.

You can if you have a certificate with multiple domain names in the SAN[0] field.

[0] http://en.wikipedia.org/wiki/SubjectAltName

Even if your UI is all in JS, Rails still saves a ton of work as an API server compared to Sinatra.

Any examples? My experience with Rails and Sinatra on a daily basis for the last two years has proven the exact opposite.

That's definitely a decent list, but the problem for me is that you are also forced to have EVERYTHING ELSE! It's all nicely required in the for you in your app and there aren't straightforward ways to remove 90% of the stuff you don't want.

I work with rails every day for the last 6+ years and it was a revelation when I started. Now I still think it works decently well for large web-apps, but it's just grown way to big over the years. Basecamp is awesome and a great proving ground, but I'd wager the vast majority of apps written in RoR come no where close to needing most of what's included today.

I'm curious as to why having that stuff available is a bad thing?

memory overhead (both for the machine and human), modifying core classes unnecessarily, complexity of third party software, setting defaults to on that aren't applicable to 90% of apps (see turbolinks which breaks the way the web and browsers work).

I'll admit to being on a hard-core minimalist, simplicity, explicit coding kick recently, so I'm already biased against behemoth frameworks. Rails is wonderful if you need that level of complexity/features. I don't think most apps do and we're "forcing" everyone to write basecamp when that is overengineering for most apps.

I'd add security to that list. Rails' most notorious vulnerability was the result of an on-by-default feature that 90% of developers never even needed. I'm not suggesting that Rails is inherently insecure or that Sinatra/Rack cannot be exploited, but less unnecessary code leaves less potential for vulnerabilities; this is especially true in the Ruby world where many developers are eager to `gem install` anything with a few stars on github.

meh, I'm not convinced. I've written some very complex APIs and sinatra-contrib covers most ancillary needs. I'm not saying Rails is always the wrong choice for an API, but most of the bullet points listed in this guide are covered or unnecessary. If you have tons of sprawling back-end logic that is exposed through your API, Rails makes sense, but time and time again I've seen first-hand how much more quickly Sinatra gets us up and going and it's always less work for new developers to grok the application flow.