Linux

48024 readers

981 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

225

Fish rewrite-it-in Rust progress: 100% (aus.social)

submitted 9 months ago by Chewy7324@discuss.tchncs.de to c/linux@lemmy.ml

21 comments fedilink hide all child comments

plan for the now completed port of fish to rust

you are viewing a single comment's thread
view the rest of the comments

[–] Urist@lemmy.ml 31 points 9 months ago* (last edited 9 months ago) (3 children)

Seems one of the main reasons is to use Rust's thread safety to enable "concurrent mode". Anyone with the knowledge able to explain what advantages that would yield for an end fish user?

[–] technom@programming.dev 30 points 9 months ago

Here's one issue they hope to solve with this rewrite: https://github.com/fish-shell/fish-shell/issues/238

[–] faho@lemmy.world 4 points 9 months ago

One big, long-standing issue is that fish can't run builtins, blocks or functions in the background or at the same time.

That means a pipeline like

seq 1 5 | while read -l line
    echo line; sleep 0.1; 
end | while read -l line
    echo line; sleep 0.1
end

will have to wait for the first while loop to complete, which takes 0.5s, and then run the second.

So it takes 0.5s until you get the first output and a full second until you get all of it.

Making this concurrent means you get the first line immediately and all of it in 0.5s.

While this is an egregious example, it makes all builtin | builtin pipelines slower.

Other shells solve this via subshells - they fork off a process for the middle part of the pipeline at least. That has some downsides in that it's annoyingly leaky - you can't set variables or create a background job in those sections and then wait for them outside, because it's a new process and so the outer shell never sees them.

[+] bizdelnick@lemmy.ml -9 points 9 months ago (3 children)

End user shouldn't care what PL the software is written in. Their advantages and disadvantages are meaningful for developers only.

[–] Falcon@lemmy.world 17 points 9 months ago

PL can have a large impact on features, bugs, bug reports, troubleshooting, performance and documentation. Particularly when dev resources are limited.

It’s hard to see how this opinion holds any water.

Rust is a great choice for a shell built as an interactive shell that doesn’t have to be core to the OS. Over C++ this also makes development more accessible to young programmers.

[–] conciselyverbose@kbin.social 13 points 9 months ago

Except they affect the end result.

[–] Nyanix@lemmy.ca 4 points 9 months ago

While I agree, most people shouldn't have to be concerned with it, you can't deny the resource impacts of various languages, libraries and frameworks, like compare the memory usage of Discord or Teams with those of FOSS chat applications, and you'll notice those two consistently eating much more memory. You can also compare compute speeds of a higher level language like Python vs lower level languages like Rust and you'll find that Rust is quite a bit faster (though generally takes more dev time). So yes, users shouldn't have to be concerned with involved languages, but if you're running something on a low-resource device, such as a Raspberry Pi, those little details can make all the difference.