|
Silver Alicorn posted:they ported all their custom scripts to netbsd so they could upgrade to more modern hardware their custom scripts were all written on att system V anyway a shell script from that era would probably work fine on bash even
|
#
¿
Jun 27, 2017 02:33
|
|
|
|
| # ¿ May 3, 2024 01:23 |
|
|
eschaton posted:what about their XKL TOAD-1 do modern xkl boxes still have tops-20 or whatever running inside?
|
|
#
¿
Jul 2, 2017 19:39
|
|
|
eschaton posted:that's what I hear http://rbnsn.com/pipermail/info-vax_rbnsn.com/2016-December/092947.html it appears the software is different but the underlying hardware is still dec-compatible 36 bit stuff
|
|
#
¿
Jul 2, 2017 20:30
|
|
|
RISCy Business posted:or bitcoins if your brain is broken beyond repair nice username + thread topic combination here
|
|
#
¿
Jul 4, 2017 19:19
|
|
|
vi was a visual mode hastily grafted to a text editor meant for teletypes vim was an attempt to re-write vi for amiga computers. this was arguably not a very good idea. i don't know how either one remains relevant today in the year two thousand and seventeen
|
|
#
¿
Jul 4, 2017 19:58
|
|
|
power botton posted:emacs is the inner platform effect for OSes sortof. modern emacs explicitly set out to be an "inner platform." i'm not sure it counts as inner platform effect if it happens intentionally. the original lisp machines were single-user workstations in a network environment. a lispM was the ultimate luxury for programmers. but nobody could afford one gnu emacs, and gosling emacs before it, were crude attempts to re-create the lispM os + environment on top of unix, so you could have a taste of luxury on $10,000 workstations instead of $60,000 workstations the lispMs are dead and gone but gnu emacs is still with us
|
|
#
¿
Jul 4, 2017 20:15
|
|
|
eschaton posted:I so wish Symbolics (or TI/LMI) would've hopped on the 68020 or 80386 train in the mid-1980s, no matter how nice they are a LispM is a royal pain to keep running ti and symbolics concluded it wasn't possible, for performance reasons xerox did actually port their lisp system to an emulator. there's even an x86/linux version floating around. i assume they were more open to it because interlisp's native hosts were so slow by 1980s standards (pdp-10 or dorado, pick your poison) eschaton posted:they honestly weren't even attempts to clone the LispM environment, not even the relatively primitive CADR/LMI environments much less the Symbolics Genera or later TI Explorer environments i'm not so sure about this. gosling, and gosling's emacs, came out of CMU's work with lisp on unix. he wanted a lisp-enabled, lisp-extensible editor that didn't require cmu lisp to get started. (and who can blame him. on 1980s hardware, cmu lisp was a real bear) stallman, and gnu emacs, were explicitly attempts to clone the CADR environment that stallman was so fond of, after he gave up his quixotic effort to clone symbollics advances on lmi and cadr machines. i mean, sure, stallman would have had his own history with emacs on its/tenex/whatever, but that doesn't seem to have been very influential on gnu emacs. the old pdp-10 emacs doesn't really resemble gnu emacs. the macro language looks more like vimscript than anything. it doesn't have a debugger. there's no notion of processes. as with vimscript, it's not a complete enough environment to write any novel applications. it's just a scriptable editor -- nothing more, nothing less. gnu emacs started on day one with a pretty fancy lisp interpreter and complete api to drive the editor. it was never a good lisp but it was considerably more than a bundle of editor macros.
|
|
#
¿
Jul 5, 2017 04:20
|
|
|
|
| # ¿ May 3, 2024 01:23 |
|
|
here is a freeware copy of the xerox interlisp environment, for those so interested specifically it is a gui application, "grammar writer's workbench," which is hosted inside a complete interlisp setup. i think all the necessary dev tools are included, but i don't know enough about xerox-land to say. i have successfully gotten it running in the past but i don't really know how to use it! http://www2.parc.com/isl/groups/nltt/medley/ ftp://ftp.parc.xerox.com/pub/lfg/README.TXT the website omits any mention of the linux/i386 version, but the binaries are there on the ftp and described in the readme
|
|
#
¿
Jul 5, 2017 04:23
|
|