Re: SSD TBW

[email protected] (Scott Dorsey)
Newsgroups comp.misc,sci.electronics.design
Organization Former users of Netcom shell (1989-2000)
Message-ID <[email protected]>
Don Y  <[email protected]> wrote:
>On 8/23/2026 11:09 AM, Scott Dorsey wrote:
>>> Note that vipw(8) adds value -- it ensures all of the passwd-associated
>>> files remain in a consistent format.  BECAUSE IT IS AWARE OF THAT FORMAT,
>>> even though the files still identify as "text" (no magic numbers, etc.)
>> 
>> Yes, and emacs has context-sensitive modes for C and for English.  If you
>> like format-specific editors you can use them.  Personally they drive me
>> up the wall and I don't like them, but it's your call as a user.
>
>Different issue.  That's (almost) entirely one of presentation.
>If emacs was continuously checking your code for BUGS, automatically
>checking out the file from whichever VCS tracks it, etc. that would be
>more comparable.

The same is the case for vipw.  It is a language-sensitive editor which 
does some rudimentary syntax checking.  I don't like these things.  Some
people do.

>> This is very much contrary to the Unix philosophy.
>
>cf. systemd?  rc.d?  inetd.conf?  Have you seen how init has evolved
>over the years in different "flavors" of UNIX?

Yes, and many systems are diverging very far from the traditional Unix
philosophy.  That doesn't mean the traditional Unix philosophy is a bad
one.

>I.e., people seem to be highly selective in what they consider
>The UNIX Way.

Oh, I don't think anyone has ever claimed systemd was the UNIX way.  They
might claim a lot of benefits for them, but it is very divergent from 
the philosophy in Thompson and Richie.

>> If you like it, that
>> is fine but it's not Unixlike.  But I am not sure why you are taking this
>> thread so far afield.
>
>It is all related to facilitating your maintenance of <whatever> -- sources,
>text (flat) "databases", configuration files, bitmapped fonts, etc.  Tools
>should make those activities simpler, quicker and more robust.  E.g., if your
>VCS tells me two (source) files differ (but the binaries end up identical)
>then it has not helped me; the differences are not related to whatever issue
>has prompted me to look at them.  ("move along; nothing here")

Here is the thing about Unix.  It's a box of tools.  If you don't like this
tool, use another one.  If you can't find something you like, write one...
but you likely won't have to because tools are designed to be modular to
allow you to change them.

If you like using a giant database instead, you can do that.  But I won't,
and I explained why.  And that's what's nice about Unix, you can set your
environment up however you want.
--scott
-- 
"C'est un Nagra. C'est suisse, et tres, tres precis."
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.