HNHacker News
TopNewBestAskShowJobs

vincent-manis

1,027 karma · joined April 23, 2020

submissionscomments
vincent-manis··on Phrase origin: Why do we "call" functions?
GLENDOWER: I can call spirits from the vasty deep.

HOTSPUR: Why, so can I, or so can any man; But will they come when you do call for them?

-- Henry the Fourth, Part 1

vincent-manis··on Swearing as a Response to Pain: Assessing Effects of Novel Swear Words
Untergrundbahnhofzeitschriftsplatz: Subway station newspaper stand
vincent-manis··on Let's Talk About Writing in Tech
The “atomization” issue is one of my biggest bugbears, which I often comment on here. If your project's documentation is a website with many small documents all linked together in multiple ways, don't expect me to spend time trying to sort it all out. I recognize that some people are hyperlink-happy, but my way of learning was influenced by an obsolete technology called “books”[1], which provide a linear path, so later topics can build on earlier ones. This is very basic pedagogy, which so many documentation practices ignore.

[1] “When I was your age, television was called books.” The Princess Bride

vincent-manis··on The Humble Programmer (1972)
OS/360 was a victim of over-ambition. Originally, it was to run on all models of System/360 (maybe not the Model 20, which implemented only a subset of the ISA), and it was complex enough that there were challenges in building it. IBM ended up spinning off the smaller models to IBM Germany, DOS/360 came from there, and subsetting OS/360 into 3 levels, so they could get something out the door only a bit late. OS/360 by some measures is one of the most successful operating systems ever: IBM's current z/OS is a remote descendent of it. Yes, it is pretty horrible to use (three letters: JCL), but it certainly was successful.

“The Mythical Man-Month” is not about OS/360 as such, but about project planning and specifically what was learned about project management during the development.

vincent-manis··on Iron Spring PL/I Compiler
I haven't written a PL/I program since about 1985, but I still have a certain affection for the language. It was a genuine attempt to create a new language that would be better than Fortran and Cobol (and Algol, for that matter). The designers bit off way more than they could chew; it has the equivalent of threads, but threads weren't understood at all in those days. Even procedures were not understood: because of the multitasking, on procedure entry, the original IBM PL/I (F) compiler used a system call (GETMAIN) to allocate a stack frame, which was freed on exit. This led to the hilarious advice in the (F) Programmers' Guide: “Do not use procedures, they are expensive.”

The preprocessor was another problem. Its language was Turing-complete, but programs that used it were essentially undebuggable.You had to look at the preprocessor output (which was generally unreadable) to fix even the smallest mistake in using it.

Finally, the language designers followed the Cobol principle of making every pre-defined facility a statement. So there are record I/O statements, stream I/O statements, and on and on. This would all have been much better done with comprehensive library facilities, which were not well-understood in those days.

With all of that said, if I were to find myself required to write PL/I code nowadays, I would find it a tolerable matter. I'm glad, even if it's only for legacy code, that the Iron Spring compiler exists.

(And I even managed to get this comment done without mentioning the time that the PL/I (F) compiler produced a box of printer paper, saying “ERROR: COMPILER IS UNABLE TO ABORT”, over and over, double-spaced, for 2000 pages, accompanied by a nasty letter explaining that I was “abusing” Computing Centre services. That really was a rocky time for PL/I programmers.)

vincent-manis··on Year 2038 Problem
Amongst my friends who are non-tech people it is a common belief that Y2K was a big scam, and that it all just went away when the calendar turned. I have to point out over and over again that it all “went away” because organizations spent billions of dollars modernizing their software (which was motivated by, but not limited to, addressing Y2K, we'll never know what the total cost of that was).

I expect the same, but worse, in 2038.

vincent-manis··on Our Journey Through Linux/Unix Landscapes
If I were asked this question, except as a piece of trivia exchange, I wouldn't want to work for them. There are arguments in favour of many OSes (including those that I used in the long-ago past on long-forgotten iron), and many against those same systems. Using any OS is generally a trade-off; so if asked `what OS do you use?', I would answer `whatever is suitable for the problem and equipment at hand'. If asked `what is the best-designed OS you have ever seen', I'd instantly respond `Plan 9', which I have never actually used.

As it so happens, I recently transitioned my daily driver laptop from Debian to Debian running under WSL2 on Windows. I had good reason for doing it. But I guess running that makes me a double loser.

vincent-manis··on Building my childhood dream PC
My teenage dream machine was a PDP-8 (the original) and a Teletype ASR-33. Fortunately, I never got it.
vincent-manis··on How to use an en-dash and em-dash correctly? (BrE)
My spelling is generally very good, and I know the difference between “e.g.” and “i.e.”. I guess I'm an AI.
vincent-manis··on Microsoft's many Outlooks are confusing users – including its own employees
Being a Thunderbird user, I feel as though I've missed out on a critical development in tech history.
vincent-manis··on Teach, Don't Tell (2013)
I agree with another commenter that this doesn't tell the entire story, but it tells almost all of it. Nowadays, I discover some new piece of software, visit the Documentation section of its website, and the first thing I see is `How to build SuperMung on the Whizzbang 47 using Mark Williams C'. I have no idea what SuperMung is for, how to use it, what errors I might make, and how to install it on Debian. Similarly, I go to the website for a new programming language, see some examples that give me little insight into what it is for, and find not even an incomplete language specification.

Proper documentation leads me by the hand, starting on what the software is for, what platforms it runs on, some examples of its use (including examples that show how it is useful for solving real-life problems), a thorough tutorial on how to use it, and finally a complete and properly indexed/searchable reference.

Back in the 1980s, I got myself in trouble: I promised a 100-page manual for a software system I had written, and I decided to do it in the then-new TeX. But this was before The TeXBook was published. So I learned TeX by reading the literate source for the code. The manual was duly ready on time, and served the literally thousands of students who relied on it for the next few years.

But when I finally got a copy of The TeXBook, I was astonished by how little I had actually known about using TeX. I had presumably been mostly using it to answer questions such as “why doesn't this work?”, and a lot of the overall principles had simply not been apparent to me. Once I had learned TeX properly, I learned a great deal about how it all worked by going back and reading the literate source. Knuth is a brilliant (if highly idiosyncratic) programmer.

My point here is to emphasize that when someone releases software, their job is not done unless people can learn to use it. That doesn't just mean completeness and accuracy, but a through-line, apparent to the reader, from learning what it does all the way to mastering it, along with the kind of reference information needed when using it.

vincent-manis··on The DOJ still wants Google to sell off Chrome
I have a very nice Chromebook tablet (a Lenovo Duet). I use it to run a Debian Linux VM; it has its quirks, but I use it to run Emacs, TeX, and various Scheme implementations. It is relatively cheap, and even though it's a relatively low-powered device, it has adequate performance for my needs. (And yes, it is not “really” Linux: you can't install your own window manager, for example. But it's usable.)

I have lots of criticisms of Chrome OS, but the fact is that the year of Linux on the Desktop has arrived. You buy one of these machines, and out of the box you can have Linux apps (and a terminal) running within 15 minutes of switching the machine on.

vincent-manis··on Don't Recurse on Untrusted Input
Since iteration is a special case of recurson, this also tells us not to let user input cause an infinite or too-long-running loop. Profound, eh?
vincent-manis··on Hard numbers in the Wayland vs. X11 input latency discussion
I have no idea of the difference(s) in performance between wlroots and Gnome's compositor. Protocols do not have performance, implementations do. If someone can prove that the Wayland protocol, on a certain set of tasks, and in a certain environment, has a better or worse performance than the X11 protocol, then it might be possible to make abstract comparisons on protocol.

Given that Gnome runs on both X and Wayland, it might be interesting to hear from the Gnome authors on the performance differences.

vincent-manis··on Hard numbers in the Wayland vs. X11 input latency discussion
>If the gnome composting ready for primetime, then Wayland isn't ready for primetime.

I use Sway, which uses a different compos[i]tor than Gnome. I would like to see similar results for wlroots, Sway's compositor, though I'm not actually interested enough to do the experiment (I guess that would be comparing Sway with i3). Cursor lag in Sway is not enough to bother me. I have on occasion used Gnome on the same machine(s), and never been bothered by lag.

As others have pointed out, Wayland is a protocol, not a compositor.

vincent-manis··on The Unisys Icon: One Canadian Xennial's Memories of Ontario's Obscure Computer
In my OS course, in 1969, I wrote an IPL (bootstrap) program that copied cards to the printer, running in supervisor mode. It ran on a 360 virtual machine under the MTS time-sharing system. Before that, I wrote programs in assembly language for an IBM 7044, and I even was allowed to operate the 7044 on some graveyard shifts. I also wrote programs that ran on a CDC 3600, a Univac 1108, and a Honeywell 200.

But I liked the PDP-8 best.

So there!

vincent-manis··on What did Ada Lovelace's program actually do? (2018)
Not sure which Fortran this refers to. I never used Fortran I, but as I understand it, names were up to 6 characters long, first character alphabetic; names with initial letter A-H and O-Z were REAL, I-M INTEGER (Fortran II added declarations to override the defaults). Dartmouth Basic restricted names to a single letter and an optional digit.

Incidentally, the various Autocode languages of the 1950s in Britain had 1-character variable names.

vincent-manis··on A new video captures a 1968 demo of IBM’s Executive Terminal
One very small correction: QUIKTRAN wasn't a “mathematical utility”, but an early timesharing system, I think running on a 7044 (coincidentally, my first mainframe). It offered an interactive Fortran system, with editing and debugging facilities. IBM's later CALL/360 system was a successor to this, adding PL/I and Basic.

Interesting UX fact: IBM researchers looked at user satisfaction on this system. They found that it wasn't poor response time that bothered people, but variability of response times. If users couldn't predict how long an operation would take, that bothered them. So they inserted delays so that average response times were maybe longer, but variance was lower. And users were happier.

vincent-manis··on The Opposite of Documentation is Superstition (2020)
I can't remember the number of times I have given up on software because there is no “Concepts and Facilities” document that gives me a mental model of what the program will do and how I operate it. Instead, one sees a website with a mass of unrelated documents that I'm supposed to read in some order, and divine how everything works.

Maybe because I'm a child of the 20th century that I value documentation that gives me a path from understanding what and why to learning how I can use it, with a master index so I can look up exactly what the “Mung Until No Good” command does, and see which other commands relate to it.

Perhaps one day generative AI will be good enough that we can feed in one of these websites, with its pages with titles like “Migrating from V4.7.2 to V4.7.3” and “Building for OS/2 Warp” (I exaggerate, but only slightly) to documentation that is useful for learning, use, and troubleshooting. I live in hope.

vincent-manis··on Owl Lisp – A functional Scheme for world domination
I haven't looked at it, but it's purely functional (so no destructive operations such as set!). It can't be called Scheme, because it's a subset of RnRS Scheme; that's why Racket isn't called PLT-Scheme any more. I can imagine this as a teaching tool (though the FAQ says the error messages aren't good), or perhaps usable as an extension language.

I'm going to look at it as a scripting tool that compiles to C.

I used to work for a company whose internal communication often claimed “world domination” as its ultimate goal. I just looked at revenue estimates for its market sector, this company isn't in the top 5, and is far behind the leader. Let's just leave Owl's world domination goal as aspirational.

vincent-manis··on An ad giant wants to control your next TV's OS
I have a smart TV running Roku. I still use cable (for news), so the other 2 sources I see are the 2 computers I have connected. The only time I ever see Roku is when I'm selecting a source. The TV is smart, but I'm smarter: no Ethernet cable.
vincent-manis··on Thomas E. Kurtz has died
I am not surprised that large-scale programs were written in Dartmouth Basic, or that those programs satisfied the needs of their users. Some program libraries include programs in unstructured Fortran IV, which have been running satisfactorily for 60 years. Similarly, some very complex hospital systems were written in Mumps (aka M), in which, due to both the language and the programming style used, programs looked more or less like line noise.

I once consulted for a company that had a product written in Pick Basic. This product had been sold around the world, and was very successful in their market. They wanted to modernize the product, so they went to a big DBMS vendor with a target business problem; the vendor said it would take several months to produce a sample solution. The company gave me the problem description. The next day I went back with a PoC program, 50 or so lines of C++. I emphasized that I had used C++ just because it was convenient (and that really any standard language would do), explained what parts of the problem were not addressed, and estimated that the entire program would take about a week's work to do. The client agreed on this, but said (a) that they needed a solution that was compatible with Pick Basic, and (b) their programmers only knew Pick Basic and wouldn't be any good at learning anything else. I don't know what became of the client and their product. (The Pick system was a combination of a variant of Dartmouth Basic and a DBMS.)

I'm not in any way saying that Dartmouth Basic is useless. I am saying that creating this language was NOT the flash of genius Kemeny and Kurtz actually had, but that making computing accessible to non-experts was the actual point.

vincent-manis··on Thomas E. Kurtz has died
I was 13 when DTSS was introduced, so never had an opportunity to learn programming with Basic. Fortunately, that didn't harm me, and I've managed to compensate for this disadvantage.

I don't want in any way to minimize the impact of a language designed for non-experts. But, while Basic, and its many limitations, was the best that could be done with the relatively limited systems it was first implemented on, it doesn't scale. I recall, around 1970, building an interactive front end for an inventory system, using a commercial company's version of Dartmouth (or GE) Basic. It came to about 900 lines, and even I couldn't make sense of it.

It's a mistake to believe that non-experts write 20-line mortgage programs, or 50-line dice games. If what you're teaching them has any value, they will naturally want to write programs that grow organically as they understand the problem better. Dartmouth Basic is a language in amber, best understood as what could be done given the equipment of the 1960s, and the understanding of programming development at the time. It was neither better nor worse than other interactive languages of the time, for example, JOSS (which begat PIL, DEC's FOCAL, and even the horrific MUMPS, closer to our time).

I think that the true value of Kemeny and Kurtz's contribution was encouraging programming as a thing for “ordinary” people, rather than a priesthood. The language they invented was developed prior to clear understandings of structured, object-oriented, and functional programming, all of which have something to say even to non-experts. (And, yes, Microsoft continued to produce products with “Basic” in their names, but they have little to do with anything that was developed at Dartmouth.)

So, kudos to all the folks who learned their programming with Dartmouth-style Basic. But I think there are a lot of modern tools that not only help non-experts write short programs, but scale well as their knowledge and skill grows. Smalltalk was one system that demonstrated that, but in more recent memory, Python and Racket are also good examples.

By comparison with film, Georges Méliès did some amazing work in 1900, but nobody would confuse that with the work of modern directors.

(I don't want to get into a discussion of What Is The One True Introductory Language; I have my opinions on that, but they are not relevant here. Instead, I am trying to put the very significant contribution of Kemeny and Kurtz—democratizing computing—into what I see as a better perspective.)

vincent-manis··on My company has banned the use of Jetbrains IDEs internally
OK, since we're wasting our time on the Pointless Editor War, I shall confess I know exactly one thing about Vim, the command `:q!'. That's all I've ever needed to know.
vincent-manis··on The Soul of an Old Machine: Revisiting the Timeless von Neumann Architecture
Many years ago, I was a user of an IBM 1130 computer system. It filled a small room, with (as I recall) 16K 16-bit words and a 5MB disk drive, which was quite noisy. I would feed in my Fortran program, then head down to the other end of the building to get coffee. The computer would think about the program for a while, and then start writing the object file. This was noisy enough that I'd hear it, and head back to the computer room just in time to see the printer burst into action.

(Please feel free to reference the Monty Python “Four Yorkshiremen” sketch. But this really happened.)

vincent-manis··on Ask HN: If you were rewriting Emacs from scratch, what would you do differently?
I am proudly not-normal, in that case.
vincent-manis··on Ask HN: If you were rewriting Emacs from scratch, what would you do differently?
If I were rewriting Emacs, I would not replace its language with Python, Lua, or Cobol.

I don't like those languages, and I have just as much right to say that as the people who don't like Lisp.

vincent-manis··on Show HN: TurtleSpaces Web Logo – online 3D Logo implementation
One of the best-known results in turtle geometry is that drawing any closed path results in you turning exactly (a multiple of) 360 degrees, the Total Turtle Trip Theorem. You get into calculus by considering a circle to be the limit of `forward 1 right :n' as n approaches 0. This all is well stated in an AI memo by Seymour Papert, `Teaching Children About Mathematics vs Teaching Children To Be Mathematicians'.

In another universe, this might have all radically changed math (and other areas of) education. Alas, that is not this universe.

vincent-manis··on Is English a “creole Language”?
I used to joke with a friend of mine who was of Netherlands descent by saying that Dutch is misspelled English. (And, yes, I'm aware of the several rounds of orthographic reforms that Dutch has experienced.)
vincent-manis··on Coding Font by Typogram – Find Your True Love of Coding Fonts
I went through the whole thing, but I liked none of the fonts--not even Inconsolata, which I used for years--as much as Cascadia Code, which in its most recent incarnation even has a Nerd Font/Powerline version.
← PreviousPage 4 of 13Next →