coursier VS fish-shell

This is an upstream page size issue, equivalent issue here: https://github.com/coursier/coursier/issues/2636

I feel like this is already is the case, one can use coursier https://get-coursier.io/ or scala-cli to get started with Scala extremely fast.

I had a nice workflow installing different Java versions using SDKMAN but switched to Coursier because that't what's recommended in the Almond installation guide. In order to run `jupter lab` and start up the notebook environment, I need to separately install Jupyter Lab via conda (and activate that conda environment).

Could a Java project use a similar scheme? Probably, but the practicality of that is dependent on programatic resolution tools like coursier which don't exist in a convenient form for Java programmers quite yet.

Shell for issuing SQL to relational databases via JDBCIf you have Coursier installed, you can quickly connect to a demo Hypersonic database with:

This seems the same thing: - https://github.com/oracle/graal/issues/4479 - https://github.com/coursier/coursier/issues/2395

I use coursier to install scala. https://get-coursier.io/

If you truly must avoid it, then take a look at coursier and ammonite: https://get-coursier.io/ and cs launch com.lihaoyi:ammonite_2.13.1:2.0.4 -M ammonite.Main

I'm digging a bit deeper on this Google Artifact Repository task and it looks like it won't. See https://github.com/coursier/coursier/issues/1987 for more details.

Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.

https://github.com/fish-shell/fish-shell/releases/tag/3.7.1

https://github.com/fish-shell/fish-shell/issues/7772#issueco...

https://gitlab.archlinux.org/archlinux/packaging/packages/fi...

A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123

An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust

It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/

And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123

We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.

They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.

[1] https://github.com/fish-shell/fish-shell/pull/9512