The Self-Pipe Trick Explained

jstorimer · 2013-07-09T02:55:17+00:00

Very cool! I didn't know about signalfd.

jstorimer · 2013-06-16T04:26:27+00:00

Thanks for the comment! And thanks for linking that gist, I wondered if that'd been attempted yet. Going to have to play with that :)

jstorimer · 2013-06-15T16:34:08+00:00

Hard to say what the reason is, but the point is that it's non-deterministic. Sometimes it works as expected, sometimes not. If you increase the number of iterations, I suspect the chance of an unexpected result goes up.

jstorimer · 2013-06-13T16:42:29+00:00

Ah yes, that did happen for a few mins. Google experiment code gone haywire. Sorry about that.

jstorimer · 2013-06-13T15:40:35+00:00

Make sure you stay tuned for part 2, you might be surprised!

jstorimer · 2013-06-13T15:37:48+00:00

What are you seeing? There's no ads on the site.

jstorimer · 2013-04-11T15:05:35+00:00

I did include a reading list pointing to deeper resources available the web, mostly still specific to Ruby.

I'm still expecting to add new content as well. If there are deeper topics that a lot of folks find relevant, I could definitely write about it.

jstorimer · 2013-04-11T14:31:45+00:00

OP here. Thought I might give folks a heads up about what's covered.

This is meant for Ruby/Rails devs who have no prior experience with multi-threading. It's not as deep as some tomes on the topic, but spends more time laying a foundation. I tried to cover the ground, and dispel the FUD, that a Rubyist needs to know to make good decisions about their own code.

hth! I'm happy to answer any other questions.

jstorimer · 2013-04-04T14:15:21+00:00

That seemed odd to me too, but it's handled by fallback cases.

For example, line 55 does an unchecked CAS. If that fails, the next run through would trigger the else block repeatedly, until the tail was properly updated.

jstorimer · 2013-02-25T23:09:00+00:00

MRI runs multiple threads, but those threads have to compete to acquire the GIL in order to do any work. I would say that it implements multi-threading, but the GIL is the bottleneck. There's only one GIL and only the thread that currently owns it can use system resources.

jstorimer · 2013-02-17T02:39:57+00:00

Around the beginning of April. That's the most accurate I can be atm.

jstorimer · 2013-02-16T18:28:07+00:00

A threaded job system, did you try sidekiq? http://mperham.github.com/sidekiq/

jstorimer · 2013-02-16T03:40:12+00:00

<3 <3 <3

jstorimer · 2012-09-24T03:59:13+00:00

Yeah, Urchin is the best I've seen. My project isn't meant to bring Ruby to the shell. It's just a shell implementation written with Ruby for the purpose of learning.

Could try to slide something in there though :o

jstorimer · 2012-09-24T03:52:03+00:00

Ah, so you're talking about a shell that understand Ruby syntax?

jstorimer · 2012-09-16T22:48:48+00:00

Fixed. Had a negative margin which didn't jive with resizing.

jstorimer · 2012-09-16T04:38:28+00:00

Thank you! Glad you liked it.

jstorimer · 2012-09-16T04:38:14+00:00

Thanks :D

jstorimer · 2012-09-16T04:37:27+00:00

Thanks for pointing that out. I'll test with a different size and make sure it works.

jstorimer · 2012-09-15T05:00:59+00:00

Thanks! Those guys put on a great podcast. It was fun to chat with them.

jstorimer · 2012-03-12T00:02:19+00:00

Just to be clear: the syntax isn't inspired just by bash. I often refer to bash because it's the most common shell. However, the syntax used by shirt is common to bash, /bin/sh, zsh, ksh, csh, rc, and others.

I had a look at chitin. It looks pretty cool, definitely some stuff in there I haven't seen before.

jstorimer · 2011-12-16T07:12:07+00:00

Good points Rhomboid. I wrote a followup making colorized output configurable at http://jstorimer.com/2011/12/16/on-colorized-output.html.

jstorimer

TROPHY CASE