Activity Status

[camertron]

Hey guys,

I've been playing around with Helix tonight and so far it's been an awesome experience, thank you! I'm concerned about using it for a project however because it doesn't appear to be very actively maintained or worked on. The last commit was 10 months ago and a number of issues and pull requests have been languishing for a while too. Is Helix still going places?

[wagenet]

As a contributor, I can speak for myself and say that I would still like it to!

[zw963]

at least，many guys like me still keep pay attention to this project. 😄 Peter Wagenet <notifications@github.com> 于 2019年4月5日周五 下午10:28写道：

…

As a contributor, I can speak for myself and say that I would still like it to! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#164 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAhhBmctkn8GQUfyPAKGA0IpJaH0XNhLks5vd12fgaJpZM4ceMpL> .

[wycats]

@camertron in general, this project is active for the use-cases it supports naturally. In particular, that means that we support calling into Rust with a String or simple payload, doing some work in Rust, and then getting the result back.

In terms of our original (very ambitious) roadmap, that means the stuff in "Greenfield Project" (which is complete) is the core feature set of Helix. Reasonable next steps would be stuff in the QoL section, as well as making it dead-easy to use Helix in a situation where the user has a Rust compiler in their environment.

We should definitely adjust our marketing and documentation to make these details clear.

[camertron]

Ok thanks @wycats. I ended up writing a C extension instead because Helix didn't support module nesting, i.e. module Foo; class Bar; end; end. I also wanted to use refinements, although truth be told I couldn't figure out how to make those work in C land either. I think modules would make Helix much more useful than it currently is.