News for hackers. Stuff that matters.
Re:Neon: Node plus Rust by rvikmanis on Wednesday December 23, 2015 @09:45PM (#10786794)
Could be killer if combined with electron.
Re:Neon: Node plus Rust by derefr on Wednesday December 23, 2015 @10:36PM (#10786979)
If the goal is having a fast "business-rules engine" coupled to a pretty HTML5-based app-wrapper, one of my own projects is to combine Electron with the Erlang VM.

Rather than trying to go whole-hog on linking the two worlds together at a process level, I've just embedded an Erlang release into the Electron package, which decompresses itself to the user's Library/APPDATA dir on Electron startup, transparently registers as a service (so it can continue to run for things like server sync when the app is quit), and then communicates with the app using Unix domain sockets.

It's a bit like the feeling of having a Service Worker, but one that just happens to be able to embed things like physics engines inside of it.

Re:Neon: Node plus Rust by shadeless on Wednesday December 23, 2015 @11:29PM (#10787123)
Using Erlang in a desktop application sounds great, do you have any code online somewhere? Or could you make a gist? I would love to see how you made that work.
Re:Neon: Node plus Rust by lucaspiller on Thursday December 24, 2015 @04:55AM (#10787698)
You might want to look into BERT [0], I think there is a JavaScript library. We used it a few years ago to call Ruby from Erlang, it wasn't fast at the time, but it did what we needed it to do.

[0] https://github.com/blog/531-introducing-bert-and-bert-rpc

Re:Neon: Node plus Rust by mmastrac on Wednesday December 23, 2015 @11:03PM (#10787062)
I'm doing the same thing with a JVM. I had to fix the bug where named pipes on Windows were totally busted in Electron before I could make any progress.
Re:Neon: Node plus Rust by derefr on Wednesday December 23, 2015 @11:28PM (#10787118)
Ah, I ran into that problem (I think?) and had been just using regular IP sockets as a stop-gap, planning to switch back over after it was fixed. I'm glad to hear someone with knowledge of Electron internals ran into it as well; I feel bad that I didn't file it as a bug, though.
Re:Neon: Node plus Rust by mmastrac on Wednesday December 23, 2015 @11:31PM (#10787126)
If you're curious, the fix was here: https://github.com/atom/electron/issues/1968

It made it out into the regular release and I think it's fixed but TBH I haven't tested for a few months.

My work is all on GH here as well: https://github.com/orbitaljs There might be some synergy here between the projects.

Re:Neon: Node plus Rust by arca_vorago on Thursday December 24, 2015 @07:05AM (#10787913)
Give me this but with Elixir and Im sold.
Re:Neon: Node plus Rust by alexnewman on Thursday December 24, 2015 @02:33PM (#10789333)
why elixir over rust? I'd assume rust makes more sense because you don't need gc
Re:Neon: Node plus Rust by ajholyoake on Thursday December 24, 2015 @06:35AM (#10787860)
What is electron in this context? (The ex-atom maybe?)
Re:Neon: Node plus Rust by dubcanada on Thursday December 24, 2015 @08:37AM (#10788098)
Yes
Re:Neon: Node plus Rust by ZenoArrow on Thursday December 24, 2015 @05:21AM (#10787741)
Great idea. Also wonder if using Neon to speed up Electron could give a noticeable performance boost to Atom.
Re:Neon: Node plus Rust by davej on Wednesday December 23, 2015 @10:01PM (#10786851)
Why particularly with Electron?
Re:Neon: Node plus Rust by paulddraper on Wednesday December 23, 2015 @10:06PM (#10786879)
Presumably because Electron needs to be hackable/customizable for lots of devs and performant for lots of workloads.