Earlier quoted context omitted.
Could you explain more re: bugs? Dylan Araps sort of specialises in well-written (ba)sh and iirc uses shellcheck meticulously. I ask not to be combative in case you're just making a casual joke - more I'd like understand how bugs might creep in to (ba)sh code - even if say, one follows shellcheck and is as competent as Dylan.
I saw that after posting. It's not a critic of Dylan's work, more a critic of how difficult it is to write good bash code. Your comment on shellcheck and Dylan expertise just confirm it. It's like C, you could write safe C but it's very difficult. I wish there was a language with the ubiquity of Bash but modern and safe.
Kiss Linux – A distribution with a focus on less is more
41–50 of 145 posts
Re: Kiss Linux – A distribution with a focus on less is more
#42I loved the idea (git everything!) until I read this: "How do I remove a package and all of its dependencies? [...] The package manager does not do recursive dependency removal on removal of a package. This error-prone automation will not be added to the package manager. "
Well, then again, many other package managers don't either. For instance XBPS and Pacman. EDIT: I'm wrong, see below.
> To remove a package and its dependencies which are not required by any other installed package:
> # pacman -Rs package_name
> To remove a package, its dependencies and all the packages that depend on the target package:
> # pacman -Rsc package_name
Re: Kiss Linux – A distribution with a focus on less is more
#43 * Based on musl libc, busybox and the Linux kernel.
As some one who is working on Go ecosystem, this drops my interesting immediately. Using musl libs means a lot of tools can't be used on this OS unless we install the glibc.Re: Kiss Linux – A distribution with a focus on less is more
#44I loved the idea (git everything!) until I read this: "How do I remove a package and all of its dependencies? [...] The package manager does not do recursive dependency removal on removal of a package. This error-prone automation will not be added to the package manager. "
This might seem like a limitation. But you can provide a base system with a toolchain & xorg with known dependencies and a limited set of packages (like a BSD base system). Then for every big and complex app clone that base system and build the app in a chroot/sandbox or container. That way you get the app and dont pollute the base system and uninstalling is just rm -rf On every distro uninstalling packages never rea…
Not at all. Apt has been able to remove everything for the last 20 years.
Re: Kiss Linux – A distribution with a focus on less is more
#45> Uses a package manager written in less than 1000 lines of POSIX sh (excluding blank lines and comments). Enough to get 20 bugs :-). I wish there was a good standard alternative to bash (sh in this case) for shell programming. Otherwise I like the spirit, it's a good match with collapse os ;-)
On Windows: ren ∗.js ∗.mjs
On Unix: for x in ∗.js; do mv "$x" "${x%.js}.mjs"; done
Feels like shells should have one line list comprehensions without the obtruse do/done. Are there any shell enhancements like zsh or the like, that make simple list operations less verbose?
Re: Kiss Linux – A distribution with a focus on less is more
#46* Based on musl libc, busybox and the Linux kernel. As some one who is working on Go ecosystem, this drops my interesting immediately. Using musl libs means a lot of tools can't be used on this OS unless we install the glibc.
Re: Kiss Linux – A distribution with a focus on less is more
#47Earlier quoted context omitted.
This might seem like a limitation. But you can provide a base system with a toolchain & xorg with known dependencies and a limited set of packages (like a BSD base system). Then for every big and complex app clone that base system and build the app in a chroot/sandbox or container. That way you get the app and dont pollute the base system and uninstalling is just rm -rf On every distro uninstalling packages never rea…
Isn't this basically what Docker is for?
Re: Kiss Linux – A distribution with a focus on less is more
#48> Uses a package manager written in less than 1000 lines of POSIX sh (excluding blank lines and comments). Enough to get 20 bugs :-). I wish there was a good standard alternative to bash (sh in this case) for shell programming. Otherwise I like the spirit, it's a good match with collapse os ;-)
One thing that irks me is the verbosity of simply renaming file extensions of all files in a directory. On Windows: ren ∗.js ∗.mjs On Unix: for x in ∗.js; do mv "$x" "${x%.js}.mjs"; done Feels like shells should have one line list comprehensions without the obtruse do/done. Are there any shell enhancements like zsh or the like, that make simple list operations less verbose?
Re: Kiss Linux – A distribution with a focus on less is more
#49Earlier quoted context omitted.
This might seem like a limitation. But you can provide a base system with a toolchain & xorg with known dependencies and a limited set of packages (like a BSD base system). Then for every big and complex app clone that base system and build the app in a chroot/sandbox or container. That way you get the app and dont pollute the base system and uninstalling is just rm -rf On every distro uninstalling packages never rea…
Isn't this basically what Docker is for?
Re: Kiss Linux – A distribution with a focus on less is more
#50Earlier quoted context omitted.
Could you explain more re: bugs? Dylan Araps sort of specialises in well-written (ba)sh and iirc uses shellcheck meticulously. I ask not to be combative in case you're just making a casual joke - more I'd like understand how bugs might creep in to (ba)sh code - even if say, one follows shellcheck and is as competent as Dylan.
I saw that after posting. It's not a critic of Dylan's work, more a critic of how difficult it is to write good bash code. Your comment on shellcheck and Dylan expertise just confirm it. It's like C, you could write safe C but it's very difficult. I wish there was a language with the ubiquity of Bash but modern and safe.
I agree. But reaching such a point would be hard. Not impossible, but hard.
I think the main problem would be to gain traction for an alternative. Because if one questions the status quo, then there are tons of alternative paths to go by. But which of them are viable…? It’s not easy to pick a winner in this kind of situtation. And most people, even in tech, would not want to spend hours on trying out/developing a new shell that won’t gain any significant traction.
The Bourne shell was developed in the mid 70s. There were not many other scripting languages around then, so Bourne shell became a major player. They could probably have used Lisp if they wanted to, but AFAIK Lisp was not widespread within the Unix world back then.
These days we have many other models for interpreted languages. Ruby, Python, Perl, TCL, Scheme, Clojure, etc etc.
Let’s say someone wrote a Python-inspired shell that aimed to replace sh/Bash. Now you need to gain traction in order to build up a useful and sound ecosystem that has the ability to replace all those shell scripts out there. But how would you convince the Ruby fans or Scheme fans to use that? Therein lies a big challenge.
Getting people to continue using sh is not as hard, since it at least is standard, despite its shortcomings.
[Slightly edited.]