From: Kenneth Goodwin <kennethgoodwin56@gmail.com>
To: Bakul Shah <bakul@iitbombay.org>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Zombified SCO comes back from the dead, brings trial back to life against IBM
Date: Sun, 4 Apr 2021 22:58:57 -0400 [thread overview]
Message-ID: <CAMQbRb2QVxaEVhYWkSzhxA-f95ZMSWsqBVUXDiKbuWYbxwQNDA@mail.gmail.com> (raw)
In-Reply-To: <9BF72B30-C353-4F61-8DF0-738F8E9536EE@iitbombay.org>
[-- Attachment #1: Type: text/plain, Size: 5238 bytes --]
On storage discipline-
UNIX derived systems deliberately don't enforce file formats. In the UNIX
philosophy
Everything is a file.
Inter program portability can be achieved in a multitude of ways.
Pure ascii format with either defined field widths or the more common
"special character" delimited fields. Ie pipe delimited or comma or :
delimited.
xml formatted.
There are several conversion programs available as well as write your own.
On Sun, Apr 4, 2021, 9:36 PM Bakul Shah <bakul@iitbombay.org> wrote:
> On Apr 4, 2021, at 4:33 PM, Clem Cole <clemc@ccc.com> wrote:
>
>
>
> On Sun, Apr 4, 2021 at 7:01 PM Bakul Shah <bakul@iitbombay.org> wrote:
>
>>
>>
>> On Apr 4, 2021, at 3:25 PM, David Arnold <davida@pobox.com> wrote:
>>
>> For us UNIX historians, we need to be careful and learn from our own
>> history here -- the Cell Phone/Mobile target is the engine for the next
>> Christenian style disruption. It is by far the #1 target for people
>> writing new programs (which I find a little sad personally - but I
>> understand and accept -- time has marched on). In the end, a small mobile
>> target will be the tech on top, and available will be driven by market
>> behavior and those suppliers will be "who has the gold.”
>>
>>
>> I feel I should point out that both the dominant mobile operating systems
>> are Unix-hased. The UI is necessarily new, but astonishingly the 50 year
>> old basic abstractions are the same.
>>
>>
>> Except Unix is kind of hard to see. It wasn't just the hierarchical file
>> system but the idea of composability. Even now we whip up a shell
>> "one-liners" to perform some task we just thought of. All that is lost. And
>> not just on mobile devices. For example search through email messages for
>> something in an email "app". And no UI composability. We have to use
>> extremely heavyweight IDEs such as X-Code weighing at 15GB (even "du -s
>> /Application/X-code" takes tens of seconds!) to painstakingly construct a
>> UI. We can't just whip up a dashboard to measure & display some realtime
>> changing process/entity. There may be equally heavyweight third party tools
>> but there has been no Bell Labs like research crew to distill it down to
>> the essence of composable UI and ship it with every copy. The idea that
>> users too can learn to "program" if given the right tools.
>>
>
> Exactly my point. The only difference I suspect is I just don't bother
> with the IDE (Xcode or VS). Frankly, vi/emacs, or as we discussed a few
> days ago, ed is still way more preferable when I'm programming.
>
>
> Many things are easier to convey visually. It would be neat if unix
> paradigms can be extended to visual design as well. And you certainly can't
> do visual design easily in vi/emacs. Just like in Autocad you need both
> interactivity and programmability for creating visual elements.
>
> I mentioned in another email Intel's new development suite - OneAPI.
> Absolutely speaking for myself here, I am a bit at odds with management WRT
> to much of it, as I feel the direction is a bit miss guided. But I do
> understand why Intel is doing it/trying. Everyone in the industry seems
> to be saying "use my Framework, my language, my solution and I will solve
> your problem." "You will sell more copies of the program if you use my
> portal, *etc*." Intel to compete, needs to do the same things. To
> me, it seems a bit like fairy dust - a promise that will work for a set of
> people, and of course, some firms like my own employer will keep making
> money (or in the words of the Dr. Sueuss Lorax character: "Biggering and
> Biggering." As I said in the previous message, it is driven by the other
> golden rule.
>
>
> IMHO a bigger need is some discipline on storage. As things stand, it is
> hard to extract data from applications for legitimate uses but not so hard
> to extract for illegitimate uses. If app A for some specific domain dies,
> there is no guarantee that app B for the same domain can use A's data.
>
> What I always felt made UNIX powerful was that it did not seem like the
> BTL folks were trying to sell anything. They were trying to solve real
> problems they and the folks at AT&T had when it came to realistically
> building and deploying systems. Yes, there were hidden from the profit
> motive at the time because of the unique rules of the 1956 consent degree
> and we all were winners because of it because they say -- sure here you can
> use it too.
>
>
> Similar conditions existed and exist to a certain extent in research orgs
> of some companies but I think that is a necessary condition, not
> sufficient. The right research crew can bring in another kind of
> interactivity -- in creativity, in trying out and critiquing each others'
> ideas and building on them. And you still need the right key people.
>
> Now that we are back to a winner take all market, (OSVM/360 *vs.* VMS
> *vs.* winders ...) I think we have traded away designing for the sake of
> getting the job done properly, for designing to sell as many as possible (
> *i.e.* be sexy and capture a market, not be simple and do the job well).
>
>
>
[-- Attachment #2: Type: text/html, Size: 8460 bytes --]
next prev parent reply other threads:[~2021-04-05 3:00 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 14:50 Josh Good
2021-04-01 15:12 ` Warner Losh
2021-04-01 15:27 ` Josh Good
2021-04-01 15:33 ` Larry McVoy
2021-04-01 16:14 ` Kevin Bowling
2021-04-01 16:26 ` John Cowan
2021-04-01 17:54 ` Thomas Paulsen
2021-04-01 16:27 ` Nemo Nusquam
2021-04-02 2:16 ` Kevin Bowling
2021-04-02 3:52 ` Wesley Parish
2021-04-02 5:26 ` Kevin Bowling
2021-04-02 16:03 ` Clem Cole
2021-04-02 16:11 ` Larry McVoy
2021-04-02 16:39 ` Heinz Lycklama
2021-04-02 17:14 ` Clem Cole
2021-04-02 17:17 ` [TUHS] AIX repeat [was " Charles H Sauer
2021-04-03 1:24 ` [TUHS] " Wesley Parish
2021-04-04 2:46 ` Adam Thornton
2021-04-04 2:50 ` Adam Thornton
2021-04-04 5:29 ` [TUHS] How to Kill a Technical Conference (was: Zombified SCO comes back from the dead, brings trial back to life against IBM) G. Branden Robinson
2021-04-04 18:22 ` Clem Cole
2021-04-04 20:54 ` Richard Salz
2021-04-04 21:11 ` Clem Cole
2021-04-05 0:36 ` John Cowan
2021-04-05 2:19 ` Warner Losh
2021-04-05 18:07 ` [TUHS] How to Kill a Technical Conference John Gilmore
2021-04-05 19:30 ` Clem Cole
2021-04-05 20:34 ` Richard Salz
2021-04-05 20:42 ` William Cheswick
2021-04-06 4:37 ` Ed Bradford
2021-04-05 20:39 ` Larry McVoy
2021-04-05 21:11 ` Theodore Ts'o
2021-04-05 21:17 ` Dan Cross
2021-04-06 15:39 ` Theodore Ts'o
2021-04-06 5:49 ` Dave Horsfall
2021-04-05 7:48 ` [TUHS] Whither Usenix [was How To Kill A Technical Conference] arnold
2021-04-05 14:05 ` [TUHS] How to Kill a Technical Conference (was: Zombified SCO comes back from the dead, brings trial back to life against IBM) Theodore Ts'o
2021-04-05 22:26 ` David Arnold
2021-04-04 23:30 ` A. P. Garcia
2021-04-04 3:41 ` [TUHS] Zombified SCO comes back from the dead, brings trial back to life against IBM Gregg Levine
2021-04-04 3:57 ` Adam Thornton
2021-04-02 5:41 ` David Arnold
2021-04-02 6:09 ` Steve Nickolas
2021-04-02 7:00 ` arnold
2021-04-02 9:53 ` Steve Nickolas
2021-04-02 10:26 ` arnold
2021-04-02 14:02 ` Josh Good
2021-04-02 14:17 ` Steve Nickolas
2021-04-02 15:16 ` Larry McVoy
2021-04-02 15:28 ` Fabio Scotoni
2021-04-03 1:50 ` Dave Horsfall
2021-04-03 1:55 ` Warner Losh
2021-04-03 2:23 ` Larry McVoy
2021-04-03 2:34 ` Earl Baugh
2021-04-03 6:16 ` Dan Stromberg
2021-04-04 16:18 ` Tony Finch
2021-04-04 1:48 ` David Arnold
2021-04-04 2:23 ` Larry McVoy
2021-04-04 8:55 ` Josh Good
2021-04-04 14:43 ` Michael Parson
2021-04-04 15:36 ` Warner Losh
2021-04-04 16:15 ` Clem Cole
2021-04-04 22:25 ` David Arnold
2021-04-04 22:55 ` Clem Cole
2021-04-05 2:30 ` Dave Horsfall
2021-04-04 23:00 ` Bakul Shah
2021-04-04 23:33 ` Clem Cole
2021-04-05 1:34 ` Bakul Shah
2021-04-05 2:58 ` Kenneth Goodwin [this message]
2021-04-05 12:35 ` John Cowan
2021-04-05 20:44 ` Kevin Bowling
2021-04-04 23:34 ` Josh Good
2021-04-04 20:08 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-04-04 21:00 ` Jon Steinhart
2021-04-04 21:40 ` Clem Cole
2021-04-04 21:54 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-04-04 22:02 ` Jon Steinhart
2021-04-04 21:58 ` Clem Cole
2021-04-04 23:48 ` Dave Horsfall
2021-04-04 23:53 ` Larry McVoy
2021-04-07 5:15 ` Dan Stromberg
2021-04-05 13:37 ` Theodore Ts'o
2021-04-07 1:52 ` Adam Thornton
2021-04-02 15:25 ` Josh Good
2021-04-03 3:10 ` John Cowan
2021-04-02 16:40 ` Boyd Lynn Gerber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMQbRb2QVxaEVhYWkSzhxA-f95ZMSWsqBVUXDiKbuWYbxwQNDA@mail.gmail.com \
--to=kennethgoodwin56@gmail.com \
--cc=bakul@iitbombay.org \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).