Earlier quoted context omitted.
Prolog, Dylan, Julia, and R are stuff like Lisp, Tcl, and Rebol. I don't know about Erlang, and I don't know what pjmlp means by "Lisp-2", which I normally interpret as meaning a Lisp with different namespaces for functions and variables, following Steele's terminology.
> ... I don't know what pjmlp means by "Lisp-2", which I normally interpret as meaning a Lisp with different namespaces for functions and variables ... There indeed was a language named LISP 2 : https://dl.acm.org/doi/pdf/10.1145/1464291.1464362 I posted it on HN two weeks ago but it didn't get much traction: https://news.ycombinator.com/item?id=41640147
The Rise of Worse Is Better (1991)
151–160 of 351 posts
Re: The Rise of Worse Is Better (1991)
#152I'm always happy whenever this old article goes viral. For two reasons: First, learning to accept the fact that the better solutions doesn't always win has helped me keep may sanity over more than two decades in the tech industry. And second, I'm old enough to have a pretty good idea what the guy meant when he replied, "It takes a tough man to make a tender chicken."
And, at the risk of intentionally missing the metaphor: they do in fact make automated tenderizers, now ;) https://a.co/d/hybzu2U
Re: The Rise of Worse Is Better (1991)
#153Earlier quoted context omitted.
The OSI stack was also designed using the packet-switching approach. Rob Graham's "OSI Deprogrammer" is a book -length article about how TCP/IP beat OSI, and how the OSI model is entirely worthless: https://docs.google.com/document/d/1iL0fYmMmariFoSvLd9U5nPVH... I'm not sure he's right, but I do think his point of view is important to understand.
Wow, you're not kidding about book-length: at 246 pages, that's an epic takedown. Learning all kinds of other things about networking along the way, though. I do remember all nine layers of the OSI stack though: physical, data link, network, transport, session, presentation, application, financial, political.
Re: The Rise of Worse Is Better (1991)
#154Earlier quoted context omitted.
"Expedient" is a common (or at least not rare) English word that means something like "practical and effective even if not directly attending to higher or deeper considerations." For example, if two students in a class are having frequent confrontations that bring learning in the class to a halt, and attempts by teachers and counselors to address their conflict directly haven't been effective, the expedient solution…
I think this is misleading -- geoengineering + social change will be necessary. You're not going to Scotty your way out of climate change.
Re: The Rise of Worse Is Better (1991)
#155Earlier quoted context omitted.
VAX Pascal is viable for systems programming (though standard Pascal wasn't). I only ever used VAX BASIC a tiny bit; was it interpreted like microcomputer BASICs? That made BASIC a nonstarter for "serious software" in the 80s. Not having records, local variables, or subroutine parameters was also a pretty big problem, but maybe VAX BASIC fixed that. I wasn't paying for access to VMS either; it just didn't hold a cand…
No one really uses standard C for systems programming, yet that always applies to other languages. There is always Assembly, compiler extensions, or OS specific APIs, as part of the deliverable. Funny how UNIX folks always have these two weights approach. I beg to differ in wax quality for candles, but if we get to do juice with bitter lemons, so be it. At least is refreshing during Summer.
K&R C has separate compilation, pointer casting, a usable but janky and bug-prone variable-length string type, variadic functions, static variables, literal data of array and record types, bitwise operations, a filesystem access API, and an array iterator type. None of those require "assembly, compiler extensions, or OS specific APIs." (Well, I'm not sure if they specified variadic functions in the book. The first ANSI C did.)
Jensen & Wirth Pascal has none of those, making it completely inadequate for anything beyond classroom use, which was what it was designed for.
Each Pascal implementation that was used for systems programming did of course add all of these features, but many of them added them in incompatible ways, with the result that, for example, TeX had to implement its own string type (in WEB).
Re: The Rise of Worse Is Better (1991)
#156I remember when I had a lesson about OSI layers, where the teacher has carefully described all the layers in detail and then said something like "most of this is not important, these layers don't really exist, TCP/IP got popular first because it's just much simpler than OSI was"
Re: The Rise of Worse Is Better (1991)
#157Earlier quoted context omitted.
Oh, there's an entirely different feature-length article to be written/found about how packet switching beat circuit switching and the "Internet approach" beat the telco approach. The great innovation of being able to deploy devices at the edges without needing clearance from the center. I don't think very many people even remember X25. The one survivor from all the X standards seems to be X509?
LDAP is “lightweight” compared to the X.500 directory access protocol. LDAP DNs are basically the same as X.500 DNs. SNMP is “simple” compared to X.711 CMIP. But SNMP also uses ASN.1 and X.660 OIDs.
Re: The Rise of Worse Is Better (1991)
#158Earlier quoted context omitted.
Also Lisp came out in 1958, and ESPOL/NEWP in 1961, PL/I and its derivates, predating C by a decade. Had AT&T been allowed to charge real money for UNIX, and the Worse is Better would never happened.
Imagine if RMS brought Lisp OS with Emacs not being bound to GNU/Unix. JITted Emacs since the 2000 and Eshell as the default CLI, with a floating WM as an easy desktop. Multithreaded, own modules for images/PDF and whatever. No need for security, daily backups and rollbacks would be granted. Today you would be 'rewinding in time' from Emacs if any attack happened.
Re: The Rise of Worse Is Better (1991)
#159Earlier quoted context omitted.
Such a weird take on HN. Lisp should be experimented with if only to appreciate the profound beauty of a small, powerful, cohesive design. It is a wholly different feeling from industry standard languages which are constantly changing. In Lisp, almost all of the language’s power is in “user space.” The ramifications for that are deep and your beliefs as to whether that is good are largely shaped by whether you believ…
> languages which are constantly changing They change because they are used.
Re: The Rise of Worse Is Better (1991)
#160There was an article posted on here[1] a while back that I only just found again, introducing the term "expedience." The idea was that we think we live in a world where people have to have "the best" sweater, be on "the best" social network, drive "the best" car, etc. But when you look at what really WINS, it's not the best, it's the most "expedient" - i.e. sufficiently good, with built-in social proof, inoculated of…
Your model of the world is not perfect so instead of trying to find a globally optimal solution, you are satisfied with a local optimum that exceeds some threshold that has to suffices. https://en.wikipedia.org/wiki/Satisficing