Skip to content
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

[QUESTION] Why Clojurescript and not JVM? #66

Closed
NightMachinery opened this issue Mar 28, 2018 · 14 comments
Closed

[QUESTION] Why Clojurescript and not JVM? #66

NightMachinery opened this issue Mar 28, 2018 · 14 comments

Comments

@NightMachinery
Copy link

Why Clojurescript and not JVM?

@dundalek
Copy link
Owner

I come from js and node background so it is easier for me to hack on. Plus lumo is awesome and it does a lot of heavy-lifting. Basically when I saw lumo I got the idea I could just hack the REPL a bit and got the prototype working.

I think with the new clj tool and clj.main Clojure proper gets more hackable too. It would be a cool exercise to abstract the code and implement platform specific code for JVM support. I would like to have that eventually down the road.

@NightMachinery
Copy link
Author

NightMachinery commented Mar 29, 2018 via email

@neominik
Copy link

neominik commented Sep 2, 2018

JVM is faster, but has a lot slower startup time. Waiting 10 seconds for your shell to start up every time would be a no-go for me.
Otherwise I would also like to see a JVM version.

@dundalek
Copy link
Owner

dundalek commented Sep 2, 2018

I am hoping that in the future it could be compiled to native code with Graal which should make the startup time be less than a second.

Anyway, the JVM port is in progress in the master branch. It is mostly done, there are just a few issues that need to be ironed out before a release.

@zcaudate
Copy link

zcaudate commented Sep 7, 2018

this is exciting. when will this be out?

@dundalek
Copy link
Owner

dundalek commented Sep 8, 2018

I don't want to give any promises, but it will hopefully be done in a month or so.

@dundalek
Copy link
Owner

dundalek commented Sep 27, 2018

Just FYI here are remaining issues that need to be completed for the JVM integration so that it can be released for v0.3:

  • Fix remaining failing unit tests regarding file redirection
  • Fix cding to non-existing directory which ends in infinite loop
  • Handle SIGINT properly
    • For example when a process runs (like sleep 10) and ctrl+c is pressed then shell quits.
    • Make sure it also interrupts properly when running in process thread, e.g. (Thread/sleep 10000) and pressing crtl+c
  • Bonus: Port the autojump integration
  • Fix glob expansion when switching directories

@zcaudate
Copy link

would it also be possible to have nrepl support?

@dundalek
Copy link
Owner

@zcaudate What would be the use case for having nrepl?

@zcaudate
Copy link

@dundalek: I'd be looking at it as a replacement for lein

@zcaudate
Copy link

it'd be essentially like having both the shell and the repl in one.

@dundalek
Copy link
Owner

@zcaudate I see, it should be possible to include nrepl middleware to start an nrepl server. Could you create a separate issue so we can track it there?

@jeroenvandijk
Copy link
Contributor

I think this can be closed as there is a JVM version now..? 🎉 #87

I'm already playing with it => #92

@dundalek
Copy link
Owner

dundalek commented Oct 9, 2018

I agree. Unfortunately more blocking issues were discovered. There are separate issues opened, I label them with bug and jvm tags.

@dundalek dundalek closed this as completed Oct 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants