Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.folklore.computers > #212313 > unrolled thread
| Started by | Iron Spring Software <Peter_Flass@Yahoo.com> |
|---|---|
| First post | 2020-07-24 09:38 -0700 |
| Last post | 2020-07-30 20:27 +0000 |
| Articles | 20 on this page of 164 — 35 participants |
Back to article view | Back to alt.folklore.computers
DEC Iron Spring Software <Peter_Flass@Yahoo.com> - 2020-07-24 09:38 -0700
Re: DEC Mike Spencer <mds@bogus.nodomain.nowhere> - 2020-07-24 17:12 -0300
Re: DEC J. Clarke <jclarke.873638@gmail.com> - 2020-07-24 17:14 -0400
Re: DEC Peter Flass <peter_flass@yahoo.com> - 2020-07-24 19:43 -0700
Re: DEC J. Clarke <jclarke.873638@gmail.com> - 2020-07-24 23:28 -0400
Re: DEC Quadibloc <jsavard@ecn.ab.ca> - 2020-07-25 02:06 -0700
Re: DEC J. Clarke <jclarke.873638@gmail.com> - 2020-07-25 05:27 -0400
Re: DEC Ahem A Rivet's Shot <steveo@eircom.net> - 2020-07-25 10:58 +0100
Re: 360 PCs was DEC John Levine <johnl@taugh.com> - 2020-07-25 17:21 +0000
Re: 360 PCs was DEC J. Clarke <jclarke.873638@gmail.com> - 2020-07-25 13:54 -0400
Re: 360 PCs was DEC Peter Flass <peter_flass@yahoo.com> - 2020-07-25 14:43 -0700
Re: 360 PCs was DEC J. Clarke <jclarke.873638@gmail.com> - 2020-07-25 18:05 -0400
Re: 360 PCs was DEC Dan Espen <dan1espen@gmail.com> - 2020-07-25 20:27 -0400
Re: 360 PCs was DEC J. Clarke <jclarke.873638@gmail.com> - 2020-07-25 21:08 -0400
Re: 360 PCs was DEC Dan Espen <dan1espen@gmail.com> - 2020-07-25 23:29 -0400
Re: 360 PCs was DEC Dan Espen <dan1espen@gmail.com> - 2020-07-25 23:30 -0400
Re: 360 PCs was DEC J. Clarke <jclarke.873638@gmail.com> - 2020-07-26 00:06 -0400
Re: 360 PCs was DEC Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-08-05 06:06 +0000
Re: 360 PCs was DEC J. Clarke <jclarke.873638@gmail.com> - 2020-08-07 10:19 -0400
Re: 360 PCs was DEC Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-08-07 20:01 +0000
Re: wiki software, not 360 PCs was DEC John Levine <johnl@taugh.com> - 2020-08-07 22:45 +0000
Re: wiki software, not 360 PCs was DEC J. Clarke <jclarke.873638@gmail.com> - 2020-08-08 13:35 -0400
Re: wiki software, not 360 PCs was DEC Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-08-09 15:33 +0000
Re: wiki software, not 360 PCs was DEC J. Clarke <jclarke.873638@gmail.com> - 2020-08-09 13:16 -0400
Re: wiki software, not 360 PCs was DEC Dan Espen <dan1espen@gmail.com> - 2020-08-09 15:00 -0400
Re: wiki software, not 360 PCs was DEC J. Clarke <jclarke.873638@gmail.com> - 2020-08-09 18:35 -0400
Re: wiki software, not 360 PCs was DEC maus <maus@dmaus.org> - 2020-08-10 23:10 +0000
Re: wiki software, not 360 PCs was DEC Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-08-09 19:18 +0000
Re: wiki software, not 360 PCs was DEC J. Clarke <jclarke.873638@gmail.com> - 2020-08-09 18:40 -0400
Re: wiki software, not 360 PCs was DEC Peter Flass <peter_flass@yahoo.com> - 2020-08-09 15:30 -0700
Re: 360 PCs was DEC Peter Flass <peter_flass@yahoo.com> - 2020-07-25 18:39 -0700
Re: 360 PCs was DEC Peter Flass <peter_flass@yahoo.com> - 2020-07-25 18:43 -0700
Re: 360 PCs was DEC Dan Espen <dan1espen@gmail.com> - 2020-07-25 23:32 -0400
Re: 360 PCs was DEC John Levine <johnl@taugh.com> - 2020-07-26 21:45 +0000
Re: 360 PCs was DEC J. Clarke <jclarke.873638@gmail.com> - 2020-07-26 18:01 -0400
Re: 360 PCs was DEC Ahem A Rivet's Shot <steveo@eircom.net> - 2020-07-27 06:38 +0100
Re: 360 PCs was DEC John Levine <johnl@taugh.com> - 2020-07-26 01:24 +0000
Re: 360 PCs was DEC Peter Flass <peter_flass@yahoo.com> - 2020-07-25 18:39 -0700
Re: 360 PCs was DEC Bob Eager <news0073@eager.cx> - 2020-07-26 20:18 +0000
Re: 360 PCs was DEC Ahem A Rivet's Shot <steveo@eircom.net> - 2020-07-25 19:39 +0100
Re: DEC Quadibloc <jsavard@ecn.ab.ca> - 2020-07-25 12:50 -0700
Re: DEC Quadibloc <jsavard@ecn.ab.ca> - 2020-07-25 02:26 -0700
Re: DEC usenet@only.tnx (Questor) - 2020-07-26 19:23 +0000
Re: DEC Thomas Koenig <tkoenig@netcologne.de> - 2020-07-26 21:05 +0000
Re: DEC Peter Flass <peter_flass@yahoo.com> - 2020-07-26 16:23 -0700
Re: DEC J. Clarke <jclarke.873638@gmail.com> - 2020-07-26 21:24 -0400
Re: DEC Peter Flass <peter_flass@yahoo.com> - 2020-07-27 11:42 -0700
Re: DEC archaeology John Levine <johnl@taugh.com> - 2020-07-27 02:41 +0000
Re: DEC archaeology Andy Burns <usenet@andyburns.uk> - 2020-07-27 07:37 +0100
Re: DEC archaeology Thomas Koenig <tkoenig@netcologne.de> - 2020-07-27 07:10 +0000
Re: DEC archaeology Ahem A Rivet's Shot <steveo@eircom.net> - 2020-07-27 09:03 +0100
Re: DEC archaeology Michael LeVine <mlevinespmfltr@redshift.com> - 2020-07-27 02:09 -0700
Re: DEC archaeology Ahem A Rivet's Shot <steveo@eircom.net> - 2020-07-27 11:27 +0100
Origin of Niven/Pournelle quips (was: DEC archaeology) Thomas Koenig <tkoenig@netcologne.de> - 2020-07-27 12:22 +0000
Re: Origin of Niven/Pournelle quips (was: DEC archaeology) Rich Alderson <news@alderson.users.panix.com> - 2020-07-27 20:51 -0400
Re: Origin of Niven/Pournelle quips (was: DEC archaeology) Ahem A Rivet's Shot <steveo@eircom.net> - 2020-07-28 06:02 +0100
Re: Origin of Niven/Pournelle quips (was: DEC archaeology) Bob Eager <news0073@eager.cx> - 2020-07-28 08:29 +0000
Re: Origin of Niven/Pournelle quips (was: DEC archaeology) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-07-28 17:30 +0000
Re: Origin of Niven/Pournelle quips (was: DEC archaeology) djheydt@kithrup.com (Dorothy J Heydt) - 2020-07-28 18:18 +0000
Re: Origin of Niven/Pournelle quips (was: DEC archaeology) Bob Eager <news0073@eager.cx> - 2020-07-28 19:57 +0000
Re: Origin of Niven/Pournelle quips (was: DEC archaeology) Ahem A Rivet's Shot <steveo@eircom.net> - 2020-07-28 21:32 +0100
Re: Origin of Niven/Pournelle quips (was: DEC archaeology) djheydt@kithrup.com (Dorothy J Heydt) - 2020-07-28 21:34 +0000
Re: Origin of Niven/Pournelle quips (was: DEC archaeology) J. Clarke <jclarke.873638@gmail.com> - 2020-07-28 18:33 -0400
Re: Origin of Niven/Pournelle quips (was: DEC archaeology) Ahem A Rivet's Shot <steveo@eircom.net> - 2020-07-28 20:55 +0100
Re: DEC archaeology John Levine <johnl@taugh.com> - 2020-07-27 14:53 +0000
Re: DEC archaeology drb@ihatespam.msu.edu (Dennis Boone) - 2020-07-27 11:30 -0500
Re: DEC archaeology scott@slp53.sl.home (Scott Lurndal) - 2020-07-27 16:37 +0000
Re: DEC archaeology drb@ihatespam.msu.edu (Dennis Boone) - 2020-07-28 10:24 -0500
Re: DEC archaeology scott@slp53.sl.home (Scott Lurndal) - 2020-07-28 15:59 +0000
Re: DEC archaeology Peter Flass <peter_flass@yahoo.com> - 2020-07-27 11:42 -0700
Re: DEC archaeology J. Clarke <jclarke.873638@gmail.com> - 2020-07-27 18:47 -0400
Re: DEC archaeology Quadibloc <jsavard@ecn.ab.ca> - 2020-07-27 17:43 -0700
Re: DEC usenet@only.tnx (Questor) - 2020-07-28 03:21 +0000
Re: DEC Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-07-28 17:30 +0000
Re: ou sont les ordinateurs d'antan, was DEC John Levine <johnl@taugh.com> - 2020-07-28 20:27 +0000
Re: ou sont les ordinateurs d'antan, was DEC J. Clarke <jclarke.873638@gmail.com> - 2020-07-28 18:53 -0400
Re: ou sont les ordinateurs d'antan, was DEC Gareth Evans <headstone255@yahoo.com> - 2020-07-29 10:36 +0100
Re: ou sont les ordinateurs d'antan, was DEC Andreas Eder <a_eder_muc@web.de> - 2020-08-02 12:55 +0200
Re: ou sont les ordinateurs d'antan, was DEC J. Clarke <jclarke.873638@gmail.com> - 2020-08-02 12:49 -0400
Re: ou sont les ordinateurs d'antan, was DEC Peter Flass <peter_flass@yahoo.com> - 2020-07-29 14:08 -0700
Re: ou sont les ordinateurs d'antan, was DEC Peter Flass <peter_flass@yahoo.com> - 2020-07-29 14:04 -0700
Re: DEC Louis Krupp <lkrupp@invalid.pssw.com.invalid> - 2020-07-30 03:49 -0600
Re: DEC scott@slp53.sl.home (Scott Lurndal) - 2020-07-30 14:41 +0000
Re: DEC Peter Flass <peter_flass@yahoo.com> - 2020-07-30 10:12 -0700
Re: DEC scott@slp53.sl.home (Scott Lurndal) - 2020-07-30 18:40 +0000
Re: DEC Peter Flass <peter_flass@yahoo.com> - 2020-07-30 12:02 -0700
Re: DEC Terry Kennedy <terry-groups@glaver.org> - 2020-07-31 02:38 -0700
Re: DEC large computers John Levine <johnl@taugh.com> - 2020-07-31 20:21 +0000
Re: DEC large computers Thomas Koenig <tkoenig@netcologne.de> - 2020-07-31 23:23 +0000
Re: DEC large computers J. Clarke <jclarke.873638@gmail.com> - 2020-07-31 21:13 -0400
Re: DEC large computers Thomas Koenig <tkoenig@netcologne.de> - 2020-08-01 10:39 +0000
Re: vectors, was DEC large computers John Levine <johnl@taugh.com> - 2020-08-01 02:21 +0000
Re: vectors, was DEC large computers Bob Eager <news0073@eager.cx> - 2020-08-01 11:14 +0000
Re: IBM models 91, 195 & CDC 7600 robin.vowels@gmail.com - 2020-07-31 20:30 -0700
Re: IBM models 91, 195 & CDC 7600 Dan Espen <dan1espen@gmail.com> - 2020-08-01 00:00 -0400
Re: IBM models 91, 195 & CDC 7600 robin.vowels@gmail.com - 2020-08-01 02:20 -0700
Re: IBM models 91, 195 & CDC 7600 Peter Flass <peter_flass@yahoo.com> - 2020-08-01 07:00 -0700
Re: IBM models 91, 195 & CDC 7600 robin.vowels@gmail.com - 2020-08-01 08:18 -0700
Re: IBM models 91, 195 & CDC 7600 Dan Espen <dan1espen@gmail.com> - 2020-08-01 11:52 -0400
Re: IBM models 91, 195 & CDC 7600 Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-02 21:58 +0000
Re: IBM models 91, 195 & CDC 7600 Dan Espen <dan1espen@gmail.com> - 2020-08-02 18:50 -0400
Re: IBM models 91, 195 & CDC 7600 Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-03 18:23 +0000
Re: IBM models 91, 195 & CDC 7600 Peter Flass <peter_flass@yahoo.com> - 2020-08-03 13:34 -0700
Re: IBM models 91, 195 & CDC 7600 Quadibloc <jsavard@ecn.ab.ca> - 2020-08-01 00:55 -0700
Re: IBM models 91, 195 & CDC 7600 robin.vowels@gmail.com - 2020-08-01 02:27 -0700
Re: IBM models 91, 195 & CDC 7600 John Levine <johnl@taugh.com> - 2020-08-01 17:27 +0000
Re: IBM models 91, 195 & CDC 7600 Peter Flass <peter_flass@yahoo.com> - 2020-08-01 12:11 -0700
Re: IBM models 91, 195 & CDC 7600 Bob Eager <news0073@eager.cx> - 2020-08-01 19:56 +0000
Re: IBM models 91, 195 & CDC 7600 John Levine <johnl@taugh.com> - 2020-08-01 20:18 +0000
Re: IBM models 91, 195 & CDC 7600 Bob Eager <news0073@eager.cx> - 2020-08-01 23:42 +0000
Re: IBM models 91, 195 & CDC 7600 robin.vowels@gmail.com - 2020-08-01 20:32 -0700
Re: IBM models 91, 195 & CDC 7600 Gerard Schildberger <gerard46@rrt.net> - 2020-08-02 12:58 -0700
Re: IBM models 91, 195 & CDC 7600 J. Clarke <jclarke.873638@gmail.com> - 2020-08-01 16:28 -0400
Re: IBM models 91, 195 & CDC 7600 David Lesher <wb8foz@panix.com> - 2020-08-02 20:42 +0000
Re: IBM models 91, 195 & CDC 7600 robin.vowels@gmail.com - 2020-08-01 20:27 -0700
Re: IBM models 91, 195 & CDC 7600 Quadibloc <jsavard@ecn.ab.ca> - 2020-08-02 00:28 -0700
Re: IBM models 91, 195 & CDC 7600 Thomas Koenig <tkoenig@netcologne.de> - 2020-08-02 08:01 +0000
Re: IBM models 91, 195 & CDC 7600 Quadibloc <jsavard@ecn.ab.ca> - 2020-08-03 16:47 -0700
Re: IBM models 91, 195 & CDC 7600 Quadibloc <jsavard@ecn.ab.ca> - 2020-08-03 19:45 -0700
Re: IBM models 91, 195 & CDC 7600 Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2020-08-03 21:00 -0600
Re: IBM models 91, 195 & CDC 7600 scott@slp53.sl.home (Scott Lurndal) - 2020-08-02 22:45 +0000
Re: IBM models 91, 195 & CDC 7600 Peter Flass <peter_flass@yahoo.com> - 2020-08-03 07:45 -0700
Re: IBM models 91, 195 & CDC 7600 "Kerr-Mudd,John" <notsaying@127.0.0.1> - 2020-08-01 08:24 +0000
Re: IBM models 91, 195 & CDC 7600 robin.vowels@gmail.com - 2020-08-01 02:30 -0700
Re: IBM models 91, 195 & CDC 7600 robin.vowels@gmail.com - 2020-08-01 02:34 -0700
Re: DEC large computers Quadibloc <jsavard@ecn.ab.ca> - 2020-08-01 00:51 -0700
Re: DEC large computers robin.vowels@gmail.com - 2020-08-01 02:23 -0700
Jupiter alternatives [was Re: DEC] Rich Alderson <news@alderson.users.panix.com> - 2020-07-31 21:16 -0400
Re: Jupiter alternatives [was Re: DEC] Robert Swindells <rjs@fdy2.co.uk> - 2020-08-01 01:56 +0000
Re: Jupiter alternatives [was Re: DEC] Adam Sampson <ats@offog.org> - 2020-08-01 15:59 +0100
Re: Jupiter alternatives [was Re: DEC] Rich Alderson <news@alderson.users.panix.com> - 2020-08-01 22:09 -0400
Re: Jupiter alternatives [was Re: DEC] Rich Alderson <news@alderson.users.panix.com> - 2020-08-01 22:07 -0400
Re: DEC usenet@only.tnx (Questor) - 2020-08-03 00:32 +0000
Re: DEC Terry Kennedy <terry-groups@glaver.org> - 2020-08-02 23:54 -0700
Re: DEC Peter Flass <peter_flass@yahoo.com> - 2020-08-03 07:45 -0700
Re: DEC robin.vowels@gmail.com - 2020-08-03 09:16 -0700
Re: DEC Quadibloc <jsavard@ecn.ab.ca> - 2020-08-03 10:10 -0700
Re: DEC Peter Flass <peter_flass@yahoo.com> - 2020-08-03 10:35 -0700
Re: DEC Terry Kennedy <terry-groups@glaver.org> - 2020-08-03 11:28 -0700
Re: DEC Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-03 21:26 +0000
Re: DEC Quadibloc <jsavard@ecn.ab.ca> - 2020-08-03 16:38 -0700
Re: DEC Dan Espen <dan1espen@gmail.com> - 2020-08-03 21:44 -0400
Re: DEC Terry Kennedy <terry-groups@glaver.org> - 2020-08-03 23:55 -0700
Re: DEC Dan Espen <dan1espen@gmail.com> - 2020-08-04 08:05 -0400
Re: DEC J. Clarke <jclarke.873638@gmail.com> - 2020-08-04 08:59 -0400
Re: DEC Terry Kennedy <terry-groups@glaver.org> - 2020-08-04 06:29 -0700
Re: DEC Peter Flass <peter_flass@yahoo.com> - 2020-08-04 07:48 -0700
Re: DEC Niklas Karlsson <anksil@yahoo.se> - 2020-08-05 04:13 +0000
Re: DEC robin.vowels@gmail.com - 2020-08-04 22:45 -0700
Re: DEC JimP <chucktheouch@gmail.com> - 2020-08-05 12:33 -0500
Re: DEC "Kerr-Mudd,John" <notsaying@127.0.0.1> - 2020-08-05 19:31 +0000
Re: DEC Terry Kennedy <terry-groups@glaver.org> - 2020-08-04 22:57 -0700
Re: DEC Bob Eager <news0073@eager.cx> - 2020-08-05 08:13 +0000
Re: DEC Peter Flass <peter_flass@yahoo.com> - 2020-08-05 10:58 -0700
Re: DEC drb@ihatespam.msu.edu (Dennis Boone) - 2020-08-05 13:28 -0500
Re: DEC Terry Kennedy <terry-groups@glaver.org> - 2020-08-06 16:21 -0700
Re: DEC Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-03 18:23 +0000
Re: DEC Terry Kennedy <terry-groups@glaver.org> - 2020-08-03 11:31 -0700
Re: DEC danny burstein <dannyb@panix.com> - 2020-08-03 18:38 +0000
Re: DEC "m. thompson" <michael.99.thompson@gmail.com> - 2020-08-04 05:38 -0700
Re: DEC Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-04 18:54 +0000
Re: DEC usenet@only.tnx (Questor) - 2020-08-03 00:32 +0000
Re: DEC Quadibloc <jsavard@ecn.ab.ca> - 2020-07-30 13:29 -0700
Re: DEC usenet@only.tnx (Questor) - 2020-07-30 20:27 +0000
Page 2 of 9 — ← Prev page 1 [2] 3 4 5 6 7 8 9 Next page →
| From | John Levine <johnl@taugh.com> |
|---|---|
| Date | 2020-08-07 22:45 +0000 |
| Subject | Re: wiki software, not 360 PCs was DEC |
| Message-ID | <rgklhl$t4r$2@gal.iecc.com> |
| In reply to | #212570 |
In article <slrnrircp3.kpi.grahn+nntp@frailea.sa.invalid>, Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: >> Mediawiki does look good--I wish I'd known about it three years ago >> when I worked for somebody with enough pull to sell it to >> managment--there's been three reshufflings since and I'm back to being >> a peon. > >I like Mediawiki because it's a wiki. The links, the categories, the >"what links here" and the search box, can be used to keep control over >a growing body of information. (I also like the templates, and the >markup language.) I like it because it's the same software the Wikipedia uses, so if you know how to edit Wikipedia entries, you know how to edit any other Mediawiki site. -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
[toc] | [prev] | [next] | [standalone]
| From | J. Clarke <jclarke.873638@gmail.com> |
|---|---|
| Date | 2020-08-08 13:35 -0400 |
| Subject | Re: wiki software, not 360 PCs was DEC |
| Message-ID | <uhotif55o1541qm6iibtovhhqas8d1mo9o@4ax.com> |
| In reply to | #212573 |
On Fri, 7 Aug 2020 22:45:09 -0000 (UTC), John Levine <johnl@taugh.com> wrote: >In article <slrnrircp3.kpi.grahn+nntp@frailea.sa.invalid>, >Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: >>> Mediawiki does look good--I wish I'd known about it three years ago >>> when I worked for somebody with enough pull to sell it to >>> managment--there's been three reshufflings since and I'm back to being >>> a peon. >> >>I like Mediawiki because it's a wiki. The links, the categories, the >>"what links here" and the search box, can be used to keep control over >>a growing body of information. (I also like the templates, and the >>markup language.) > >I like it because it's the same software the Wikipedia uses, so if you >know how to edit Wikipedia entries, you know how to edit any other >Mediawiki site. Which has the fallout that unlike Microsoft's attempt (a) it actually works and (b) given sufficient hardware it is likely to handle any load that it is going to encounter.
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2020-08-09 15:33 +0000 |
| Subject | Re: wiki software, not 360 PCs was DEC |
| Message-ID | <slrnrj05pc.kpi.grahn+nntp@frailea.sa.invalid> |
| In reply to | #212580 |
On Sat, 2020-08-08, J Clarke wrote: > On Fri, 7 Aug 2020 22:45:09 -0000 (UTC), John Levine <johnl@taugh.com> > wrote: > >>In article <slrnrircp3.kpi.grahn+nntp@frailea.sa.invalid>, >>Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: >>>> Mediawiki does look good--I wish I'd known about it three years ago >>>> when I worked for somebody with enough pull to sell it to >>>> managment--there's been three reshufflings since and I'm back to being >>>> a peon. >>> >>>I like Mediawiki because it's a wiki. The links, the categories, the >>>"what links here" and the search box, can be used to keep control over >>>a growing body of information. (I also like the templates, and the >>>markup language.) >> >>I like it because it's the same software the Wikipedia uses, so if you >>know how to edit Wikipedia entries, you know how to edit any other >>Mediawiki site. And Wikipedia is also a good example of what you can do. (Although you're probably not creating an encyclopedia.) > Which has the fallout that unlike Microsoft's attempt (a) it actually > works and (b) given sufficient hardware it is likely to handle any > load that it is going to encounter. Yeah, I wonder how Wikipedia pulls that off. That and security. I also never hear "we have to use $technology because $large_company uses it and so it's proven to scale to a billion users" about Wikipedia. (It's usually LinkedIn, Facebook or SoundCloud, and the technology is usually some message queue software or a functional language.) /Jorgen -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
| From | J. Clarke <jclarke.873638@gmail.com> |
|---|---|
| Date | 2020-08-09 13:16 -0400 |
| Subject | Re: wiki software, not 360 PCs was DEC |
| Message-ID | <isa0jf1439acilmr396la4ecd6d0kuhcas@4ax.com> |
| In reply to | #212601 |
On 9 Aug 2020 15:33:00 GMT, Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: >On Sat, 2020-08-08, J Clarke wrote: >> On Fri, 7 Aug 2020 22:45:09 -0000 (UTC), John Levine <johnl@taugh.com> >> wrote: >> >>>In article <slrnrircp3.kpi.grahn+nntp@frailea.sa.invalid>, >>>Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: >>>>> Mediawiki does look good--I wish I'd known about it three years ago >>>>> when I worked for somebody with enough pull to sell it to >>>>> managment--there's been three reshufflings since and I'm back to being >>>>> a peon. >>>> >>>>I like Mediawiki because it's a wiki. The links, the categories, the >>>>"what links here" and the search box, can be used to keep control over >>>>a growing body of information. (I also like the templates, and the >>>>markup language.) >>> >>>I like it because it's the same software the Wikipedia uses, so if you >>>know how to edit Wikipedia entries, you know how to edit any other >>>Mediawiki site. > >And Wikipedia is also a good example of what you can do. (Although >you're probably not creating an encyclopedia.) Actually that's one of the things that we kind of need to do. I tried making a start on it with Micrsoft's wiki software and the first time I needed to include a diagram I found out that it wouldn't handle it in any kind of graceful manner. >> Which has the fallout that unlike Microsoft's attempt (a) it actually >> works and (b) given sufficient hardware it is likely to handle any >> load that it is going to encounter. > >Yeah, I wonder how Wikipedia pulls that off. That and security. The nature of wikipedia is such that security isn't really an issue. Anybody can change it, by design. >I also never hear "we have to use $technology because $large_company >uses it and so it's proven to scale to a billion users" about >Wikipedia. (It's usually LinkedIn, Facebook or SoundCloud, and the >technology is usually some message queue software or a functional >language.) We _are_ "large company" and we _had_ systems that could scale to a billion users. But some "consultant" convinced management that that obsolete junk (written in clunky old C and Fortran and <gasp> COBOL dontcha know) was "holding back progress" and so management decided to go with whatever the consultant recommended. But nobody looked into porting our existing code to the new system. So we are going to have to maintain the COBOL and C and Fortran until sometime around 2010 when the last policyholder holding a policy supported by those systems dies, and we are going to have to maintain another system until around 2015, and another one until around 2020, and no doubt between now and then there will be another 20 "improved" systems that we have to maintain.
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <dan1espen@gmail.com> |
|---|---|
| Date | 2020-08-09 15:00 -0400 |
| Subject | Re: wiki software, not 360 PCs was DEC |
| Message-ID | <rgph3v$ua4$4@dont-email.me> |
| In reply to | #212608 |
J. Clarke <jclarke.873638@gmail.com> writes: > On 9 Aug 2020 15:33:00 GMT, Jorgen Grahn <grahn+nntp@snipabacken.se> > wrote: > >>On Sat, 2020-08-08, J Clarke wrote: >>> On Fri, 7 Aug 2020 22:45:09 -0000 (UTC), John Levine <johnl@taugh.com> >>> wrote: >>> >>>>In article <slrnrircp3.kpi.grahn+nntp@frailea.sa.invalid>, >>>>Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: >>>>>> Mediawiki does look good--I wish I'd known about it three years ago >>>>>> when I worked for somebody with enough pull to sell it to >>>>>> managment--there's been three reshufflings since and I'm back to being >>>>>> a peon. >>>>> >>>>>I like Mediawiki because it's a wiki. The links, the categories, the >>>>>"what links here" and the search box, can be used to keep control over >>>>>a growing body of information. (I also like the templates, and the >>>>>markup language.) >>>> >>>>I like it because it's the same software the Wikipedia uses, so if you >>>>know how to edit Wikipedia entries, you know how to edit any other >>>>Mediawiki site. >> >>And Wikipedia is also a good example of what you can do. (Although >>you're probably not creating an encyclopedia.) > > Actually that's one of the things that we kind of need to do. I tried > making a start on it with Micrsoft's wiki software and the first time > I needed to include a diagram I found out that it wouldn't handle it > in any kind of graceful manner. > >>> Which has the fallout that unlike Microsoft's attempt (a) it actually >>> works and (b) given sufficient hardware it is likely to handle any >>> load that it is going to encounter. >> >>Yeah, I wonder how Wikipedia pulls that off. That and security. > > The nature of wikipedia is such that security isn't really an issue. > Anybody can change it, by design. > >>I also never hear "we have to use $technology because $large_company >>uses it and so it's proven to scale to a billion users" about >>Wikipedia. (It's usually LinkedIn, Facebook or SoundCloud, and the >>technology is usually some message queue software or a functional >>language.) > > We _are_ "large company" and we _had_ systems that could scale to a > billion users. But some "consultant" convinced management that that > obsolete junk (written in clunky old C and Fortran and <gasp> COBOL > dontcha know) was "holding back progress" and so management decided to > go with whatever the consultant recommended. But nobody looked into > porting our existing code to the new system. So we are going to have > to maintain the COBOL and C and Fortran until sometime around 2010 > when the last policyholder holding a policy supported by those systems > dies, and we are going to have to maintain another system until around > 2015, and another one until around 2020, and no doubt between now and > then there will be another 20 "improved" systems that we have to > maintain. Looks like you have your own Y2K problem. (All the dates above look like they're off by 100.) My motto, "whenever management makes a decision, that's a problem.". -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | J. Clarke <jclarke.873638@gmail.com> |
|---|---|
| Date | 2020-08-09 18:35 -0400 |
| Subject | Re: wiki software, not 360 PCs was DEC |
| Message-ID | <kfu0jflpelsln81e49g21qllpknl33iuro@4ax.com> |
| In reply to | #212617 |
On Sun, 09 Aug 2020 15:00:15 -0400, Dan Espen <dan1espen@gmail.com> wrote: >J. Clarke <jclarke.873638@gmail.com> writes: > >> On 9 Aug 2020 15:33:00 GMT, Jorgen Grahn <grahn+nntp@snipabacken.se> >> wrote: >> >>>On Sat, 2020-08-08, J Clarke wrote: >>>> On Fri, 7 Aug 2020 22:45:09 -0000 (UTC), John Levine <johnl@taugh.com> >>>> wrote: >>>> >>>>>In article <slrnrircp3.kpi.grahn+nntp@frailea.sa.invalid>, >>>>>Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: >>>>>>> Mediawiki does look good--I wish I'd known about it three years ago >>>>>>> when I worked for somebody with enough pull to sell it to >>>>>>> managment--there's been three reshufflings since and I'm back to being >>>>>>> a peon. >>>>>> >>>>>>I like Mediawiki because it's a wiki. The links, the categories, the >>>>>>"what links here" and the search box, can be used to keep control over >>>>>>a growing body of information. (I also like the templates, and the >>>>>>markup language.) >>>>> >>>>>I like it because it's the same software the Wikipedia uses, so if you >>>>>know how to edit Wikipedia entries, you know how to edit any other >>>>>Mediawiki site. >>> >>>And Wikipedia is also a good example of what you can do. (Although >>>you're probably not creating an encyclopedia.) >> >> Actually that's one of the things that we kind of need to do. I tried >> making a start on it with Micrsoft's wiki software and the first time >> I needed to include a diagram I found out that it wouldn't handle it >> in any kind of graceful manner. >> >>>> Which has the fallout that unlike Microsoft's attempt (a) it actually >>>> works and (b) given sufficient hardware it is likely to handle any >>>> load that it is going to encounter. >>> >>>Yeah, I wonder how Wikipedia pulls that off. That and security. >> >> The nature of wikipedia is such that security isn't really an issue. >> Anybody can change it, by design. >> >>>I also never hear "we have to use $technology because $large_company >>>uses it and so it's proven to scale to a billion users" about >>>Wikipedia. (It's usually LinkedIn, Facebook or SoundCloud, and the >>>technology is usually some message queue software or a functional >>>language.) >> >> We _are_ "large company" and we _had_ systems that could scale to a >> billion users. But some "consultant" convinced management that that >> obsolete junk (written in clunky old C and Fortran and <gasp> COBOL >> dontcha know) was "holding back progress" and so management decided to >> go with whatever the consultant recommended. But nobody looked into >> porting our existing code to the new system. So we are going to have >> to maintain the COBOL and C and Fortran until sometime around 2010 >> when the last policyholder holding a policy supported by those systems >> dies, and we are going to have to maintain another system until around >> 2015, and another one until around 2020, and no doubt between now and >> then there will be another 20 "improved" systems that we have to >> maintain. > >Looks like you have your own Y2K problem. > >(All the dates above look like they're off by 100.) Yep. Should have been 2110, 2115, and 2120. Eventually though the situation may stabilize with 20 or systems in continuous maintenance, with the older ones dropping off as the last policyholder dies, and new ones coming on as consultants sucker management. > >My motto, "whenever management makes a decision, >that's a problem.".
[toc] | [prev] | [next] | [standalone]
| From | maus <maus@dmaus.org> |
|---|---|
| Date | 2020-08-10 23:10 +0000 |
| Subject | Re: wiki software, not 360 PCs was DEC |
| Message-ID | <slrnrj3kvu.dqd.maus@dmaus.org> |
| In reply to | #212629 |
On 2020-08-09, J Clarke <jclarke.873638@gmail.com> wrote: > On Sun, 09 Aug 2020 15:00:15 -0400, Dan Espen <dan1espen@gmail.com> > wrote: > >>J. Clarke <jclarke.873638@gmail.com> writes: >> >>> On 9 Aug 2020 15:33:00 GMT, Jorgen Grahn <grahn+nntp@snipabacken.se> >>> wrote: >>> >>>>On Sat, 2020-08-08, J Clarke wrote: >>>>> On Fri, 7 Aug 2020 22:45:09 -0000 (UTC), John Levine <johnl@taugh.com> >>>>> wrote: >>>>> >>>>>>In article <slrnrircp3.kpi.grahn+nntp@frailea.sa.invalid>, >>>>>>Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: >>>>>>>> Mediawiki does look good--I wish I'd known about it three years ago >>>>>>>> when I worked for somebody with enough pull to sell it to >>>>>>>> managment--there's been three reshufflings since and I'm back to being >>>>>>>> a peon. >>>>>>> >>>>>>>I like Mediawiki because it's a wiki. The links, the categories, the >>>>>>>"what links here" and the search box, can be used to keep control over >>>>>>>a growing body of information. (I also like the templates, and the >>>>>>>markup language.) >>>>>> >>>>>>I like it because it's the same software the Wikipedia uses, so if you >>>>>>know how to edit Wikipedia entries, you know how to edit any other >>>>>>Mediawiki site. >>>> >>>>And Wikipedia is also a good example of what you can do. (Although >>>>you're probably not creating an encyclopedia.) > The last ex-confederate pension pension lasted to the 1950's
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2020-08-09 19:18 +0000 |
| Subject | Re: wiki software, not 360 PCs was DEC |
| Message-ID | <slrnrj0ivp.kpi.grahn+nntp@frailea.sa.invalid> |
| In reply to | #212608 |
On Sun, 2020-08-09, J Clarke wrote: > On 9 Aug 2020 15:33:00 GMT, Jorgen Grahn <grahn+nntp@snipabacken.se> > wrote: > >>On Sat, 2020-08-08, J Clarke wrote: [Mediawiki] >>> Which has the fallout that unlike Microsoft's attempt (a) it actually >>> works and (b) given sufficient hardware it is likely to handle any >>> load that it is going to encounter. >> >>Yeah, I wonder how Wikipedia pulls that off. That and security. > > The nature of wikipedia is such that security isn't really an issue. > Anybody can change it, by design. There are other aspects, like: - You don't want people to get login access on the servers via some exploit. - You don't want them to change the edit history or pages. - Denial of service. There must be all kinds of organizations (including countries, cults and drug lords) with motives to damage Wikipedia, so they must have solved that somehow. /Jörgen -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
| From | J. Clarke <jclarke.873638@gmail.com> |
|---|---|
| Date | 2020-08-09 18:40 -0400 |
| Subject | Re: wiki software, not 360 PCs was DEC |
| Message-ID | <bju0jf50lhgg4cvcfo8qrifbnpsddvchcr@4ax.com> |
| In reply to | #212618 |
On 9 Aug 2020 19:18:17 GMT, Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: >On Sun, 2020-08-09, J Clarke wrote: >> On 9 Aug 2020 15:33:00 GMT, Jorgen Grahn <grahn+nntp@snipabacken.se> >> wrote: >> >>>On Sat, 2020-08-08, J Clarke wrote: > >[Mediawiki] > >>>> Which has the fallout that unlike Microsoft's attempt (a) it actually >>>> works and (b) given sufficient hardware it is likely to handle any >>>> load that it is going to encounter. >>> >>>Yeah, I wonder how Wikipedia pulls that off. That and security. >> >> The nature of wikipedia is such that security isn't really an issue. >> Anybody can change it, by design. > >There are other aspects, like: >- You don't want people to get login access on the servers via some > exploit. What happens if they do? They change the pages? >- You don't want them to change the edit history or pages. What happens if they do? The wiki people don't know after who to send the hit squad? >- Denial of service. Plenty of ways to do that--that's not really an issue for application software to deal with. >There must be all kinds of organizations (including countries, cults >and drug lords) with motives to damage Wikipedia, so they must have >solved that somehow. Yeah, let them damage it and the various people who monitor the various pages fix it.
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <peter_flass@yahoo.com> |
|---|---|
| Date | 2020-08-09 15:30 -0700 |
| Subject | Re: wiki software, not 360 PCs was DEC |
| Message-ID | <1716702229.618704055.360152.peter_flass-yahoo.com@news.eternal-september.org> |
| In reply to | #212608 |
J. Clarke <jclarke.873638@gmail.com> wrote: > On 9 Aug 2020 15:33:00 GMT, Jorgen Grahn <grahn+nntp@snipabacken.se> > wrote: > >> On Sat, 2020-08-08, J Clarke wrote: >>> On Fri, 7 Aug 2020 22:45:09 -0000 (UTC), John Levine <johnl@taugh.com> >>> wrote: >>> >>>> In article <slrnrircp3.kpi.grahn+nntp@frailea.sa.invalid>, >>>> Jorgen Grahn <grahn+nntp@snipabacken.se> wrote: >>>>>> Mediawiki does look good--I wish I'd known about it three years ago >>>>>> when I worked for somebody with enough pull to sell it to >>>>>> managment--there's been three reshufflings since and I'm back to being >>>>>> a peon. >>>>> >>>>> I like Mediawiki because it's a wiki. The links, the categories, the >>>>> "what links here" and the search box, can be used to keep control over >>>>> a growing body of information. (I also like the templates, and the >>>>> markup language.) >>>> >>>> I like it because it's the same software the Wikipedia uses, so if you >>>> know how to edit Wikipedia entries, you know how to edit any other >>>> Mediawiki site. >> >> And Wikipedia is also a good example of what you can do. (Although >> you're probably not creating an encyclopedia.) > > Actually that's one of the things that we kind of need to do. I tried > making a start on it with Micrsoft's wiki software and the first time > I needed to include a diagram I found out that it wouldn't handle it > in any kind of graceful manner. > >>> Which has the fallout that unlike Microsoft's attempt (a) it actually >>> works and (b) given sufficient hardware it is likely to handle any >>> load that it is going to encounter. >> >> Yeah, I wonder how Wikipedia pulls that off. That and security. > > The nature of wikipedia is such that security isn't really an issue. > Anybody can change it, by design. Administrators can make pages “protected” or “semi-protected.”. With the first I think you have to have special privileges to edit, with the second you have to have an account, so you van track who edited what. I suppose a company could easily layer their own security on top, with calls to RACF, e.g. for certain things. > >> I also never hear "we have to use $technology because $large_company >> uses it and so it's proven to scale to a billion users" about >> Wikipedia. (It's usually LinkedIn, Facebook or SoundCloud, and the >> technology is usually some message queue software or a functional >> language.) > > We _are_ "large company" and we _had_ systems that could scale to a > billion users. But some "consultant" convinced management that that > obsolete junk (written in clunky old C and Fortran and <gasp> COBOL > dontcha know) was "holding back progress" and so management decided to > go with whatever the consultant recommended. But nobody looked into > porting our existing code to the new system. So we are going to have > to maintain the COBOL and C and Fortran until sometime around 2010 > when the last policyholder holding a policy supported by those systems > dies, and we are going to have to maintain another system until around > 2015, and another one until around 2020, and no doubt between now and > then there will be another 20 "improved" systems that we have to > maintain. > Ain’t that the way. > -- Pete
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <peter_flass@yahoo.com> |
|---|---|
| Date | 2020-07-25 18:39 -0700 |
| Subject | Re: 360 PCs was DEC |
| Message-ID | <1613720486.617420172.868313.peter_flass-yahoo.com@news.eternal-september.org> |
| In reply to | #212369 |
Dan Espen <dan1espen@gmail.com> wrote: > J. Clarke <jclarke.873638@gmail.com> writes: > >> The IBM operating systems have other issues. And IBM still doesn't >> have a good shell and applications. > > Except UNIX System Services (USS) in z/OS. > USS is a pretty good UNIX implementation. > I was actually thinking of a GUI shell, line WPS for VM. -- Pete
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <peter_flass@yahoo.com> |
|---|---|
| Date | 2020-07-25 18:43 -0700 |
| Subject | Re: 360 PCs was DEC |
| Message-ID | <879942733.617420411.235911.peter_flass-yahoo.com@news.eternal-september.org> |
| In reply to | #212372 |
Peter Flass <peter_flass@yahoo.com> wrote: > Dan Espen <dan1espen@gmail.com> wrote: >> J. Clarke <jclarke.873638@gmail.com> writes: >> >>> The IBM operating systems have other issues. And IBM still doesn't >>> have a good shell and applications. >> >> Except UNIX System Services (USS) in z/OS. >> USS is a pretty good UNIX implementation. >> > > I was actually thinking of a GUI shell, line WPS for VM. > Actually PROFS was a pretty good shell. Places could use PROFS the way we have been discussing using M$ Office, or probably DEC All-in-one (I’d guess). Besides the office capability both provided the ability to add your own applications integrated into the menuing system. -- Pete
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <dan1espen@gmail.com> |
|---|---|
| Date | 2020-07-25 23:32 -0400 |
| Subject | Re: 360 PCs was DEC |
| Message-ID | <rfitg6$mi4$3@dont-email.me> |
| In reply to | #212372 |
Peter Flass <peter_flass@yahoo.com> writes: > Dan Espen <dan1espen@gmail.com> wrote: >> J. Clarke <jclarke.873638@gmail.com> writes: >> >>> The IBM operating systems have other issues. And IBM still doesn't >>> have a good shell and applications. >> >> Except UNIX System Services (USS) in z/OS. >> USS is a pretty good UNIX implementation. >> > > I was actually thinking of a GUI shell, line WPS for VM. Yeah, see my other post. USS can run a GUI but there's no good reason to do so that I've seen. -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | John Levine <johnl@taugh.com> |
|---|---|
| Date | 2020-07-26 21:45 +0000 |
| Subject | Re: 360 PCs was DEC |
| Message-ID | <rfkth4$15t5$2@gal.iecc.com> |
| In reply to | #212369 |
In article <rfiile$l8n$1@dont-email.me>, Dan Espen <dan1espen@gmail.com> wrote: >J. Clarke <jclarke.873638@gmail.com> writes: > >> The IBM operating systems have other issues. And IBM still doesn't >> have a good shell and applications. ... I hear that zSeries makes a pretty good high end linux server. -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
[toc] | [prev] | [next] | [standalone]
| From | J. Clarke <jclarke.873638@gmail.com> |
|---|---|
| Date | 2020-07-26 18:01 -0400 |
| Subject | Re: 360 PCs was DEC |
| Message-ID | <e8vrhfd6kur61i6mvbjhmvrs54vsv5hios@4ax.com> |
| In reply to | #212387 |
On Sun, 26 Jul 2020 21:45:08 -0000 (UTC), John Levine <johnl@taugh.com> wrote: >In article <rfiile$l8n$1@dont-email.me>, >Dan Espen <dan1espen@gmail.com> wrote: >>J. Clarke <jclarke.873638@gmail.com> writes: >> >>> The IBM operating systems have other issues. And IBM still doesn't >>> have a good shell and applications. ... > >I hear that zSeries makes a pretty good high end linux server. But does it really bring anything to the table in that role that an Intel cluster for a 10th the price doesn't bring?
[toc] | [prev] | [next] | [standalone]
| From | Ahem A Rivet's Shot <steveo@eircom.net> |
|---|---|
| Date | 2020-07-27 06:38 +0100 |
| Subject | Re: 360 PCs was DEC |
| Message-ID | <20200727063832.5844dca15c6fadfea2c86896@eircom.net> |
| In reply to | #212388 |
On Sun, 26 Jul 2020 18:01:24 -0400 J. Clarke <jclarke.873638@gmail.com> wrote: > On Sun, 26 Jul 2020 21:45:08 -0000 (UTC), John Levine > <johnl@taugh.com> wrote: > > >I hear that zSeries makes a pretty good high end linux server. > > But does it really bring anything to the table in that role that an > Intel cluster for a 10th the price doesn't bring? It can also be a mainframe (at the same time) so it makes a good platform for migration and enhancing a legacy core with modern applications. Also it has the magic letters. -- Steve O'Hara-Smith | Directable Mirror Arrays C:\>WIN | A better way to focus the sun The computer obeys and wins. | licences available see You lose and Bill collects. | http://www.sohara.org/
[toc] | [prev] | [next] | [standalone]
| From | John Levine <johnl@taugh.com> |
|---|---|
| Date | 2020-07-26 01:24 +0000 |
| Subject | Re: 360 PCs was DEC |
| Message-ID | <rfim10$180o$1@gal.iecc.com> |
| In reply to | #212362 |
In article <tpaphf5gke3nl5sj7ou02oeuprg7onslbb@4ax.com>, J. Clarke <jclarke.873638@gmail.com> wrote: >The IBM operating systems have other issues. And IBM still doesn't >have a good shell and applications. It's been a while but my recollection is that CMS and REXX weren't too bad if you wanted to do stuff that CMS can do. -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <peter_flass@yahoo.com> |
|---|---|
| Date | 2020-07-25 18:39 -0700 |
| Subject | Re: 360 PCs was DEC |
| Message-ID | <1229230239.617420219.692022.peter_flass-yahoo.com@news.eternal-september.org> |
| In reply to | #212371 |
John Levine <johnl@taugh.com> wrote: > In article <tpaphf5gke3nl5sj7ou02oeuprg7onslbb@4ax.com>, > J. Clarke <jclarke.873638@gmail.com> wrote: >> The IBM operating systems have other issues. And IBM still doesn't >> have a good shell and applications. > > It's been a while but my recollection is that CMS and REXX weren't too > bad if you wanted to do stuff that CMS can do. > We had a guy who built a lot of stuff that way for our publishing application. XEDIT and Script with a lit of Rexx. Made it pretty easy to input and edit. -- Pete
[toc] | [prev] | [next] | [standalone]
| From | Bob Eager <news0073@eager.cx> |
|---|---|
| Date | 2020-07-26 20:18 +0000 |
| Subject | Re: 360 PCs was DEC |
| Message-ID | <ho66o1FmsnaU10@mid.individual.net> |
| In reply to | #212373 |
On Sat, 25 Jul 2020 18:39:24 -0700, Peter Flass wrote: > John Levine <johnl@taugh.com> wrote: >> In article <tpaphf5gke3nl5sj7ou02oeuprg7onslbb@4ax.com>, >> J. Clarke <jclarke.873638@gmail.com> wrote: >>> The IBM operating systems have other issues. And IBM still doesn't >>> have a good shell and applications. >> >> It's been a while but my recollection is that CMS and REXX weren't too >> bad if you wanted to do stuff that CMS can do. >> >> > We had a guy who built a lot of stuff that way for our publishing > application. XEDIT and Script with a lit of Rexx. Made it pretty easy to > input and edit. I use REXX quite a bit on UNIX; quite good for a lot of things. And the nearest I came to IBM was OS/2 for about 20 years. -- Using UNIX since v6 (1975)... Use the BIG mirror service in the UK: http://www.mirrorservice.org
[toc] | [prev] | [next] | [standalone]
| From | Ahem A Rivet's Shot <steveo@eircom.net> |
|---|---|
| Date | 2020-07-25 19:39 +0100 |
| Subject | Re: 360 PCs was DEC |
| Message-ID | <20200725193917.7ab86e5fb30f0cc8b874628a@eircom.net> |
| In reply to | #212346 |
On Sat, 25 Jul 2020 17:21:39 -0000 (UTC) John Levine <johnl@taugh.com> wrote: > In article <20200725105838.f7c55adc0a8b1643e17690b3@eircom.net>, > Ahem A Rivet's Shot <steveo@eircom.net> wrote: > > Quite so, although ISTR there being talk of a 360 on a chip at > >around the same time or a little earlier, something about a hot, hairy, > >smoking golf ball (for some reason that phrase sticks in the mind). > > IBM sold a couple of 370 and 390 add-on cards for PCs. The first one > used M68K and 8087 chips with custom microcode. They worked, it was > like a single user VM/370 system. I remember those, they were quite a bit later, the rumours I recall were around the time the PC was being developed. -- Steve O'Hara-Smith | Directable Mirror Arrays C:\>WIN | A better way to focus the sun The computer obeys and wins. | licences available see You lose and Bill collects. | http://www.sohara.org/
[toc] | [prev] | [next] | [standalone]
Page 2 of 9 — ← Prev page 1 [2] 3 4 5 6 7 8 9 Next page →
Back to top | Article view | alt.folklore.computers
csiph-web