mpobrien

This is a tool to analyze large goroutine stacktrace dump files, to assist in debugging by parsing the dump and displaying it in a structured table.

It works entirely client-side (no data is uploaded or stored), groups together goroutines with identical stacktraces into a single entry, and allows quickly sorting/filtering/searching.

Remapping caps lock to ESC has been my preferred method for this, I'd suggest giving it a try!

Isn't that still missing the point? We don't want to be spied on period, whether there are things to hide or not.

That's about what I would have guessed too, except I think "documentation" is "wiki", and "merging" is "pull requests".

The icons for pull requests and branches are far too similar to each other, in my opinion.

Looked at loom.com, don't get what this site does.

Looked at loom.com/about and read wall of text, still not sure.

I'd suggest finding a more efficient way to communicate what this site is to newcomers.

But isn't suing to enforce his patent rights also an expensive legal battle that he would need to somehow fund? I don't see how this threat could be seen as effective.

Some people, when confronted with a problem, think "I know, I'll use Javascript!"

Now they have NaN problems.

The stars animation behind that logo seems to be using quite a bit of CPU...

I love it. Instead of MMS though, reminders via instant message (gchat/aim/whatever) would be nice.

That's Portuguese.

It's not mentioned in the article, but using the MULTI command (exposed as client.multi() in this module) can sometimes help alleviate this if you need to execute multiple redis commands whose inputs/outputs do not depend on each other.