-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HeadlessChromium vs Node #25
Comments
I don't have firm plans, just trying. The potential benefits that I see :
|
Yes, the setup right now is not good. I think the main problem is actually the whole Cario, Rsvg stuff, that seems pretty brittle. Maybe things will become more stable once BinDeps2 is used for that, but who knows... |
I'll have another go also at making the whole NodeJS setup more robust. It just feels weird to install a full HTML browser rendering engine for this :) Were there specific things that were brittle that you saw happening? At least in my experience, the NodeJS stuff seemed to work very reliable, the issue was more Cairo.jl and Rsvg.jl, at least in terms of getting them installed. |
A bit of an update here. I think I've gotten the NodeJS.jl setup pretty stable now, so I think using node directly should be mostly ok at this point? Cairo.jl and friends still worry me. BUT, my understanding is that the folks that are building the new BinDeps2 story will take a crack at porting Cairo.jl over to the new BinDeps2 framework. I think that should make that part of the story much, much more stable. So maybe the best strategy for now is to just stick with what we have on |
I have one more update on this: I taught a class using julia this semester, and at some point also used VegaLite.jl. I had all students install VegaLite.jl and use it on their machines. Wasn't a huge number (10), but I believe it worked out of the box for everyone, which was encouraging. |
I see that you are replacing the Node.js stuff with HeadlessChromium. Was there a problem with the node stuff or do you see some other benefit?
The text was updated successfully, but these errors were encountered: