Subj : Re: Windows vs Linux
To   : boraxman
From : tenser
Date : Mon Apr 25 2022 01:21:12

On 23 Apr 2022 at 12:55p, boraxman pondered and said...
 
 bo> The difference is that one system, out-of-the-box, is designed around
 bo> this paradigm, and the other was designed around another, but is adding
 bo> a better shell language and SWL later on.

And yet that "one system, out-of-the-box, [that] is
designed around this paradigm" is useless for this
kind of work.  The other that is "adding a better
shell language" (nevermind that PowerShell is 15 years
old) can do it.

Something I had to come to terms with 15 or so years
ago is that the Unix pipeline model _has limitations_.

 bo> I use Windows at work, and the workflows and data management is
 bo> horrendously hobbled by the "desktop consumer computing" paradigm.  It
 bo> may be possible for the IT team to set up our Windows machines
 bo> differently, so that we aren't playing application jockeys, but I really
 bo> doubt it will happen.  They are to stuck in the mindset of finding
 bo> applications which encompass the entire solution.
 bo> 
 bo> The company I'm working for is spending a 6 figure amount for a such a
 bo> web based software package.  I've used similar management systems such
 bo> at that elsewhere, and they save no time, have a short shelf life, and
 bo> are rigid in how they are used.

But a couple of shell scripts and some awk will do better?

I've heard this many times, and implemented it a few times
myself.  The thing that happens time and time again is that
it seems simple at first, but systems grow to accommodate
special cases and you start to realize that those "rigid"
packages actually have real value.

Again, computers are _tools_.  Use them to do real work; for
most people, they are not the end in and of themselves.

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.