deanmao / node-chimera

A new kind of headless webkit integration for nodejs; a great alternative to phantomjs.
http://www.deanmao.com/2012/08/13/enter-chimera/
MIT License
847 stars 45 forks source link

no longer being maintained? #44

Open mkoryak opened 10 years ago

mkoryak commented 10 years ago

Judging by the number of pull requests opened - some of which are many months old, is it fair to say that this project is no longer being worked on?

deanmao commented 10 years ago

I guess I've been working on it, but mostly on my company's private repo. I should probably port some of the changes over to the open source project.

mkoryak commented 10 years ago

+1 :)

dhendo commented 10 years ago

Great - I'd love to get this working in production - currently I'm using Phantom + websockets (as a communications channel) to convert a given snippet of HTML to a png to send back to the client.

html in node -> websockets -> phantomjs -> png (base64) -> websockets -> node (base64 decode to buffer) -> out to web client.

With this setup, the latency is pretty poor, so cutting out some of the layers and being able to pass around node buffers with chimera would be awesome.

ghost commented 10 years ago

So, still have plans to get the open source version up and running again?

mercmobily commented 10 years ago

+1 on this. I need to decide between node-webkit and chimera. Frankly, chimera seems like the best option, but at the moment it doesn't look like it's getting much love...

fabiocicerchia commented 10 years ago

+1, looking forward for bug fixes and new features ;)

mercmobily commented 10 years ago

@deanmao Dean, node-chimera as a project has a lot of stars, it's talked about on the internet a lot, and it is the only way, currently, to have a headless browser without the burden of an executable. Plus, it's the only think that would run no nodejitsu.

Saying "I guess I've been working on it, but mostly on my company's private repo. I should probably port some of the changes over to the open source project." is a little ambiguous, and I think it would be nicer to have a more definite update. "I guess I've been working on it"? "Porting some of the changes over"? What about existing pull requests and bug reports? What about new development?

I think what you did was fantastic, and am immensely grateful that you released it. Really, really "thank you".

I have some questions:

If not, maybe it would be more appropriate to have a notice on the project's page, saying "Looking for a new maintainer". I am sure one of the 723 people who starred it would only be happy to step in -- well, at least I hope so!

Once again, thank you for releasing it!

konobi commented 10 years ago

+1, I love this approach... makes much more sense to me

mfrye commented 10 years ago

+1 This sounds awesome, I've been looking for something like this. What's the current status of the project?

Pampattitude commented 10 years ago

Bumpity bump, I would also like hearing if this project is still maintained.

adampatarino commented 10 years ago

Update? Is this being maintained or not?

mkoryak commented 10 years ago

I would venture to say that it is not.

nousacademy commented 9 years ago

private repo aka building proprietary software...

mercmobily commented 9 years ago

@deanmao Dean, the stars have become 814. I think developers around the world are still looking forward to a couple of answers:

Thanks

doctorXWrites commented 8 years ago

@deanmao @here i don't think its maintained actively. I think its time to create something from scratch, that is truly open source and maintained by a community not an individual. Is there such an option already available ?

konobi commented 8 years ago

I've been using zombie.js as an alternative.