30 ms·
Out of curiosity, what were things that these systems did poorly or that we know not to do these days?
by bane 12y ago
Out of curiosity, what were things that these systems did poorly or that we know not to do these days?
- adwf 12y agoCosting $70,000 for the base machine would be one thing.
- lispm 12y agoA later MacIvory was a third of that.
- pavement 12y ago$23,000 is still a pretty penny.
- lispm 12y agoI have for example this NXP1000, with twice the RAM: ftp://ftp.ai.sri.com/pub/mailing-lists/slug/930331/msg00117.html $18,700 in 1992. The last hardware Lisp Machine type. Many years later I got mine for free from a telco equipment manufacturer.
- michaelmike 12y agoI don't see the relevance. I, too, can easily find dead-end hardware that was expensive years ago that no one wants today. Most are just happy someone is taking that crap out of their hands. It's big, heavy, has strange power requirements, people forgot how to even turn it on and get it running, etc.
- deleted 12y ago[deleted]
- michaelmike 12y agoThanks for the downvote, guy. $18k is still a shitton of money. I guess you don't get that.
- deleted 12y ago[deleted]
- ScottBurson 12y agoSecurity was literally nonexistent. If you were at the console, you had control of the machine. Pwning one over the network was probably not difficult, though it wasn't the kind of thing people spent much time on back then.
- cturner 12y agoIs that a bad thing? I wonder sometimes how much we lose in develop collaboration due to security layers. I can imagine running a cool multiuser image in a prototyping language like to.
- bitwize 12y agoIf security is important, you lose something in terms of getting shit done. It's up to you or your organization what the tradeoff is. Fun fact: At one company I worked at, it was a matter of security policy that every machine in the company run the Bit9 binary whitelisting software. Every. Single. One. Including all the dev machines. In addition, it was decided that valuable corporate assets such as source control be airgapped from the outside network, making it difficult to run a dev machine that could access both the repo and the Web where all your documentation is. But Security was determined to be Priority One at that company, so productivity had to take the hit. If you develop the tech ten times slower and with ten times greater annoyance to your engineers, that was a worthy price to pay for not having it stolen by scary foreign spear phishers.
- pavement 12y agoBut given the level of expertise which would have supposedly been their target market, wouldn't this have been an ideal environment for security analysts to develop within? If you buy into the sales pitch, highly trained teams of developers would be properly outfitted with workstations well-suited to roll their own crypto, for development purposes, and then easily test against a wide array of complex scenarios.
- JoachimSchipper 12y agoCurrent hardware wouldn't contemplate supporting only a single, oddball (even then) language. (Although the C spec is carefully written to allow C-on-Lisp - e.g. by making it illegal to compare pointers not pointing to the same array, allowing a C-"object"-per-Lisp-object implementation - real C code tends to make assumptions.)
- lispm 12y agoSymbolics sold ISO Pascal, C, Ada, Prolog and Fortran compilers for it. I've used TeX and the original MIT X11 server on a Lisp Machine.
- ScottBurson 12y agoMy Zeta-C compiler predated Symbolics C by almost two years. One customer said they'd run millions of lines of code through it.
- hga 12y agoSo Symbolics' announcement of their vaporware C compiler didn't cost you all your sales? Good to hear that.
- ScottBurson 12y agoIt was a problem, as I recall, but not nearly as big a problem as the fact that people stopped buying the machines :-) Actually, it turned out -- though I never managed to communicate this to potential users -- Zeta-C and Symbolics C served different use cases. Symbolics C was best for porting entire C programs; Zeta-C was best if you had a library written in C and wanted to call it from Lisp.