Live data from Hacker News

Kiss Linux – A distribution with a focus on less is more

k1ss.org

141–145 of 145 posts

Re: Kiss Linux – A distribution with a focus on less is more

#142
post #125
post #75

No Wayland, but Xorg? How is that simple?

There are lots of good, simple window managers (not to mention other utilities) for xorg. Window managers in wayland have a lot more work to do, and are typically more complicated. There are lots of utilities that aren't available in wayland yet, so you'll often end up with an x server installed anyway.

Not using a GUI at all would be much simpler.

Re: Kiss Linux – A distribution with a focus on less is more

#143

I 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. "

FWIW I'm thinking: Step 1, Install Nix (or Guix.)

that sounds reasonable (and a unixy solution - combine good individual tools into a better whole)

Re: Kiss Linux – A distribution with a focus on less is more

#144
post #106

> The distribution targets only the x86-64 architecture and the English language. Deal breaker for me. But the author should be commended for stating it up front. Far to often, only the benefits are presented but none of the flaws so you have to investigate new tech deeply to find out if it is right for you.

Seriously? There's a link "Ports (non-x86-64)" in the side bar. https://k1ss.org/ports

There is no reason for you to be snarky. I care about only English being officially supported. That is a non starter.

Re: Kiss Linux – A distribution with a focus on less is more

#145
post #123
post #17

Earlier quoted context omitted.

It's an operating system distribution... why bother with how its documentation is served

Because it reflects how the writers solve problems. They needed a website. Did they spin up a docker container of wordpress, install a theme and some plugins until it looked the way they wanted, and write content in an in-browser WYSIWYG editor? Or did they write their content as HTML, and copy it to a server running HTTPD? Those two solutions represent different values, different philosophies, about how to use compu…

No, it primarily reflects the problems. For example, the Gentoo and Arch Linux run MediaWiki. Does this tell you something about their "values or philosophies about how to use computers"? No, a static site generator would simply not be practical for either project. What renders documentation HTML in the background tells nothing about either project's approach to operating system development.
Post reply on HN