foca

Yeah, it definitely depends on the use case. Some websites just "make sense" on responsive layouts. Others… not so much :)

I have no idea :P

But that's the case for which I use raw + save instead of download the zip / clone :)

For JavaScript or CSS single-file projects it's actually quite simpler to wget the one file from the Raw URL (or copy-paste the contents into a new buffer in your editor), than to clone/download the archive and then move the file from the downloaded directory and then clean up the other downloaded files.

edit For example, `curl https://raw.github.com/documentcloud/backbone/master/backbon... > js/lib/backbone-min.js`

Get those pull requests merged! :)

We did, and then we dropped it because a _very_ small percentage of users were on non-English locales.

Ah, my Family Game, how many hours did I invest in it while growing up? Those "999 in 1" cartridges were awesome :)

Love it :)

One suggestion, show small flags next to people in the list view as well, with the name of the country in the title attribute.

For all the respect you can have to Yehuda, please don't compare him to Feynman :)

Heh, rails' time_ago_in_words, but right :P

Well the obvious reason is mentioned in the article: most people already do have a facebook account, while G+ is still new for most of the internet.

If you are likely to be on facebook, you probably already are. I don't think it's surprising the growth is decreasing.

I would be (pleasantly) surprised if the growth was negative, but that's not going to happen :P

Co-located teams are better off with sticky notes and whiteboards as long as the client is also in the same room :)

Either way, I work from South America for clients in the US, so I like having these tools around. Specially when they innovate in any way. That means better tooling for communicating with my clients, which is the #1 problem of distributed teams :)

Chat hooks! I want hipchat (or campfire, w/e) to say "Joe commented on…" etc. Specially new items, comments and status changes.

Then I could configure github to notify sprintly and sprintly to notify the chat, instead of getting all the pushes in the chat, which is too noisy IMO.

Oh man, I can't even begin to… I mean, this is written in DJANGO?! Who thought of THAT?! :D

ps: congrats on finally launching ^^

Yep, it needs an API and webhooks.

The idea of asking the credit card up-front is that it makes it clear that it's a paid service.

I personally dislike it, but probably stump can give a better insight on why he chose this workflow.

In this regard I love what Chile is doing with Startup Chile. You guys seriously need something like that, where you just grant visas to smart founders.

I still wouldn't like to live in the US, but I totally support that you become more open :)

When was it that you used it? I haven't used it lately, and when I did I felt the same as you, but for what I've seen Dojo is no longer the "kitchen sink" it used to be. It's small, VERY modular, and has a lot of utilities and interesting things.

Not that jQuery doesn't have any of these. But jQuery was thought out as a DOM manipulation library and then people started sticking a ton of things on top of it.

Dojo is thought out as a modular toolkit, where DOM manipulation is just one of the libraries it includes.

The specific point is that the evented model is not designed as a "one size fits all" solution. It's great for certain scenarios, not very good for certain others.

Basically, the original blog post tries to get to this, remarking on node.js is sold as if it was the silver bullet of web servers, that will scale to anything for anything you .

Of course, you can try to adapt most problems into something that would work in an evented model, but you have to know VERY WELL what you're doing.

IMO the solution is simple: polyglotism. Have parts of your app in node. Other parts in python. Others in ruby. Whatever works best for each specific small part :)

Node is not useless, but it's definitely not my choice to program everything and anything. Same thing with, for example, Rails :)

git?

Thanks! I didn't know of that url. How did you find it? It doesn't seem to be linked anywhere in the site.

The guys at c2 have already figured this one out: http://c2.com/cgi/wiki?CommunityLifeCycle

Also, if you're into how communities work and why how they succeed/fail/implode, you should definitely look at Meatball wiki: http://meatballwiki.org/wiki/

Welcome to the future. Sadly, we don't have jetpacks or flying cars yet.

I really disagree with your point on the community valuing monkeypatching so much. Yes, it's a tool. Yes, it has it's place. No, it's not the favorite tool in our belt. And no, it's not something you should use always. At least, IMHO.

"We receive about 100 status updates per day". 5 years later, the average number of tweets per day is 140 MILLION.

(According to http://blog.twitter.com/2011/03/numbers.html)

He didn't say libs were well documented. He said ruby libraries usually have the same or similar structure/coding style.

The point is that it's oftentimes easier to grep the source for something than to track down said thing in google.

SPECIALLY because ruby libs tend to be horribly documented, but most times with simple-ish code to understand.

And, moreover, if you see a library that does too many weird things and you can't follow, it means that probably the code is shit and it's time to look for an alternative :)

I don't think this is necessary. The solution is to go to your project's mailing list, irc room, ask your twitter followers, or whatever, and ask for a new maintainer. Even messaging the users who actively report issues can be a good idea.

Once you have a new maintainer, announce it, open a support request in http://support.github.com asking them to re-root the network to the new maintainer's fork, and then change the description of your repo (a one click change) to something like "this is no longer maintainer, check http://github.com/otheruser/repo

Yes, it takes a while, but then when you solve it, you give the community a new maintainer. So I think it's a better solution than just marking it as abandoned :)

Yeah, but adding a whole organization for each open source repo? I have tons of small gems/libraries that solve one specific problem, and all enjoy their share of users/

I don't want to setup a bunch of organizations just because they might change owners at some point in the future.

indeed. My only regret is not being able to downvote him

Upvoted for funny book name.

Oh, wait, this isn't reddit. Damn.

Ease of signup. If all I have to do is click a "sign in with my facebook account" and I don't have to sign up for yet another site, I might be compelled to join your site and thus be your customer.

Not saying facebook login is the best way to do this, but as a user, it's comfortable enough.