dragora-members
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Dragora-members] Dragora package management


From: Michael Siegel
Subject: Re: [Dragora-members] Dragora package management
Date: Wed, 13 May 2020 18:38:33 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:68.0) Gecko/20100101 Thunderbird/68.8.0

Am 13.05.20 um 03:41 schrieb Kevin "The Nuclear" Bloom:
> 
> It seems to me that using the more "primitive" approach is far simpler
> than the Nix/Guix method. Keep in mind that "simple" is NOT the same as
> "ease-of-use." I would agree that Graft may be "complex" but it's
> solving a rather complicated problem. My question back would be: Is
> Graft's "complexity" the result of simplicity or poor design choice? For
> example, if someone chooses to use wpa_supplicant for wifi connection
> instead of wicd. WPA is far more "complicated" due to the fact you have
> to do everything yourself whereas wicd is far "less complicated" due to
> the UI provided and automated items. WPA is most likely simpler, whereas
> wicd is easier to use yet more complex code-wise.
> 
> On the other hand, Emacs vs Moe. Emacs has become very very complex -
> this is not only because of endless power within the editor but also
> poor design choice. Emac's complexity has to do with people continually
> adding and adding and adding stuff to it. The poor design choice is that
> people keep adding stuff to mainline Emacs. Make it modular and it
> wouldn't be as big of a concern.  Moe, which keep in mind is VERY
> different than Emacs, lacks this flaw. It's designer said "I want Moe to
> edit text." That's it. The design is straightforward and
> simple. Simplistic and good design.
> 
> Not sure if any of this makes sense.

I think it does.

> Going by lines of code isn't always synonymous with complexity, poor
> programming, or bloat. Depending on the language, problem, and project
> goals any program can have any number of lines. If I wanted Qire to just
> fetch packages, it would be like 200 LOC but if I want it to fetch,
> install, upgrade, list, display info, build index files for repos, and
> do all of this with [possibly] many versions of the same program it's
> definitely going to be more code! As Matias mentioned, code-style is
> important too. If you create unreadable code, you may save on lines of
> code but at what cost?

Agreed.


Best
Michael




reply via email to

[Prev in Thread] Current Thread [Next in Thread]