Spawn needs a new name about spawnling HOT 18 CLOSED

+1 spown

from spawnling.

+1 spork

from spawnling.

Genghis Khan had lots of offspring so how about "khan"? Do you have a "khan do" attitude?

from spawnling.

"Spark" is good, but also in use (though it appears to be a dead project)

It doesn't have quite the same meaning, but how about "respawn"?

Or to keep with the original theme, "roe" and "offspring" are both available.

from spawnling.

I've been giving it more thought and am considering keeping the name and, instead, changing the syntax to something like this:

Spawn.new do
  stuff
end

Or maybe,

Spawn.run do
  stuff
end

This sort of change would also make it easier to pull out of ActiveRecord so that you can run it anywhere.

from spawnling.

That would be much better!

from spawnling.

Spark +1

from spawnling.

I took this as an option to learn about forking, setting up a github repo, and making it a gem. So I did "Spawner".

But I also vote for the Spawn.new or Spawn.run, particularly as that's cleaner to understand what is happening. In my case, though, I'd make it: Spawner.new or Spawner.run

I like "Spawner" because it's the thing that spawns... i.e. a Driver drives... a Coder codes.

from spawnling.

I like Spawn.new or Spawn.run

from spawnling.

+1 for Spawn.run

Is the gem completely broken under Ruby 1.9? I tried to make the necessary name changes but couldn't seem to get it working ...

from spawnling.

whatever name it is, can it be implemented soon please? :-)
right now because of the name hijack, I get "wrong number of arguments" ...

from spawnling.

I tried to fork the 'edge' branch and change the name but I can't seem to get it to work. Has anyone else had any luck?

from spawnling.

I'm going with Spawn.run

from spawnling.

Good call, tra. +1 for Spawn.run

I look forward to seeing it work. :-)

from spawnling.

Is there an ETA on the change to Spawn.run? The gem seems to be completely broken under 1.9.2.

from spawnling.

ETA = whenever I stop being so damned lazy!

from spawnling.

tra, I posted a pull request for this, hopefully that'll make it easier on you. :-)

from spawnling.

Spawn.new is what I settled on. I chose that because it returns an object which you can use to monitor the spawned process. Unfortunately, the name "spawn" is already used in another gem which doesn't actually spawn anything. So the gem is called "spawn-block" for now. If that's too confusing I may go with a name change after all but we'll see how this goes.

from spawnling.