waxjar

I'd rather mock stuff like this with a mocking library that doesn't involve making requests to remote servers. The interwebs are (relatively) slow and I want my tests to run fast.

Their servers are located in the US according to the article.

That's all very nice, but what about the rest of the world?

It's not :) Running things concurrently means that you finish two or more tasks in the same time period. Running things in parallel means those things happen at the same time.

> "millions of private contractors"

?

To me it's style, mostly. I used to just buy books, then got home, started reading and discovered I really couldn't stand the style of writing or the tone. I try to sample a little bit now.

Chrome.

It's a 2011 macbook pro.

I left this open in a tab on the background with the intention to check it out later. It froze my machine.

The idea an sich is good. In light of last week's news however, I'll stick with 1Password.

GMail does send what you've typed to their servers and stores it as a concept so you don't lose your work in case your browser or computer crashes. I seriously doubt the NSA has access to that stuff, but technically it would be more or less possible ;)

An iCloud keychain? No thanks.

"Media" isn't a collective noun, in the same way that "apples" isn't a collective noun. It's the plural form of "medium".

That headline makes me cringe. Media is the plural of medium, they do things, they don't does things.

The URL has probably been submitted already once. You can try adding a question mark or a bogus query to re-submit a URL which has been submitted before.

If it did the same as GMail does and GMail didn't exist, I would. It's just so convenient.

Ruby has a tainting mechanism, but I don't believe it's used very much.

http://www.ruby-doc.org/docs/ProgrammingRuby/html/taint.html

Not everyone has a blazingly fast internet connection. I don't, even Hackernews loads slow for me at times.

If you want to scale, you'll have to reach me at some point and you won't reach me with a huge app that takes me 30 seconds to load.

It has something to do with the size of your app, though.

The metric OP uses (total # packages dived by the # years the language exists) is misleading.

Node.js is new, a lot of people are trying to solve a lot of problems that aren't solved yet. Once they're solved and have a more or less standard solution the rate at which new packages are released will drop, simply because most problems will have been solved.

Having had a look at the Gemfiles, it might be the choice of HTTP server used. I believe defaults to WEBrick, if no other server is present and I believe WEBrick is single-threaded.

I don't have any experience with JRuby, but this might be a possibility.

Im surprised to see that Sinatra on JRuby often performs worse than Sinatra on MRI, while Rack on the other hand performs much better.

Tiny error: in Ruby global variables start with $, class variables start with @@.

What's needed is a system to sync state (read items, starred items, etc), preferably one that only you have access to. I propose a standard file format, implemented by RSS Readers that contains this kind of data. The file can be stored on a service like Dropbox. If implemented correctly, you'd never lose your data when switching clients and you'd be able to use different clients on different platforms with your own data.

Kut is dutch slang for vagina, though.

I don't think I am and I don't see how this makes it okay. Services that want to track people shouldn't be opt-out in the first place. It isn't obvious to anyone without some knowledge of computers (the vast majority of people) when they're being tracked.

This is irrelevant. Google Analytics can be included on any website that wishes to do so.

You can try not using Google services (which is nearly impossible in the first place), but there's no getting away from Google Analytics and countless similar services without installing ad-blockers and browser extensions like Ghostery.

> but the real question is: why do you care?

Translate what Google does to the analog world. It might look like this: some guy following you around in every shop, every café you eat. He'll note what you buy, what you talk about, what you don't talk about. He'll read your mail to see what interests you (and your friends!). I hope this will help you answer "the real question".

That's a good point and likely the reason this won't ever happen. The upside for app developers is that they won't have to run their own servers or rely on a commercial third party to keep state in sync.

I think the developers of a couple of the biggest RSS readers should get together and decide on a standard file format to store "metadata" such as read items, starred items, etc.

This file could be stored on a server or in a user's Dropbox folder. It would allow users to pick an RSS reader freely (per platform), without losing and rebuilding all their data. It also keeps all this metadata in sync, one less worry for the developers.