41–50 of 138 posts
Nice, I've been waiting for a good modern shell to replace ZSH. Fish just wasn't enough of an improvement for me to abandon ZSH. This is an area where most open-source developers have avoided, as it's a "solved" problem, but it really isn't. I'm currently waiting on Elvish [1] to mature. It's written in Go [2], but they're developing a new language on top of it for shell scripting, which I tried for a week. It's a ni…
Nice, I've been waiting for a good modern shell to replace ZSH. Fish just wasn't enough of an improvement for me to abandon ZSH. This is an area where most open-source developers have avoided, as it's a "solved" problem, but it really isn't. I'm currently waiting on Elvish [1] to mature. It's written in Go [2], but they're developing a new language on top of it for shell scripting, which I tried for a week. It's a ni…
Rash? Rust Already SHell (There's already a "RuSH" made with Ruby). Oh. https://github.com/redox-os/ion CLASH - Common Lisp Again SHell? Oh. http://www.cliki.net/CLISP-Shell Doh! https://docs.racket-lang.org/rash/index.html Someone put OO in my Linux shell! https://virtualizationreview.com/articles/2017/06/01/how-to-...
Earlier quoted context omitted.
startup time: not sure it's good ux to wait seconds for every command... lumo/cljs is instantaneous
500-600ms is, to be fair, a big one time cost. The downsides are pretty darn significant though. I can’t imagine a situation where I would trade ‘starts a bit faster’ for ‘throw away all parallelism in code’ personally... but hey. Plenty of people use node for very serious stuff. I suppose I just think this is an example of fast and cheap on the fast/cheap/good scale.
Earlier quoted context omitted.
What does your development environment look like? Every time I bail on a Cljs project it's because tooling is worse than for Clj.
I use Spacemacs and have the following in inside my .spacemacs in the dotspacemacs/user-config functions: (require 'cider) (setq cider-cljs-lein-repl "(do (require 'figwheel-sidecar.repl-api) (figwheel-sidecar.repl-api/start-figwheel!) (figwheel-sidecar.repl-api/cljs-repl))") Then I just use figwheel to manage my cljs projects (I think this is the default now for reagent and luminus projects, it's also the default fo…
> npm install -g lumo-cljs closh why? seriously, is this the point that modern tooling has gotten to where for no apparent reason it has a node dependency?
i mean, really what is the point of Node ?
> Why try to reinvent bash? > ... > It treats everything as text while we mostly need to manipulate structured information. Looking at the examples given, it's more like Powershell, but with better compatibility with existing Unix text-based tools. Which is awesome.
It seems like the concepts are orthogonal though. The reason powershell works is that it replaced the entire shell toolchain with object-oriented equivalents. Without that you're fundamentally limited because your inputs are still plain text, so you're still doing the equivalent of awk/sed scripts to transform text into structured data.
Nice, I've been waiting for a good modern shell to replace ZSH. Fish just wasn't enough of an improvement for me to abandon ZSH. This is an area where most open-source developers have avoided, as it's a "solved" problem, but it really isn't. I'm currently waiting on Elvish [1] to mature. It's written in Go [2], but they're developing a new language on top of it for shell scripting, which I tried for a week. It's a ni…
[0]: https://github.com/rakitzis/rc
Secondly, I use rc in emacs shell-mode which poorly emulates a terminal, so advanced completion and all that other stuff I delegate to emacs. rc is just a programming language that supports shell commands extremely well.
> Why try to reinvent bash? > ... > It treats everything as text while we mostly need to manipulate structured information. Looking at the examples given, it's more like Powershell, but with better compatibility with existing Unix text-based tools. Which is awesome.
It seems like the concepts are orthogonal though. The reason powershell works is that it replaced the entire shell toolchain with object-oriented equivalents. Without that you're fundamentally limited because your inputs are still plain text, so you're still doing the equivalent of awk/sed scripts to transform text into structured data.
This needs freakin' Node.js.
I'm more looking in the Rust/Haskell/OCaml direction for a hip bash/zsh replacement.