HNHacker News
TopNewBestAskShowJobs

fusiongyro

5,495 karma · joined September 17, 2008

Daniel K Lyons

http://www.storytotell.org

Feel free to email me at fusion at storytotell dot org.

[ my public key: https://keybase.io/fusiongyro; my proof: https://keybase.io/fusiongyro/sigs/aYrkbCZouBBhqp_qOKPGdBfIn---A8P8wPVCKLSlpnA ]

submissionscomments
fusiongyro··on Voynich manuscript: the solution?
I agree. To claim a solution without writing out the whole thing so it can be analyzed in depth seems absurd to me. I'm also not convinced that the statistical analyses that have been thrown at it would fail to detect patterns of meaning that are obscured merely by abbreviation.
fusiongyro··on Lisp Machine Manual (1984)
I don't have to explain why Lisp failed to take off. I just have to explain why C did, because network effects are more significant than language advantages. This is my central thesis.

I don't think awareness of Lisp was evenly distributed among people developing on PCs in the time period when the network advantage was obtained. Even if it was, if there were already a decent C compiler, I don't think most practical engineers would immediately embark on a compiler development project. During this era, those who did know about Lisp certainly would have regarded it as being too resource-intensive for work in a resource-constrained environment like the PC.

I think it's specious to say it's easy to develop a simple Lisp compiler, so why didn't anything get ported. The code you may have wanted to port would not have been written in some minimalist dialect of Lisp, it would have been written in ZetaLisp. So there would be assumptions about resources and the underlying system that you would have to fake. And again, we're talking about porting from a resource-rich environment to a resource-scarce environment.

It was probably a reach for me to say there wasn't anything to port. But what would someone have wanted to port? A graphical application that ran on a Lisp machine would have made assumptions about the display that aren't true about a PC. An academic AI program would have been too short on resources to be much use.

What wound up selling the PCs in the early days was business applications. Were there an assortment of useful business applications on Lisp machines that there was commercial demand for? WordStar and Visicalc invented that territory and were first released in the late 70s—does anyone remember programs for the Lisp machine that businesses were clamoring for? And really, software churn has always meant there are more new programs in use than old ones.

What I don't have an explanation for is why the C compilers produced better code than the Pascal compilers. Partly, I know p-code made it faster to build a Pascal compiler but I don't know why it inhibited development of more performant ones. Turbo Pascal's speed of compilation was a result of not having an AST, which probably inhibited performance optimizations, but that may have been too late in the story to explain anything. And I don't have an explanation for why nobody developed a Lisp-like language that had explicit allocation. My best guess would be simply that their attention was elsewhere, probably working on AI, which wouldn't bottom out until after the winners were already entrenched.

By the way, in case it isn't clear, I am really enjoying this conversation. I'm very interested in this window of time in computing and if I have a wrong idea about something, I do want to know. The only way to preserve this history is to talk about it and keep the memory alive.

fusiongyro··on Lisp Machine Manual (1984)
It ran on several machines, but not the ones that mattered. The existing code was irrelevant and not portable.

I'm not denigrating Lisp. I'm saying the network effects favored C because the PC happened to take off.

fusiongyro··on Lisp Machine Manual (1984)
So how did Lisp have the home court advantage then? :)
fusiongyro··on Voynich manuscript: the solution?
Where's the actual solution? I feel like I'm missing something because what I see is some plausible commentary about it and some interesting discussion of Latin and ligatures but where's the actual decoding of the writing?
fusiongyro··on Lisp Machine Manual (1984)
Lisp had a 10 year head start on expensive academic machines that were low on industry uses. C had a head start on high-end mainframes for actual work. Then the main contenders on the nascent PC were assembly, C and Pascal. P-code based compilers arrived quickly and were faster to develop with, but the resulting code was inefficient—and early PCs were sufficiently resource-constrained that inefficient code was very noticeable. So C obtained the territory that mattered: high-end business machines and the low-end machines that would spark the computing revolution, and just had to grow the two together.

Lisp had a head start, but wasn't on the track that mattered.

fusiongyro··on Lisp Machine Manual (1984)
A more powerful language is not enough of an advantage to defeat entrenched alternatives with strong network effects. There isn't a reason why language X is not entrenched, but there are historical reasons why C, C++ and Java are entrenched. Lisp just isn't enough more powerful than them to beat their home-court advantage. I guess I'd say, Lisp might be 10x better, but the network effects are orders of magnitude more meaningful than that intrinsic benefit.

It's not a very meaningful answer to the question, but it's a bit like asking why Todd isn't rich when we all know Todd is a smart guy. It's because getting rich takes more than raw intelligence.

Suppose you have a wildly evolving field where nobody can really predict what technologies are going to be successful in the market beyond the next five years or so. Suppose you have no internet. Suppose there are thousands of programmers with the ability to invent a language. Wouldn't you expect that some of them will, by happenstance, wind up on successful products and become successful while others stay relatively unknown? That's the birth of the mainstream programming languages and their antecedents in the 70s and early 80s.

fusiongyro··on Lisp Machine Manual (1984)
The classic joke in here is that if you look up "fascism" in the index, it goes to the section about logging in. User authentication wasn't part of the dream, so having been forced to build it, they embedded a dig on it right in the manual.

https://hanshuebner.github.io/lmman/files.xml#fascism

I think there are a few other jokes in the index but I don't recall what they are.

fusiongyro··on Why favor PostgreSQL over MariaDB/MySQL?
I have found Solr to be more reliable than ES and faster than Postgres for FTS. It is cool to be able to do it in-database though. Solr is a bit more work to configure than ES though.
fusiongyro··on Why favor PostgreSQL over MariaDB/MySQL?
To restate your other reply, key-value allows you to sweep consistency problems under the rug. What happens if two transactions try to update the same row? One of the transactions fails. What happens if two clients write different values to the same key in a multi-master key-value store? The last one in wins and the first write is just lost.

Many of the NoSQL databases have provisions for these situations so they can handle both writes but bubble the decision up to the application layer. CouchDB, for instance, will tell you you've got multiple versions and has a way for you to tell it how to resolve the conflict. CRDTs let you bake the logic in for handling a conflict. MySQL does not do any of that. If your database consists of "likes" and other low-value data like that, you may not care if you're losing data at some low rate. Reddit is in that situation, and the decision seems to work for them. But I don't think it generalizes to all situations.

fusiongyro··on The sudden death and eternal life of Solaris
Terrifying!
fusiongyro··on The sudden death and eternal life of Solaris
Sure. But AIX is something you are forced to use, not something you opt-in for. All the remaining commercial Unixes are kind of in that boat.

People my age and younger just didn't get much access to commercial Unix environments when we were growing up. Once we got into industry, we found it hard to see the justification for high Unixes when we had experienced good results with low Unixes. So the low Unixes have mostly won the war. This story repeats time and time again in our industry: the freest foo conquers the non-free foo, even if the non-free foo is technically superior.

fusiongyro··on Why favor PostgreSQL over MariaDB/MySQL?
I read their article, and a dozen of the rebuttals. If you want to use MySQL badly enough, you can.
fusiongyro··on Why favor PostgreSQL over MariaDB/MySQL?
As someone who might fairly get scolded for this, we feel like praising MySQL's features is a bit like enjoying the recessed lighting and granite counters in a house whose roof is actively leaking.

There are certainly features MySQL has that Postgres doesn't, but data integrity is problem 1, and most of us got burned by MySQL on that one at some point before we got here. Or, we deployed MySQL and then found out that the features we were depending on were InnoDB-only, but switching to InnoDB cratered our performance. Or we tripped on one too many of MySQL's numerous special cases or silent limitations.

You can use MySQL productively. You can even benefit from its special features. But the thing taken together is a bit of a mine field.

Postgres has some false advertising issues too ("object-relational"?) but the day-to-day living with it is a lot nicer, because the roof doesn't leak. I can live without the granite counters.

fusiongyro··on Why favor PostgreSQL over MariaDB/MySQL?
Advanced replication strategies in MySQL and Oracle mostly cause hair loss and divorce. Everywhere I have worked that uses these databases eventually convinces itself that it needs futuristic replication technology and then goes on to suffer from outages and weird corruption. It turns out, distributed consistency is a hard problem. Oracle and MySQL both benefit monetarily from people assuming it will work and then activating it, only to find out a month or two later that it's a complicated problem that requires actual planning and oversight.

I think Postgres will be a better product when it incorporates similar functionality, but the implementations in MySQL and Oracle lie somewhere on the border between false advertising and reckless endangerment. I appreciate that Postgres not having it as two-lines of configuration sends a message that you are making a commitment. Nearly everything else in Postgres is set-it-and-forget-it. You really want to have a DBA if you're going to try to make replication work. When you read the docs on having a hot standby and how much of a commitment that is and sense yourself getting tired, you're starting to appreciate what you might be getting yourself into with single-master replication, let alone multi-master.

fusiongyro··on The sudden death and eternal life of Solaris
I dunno. I used it a little in college in the early 2000s, along with anything else I could get my hands on, and it seemed to me to be user hostile even by Unix standards. When I worked with Linux, *BSD etc. or Irix, things tended to make more sense.

It was difficult to get much experience with Solaris or the other commercial Unixes because you usually had to have particular hardware. Even when Solaris became free and ran on x86, it was picky about hardware. By then it seemed to me that even running BSD was kind of an uphill battle, if you wanted a VPS or something.

I'm not a completely neutral party. Sun totally botched a job interview process with me when I graduated, and I came away feeling that there must be a lot of internal confusion. Their public side certainly gave that impression too. I knew they had cool technology in Solaris, like dtrace and zones, but apart from the names you almost never saw someone who attributed their success to these technologies. And then of course Oracle and the slow death.

fusiongyro··on Harvard and the Making of the Unabomber (2000)
That's a fair point about the Koch brothers. I can't disagree with what you're saying here.
fusiongyro··on Harvard and the Making of the Unabomber (2000)
It doesn't seem to you like the right is increasingly reliant on shadowy conspiracies to explain events? I haven't heard the phrase "false flag operation" come up except from my infowars friends. A Republican chairman from my state said the violence in Charlottesville was caused by "evil Soros money," which seems to imply a conspiracy to me. Doesn't the whole "fake news" thing strike you as an attempt on the part of the right to brand the entire media a conspiracy, if not journalism itself?
fusiongyro··on 24/192 Music Downloads Are Very Silly Indeed (2012)
Interesting!
fusiongyro··on 24/192 Music Downloads Are Very Silly Indeed (2012)
I get what you're saying, that if you remove the ability to zoom you can equalize things, but without that twist I think this preserves the essential problem with the analogy that Monty works so hard to correct. If your data rate is too low, you don't have enough samples to recreate the waveform. So you create an approximate. But there is a finite number of samples that you need to recreate all of the information in the waveform, so once you have that, there isn't any additional information there for you to obtain if you continue to increase the sample rate.
fusiongyro··on 24/192 Music Downloads Are Very Silly Indeed (2012)
Basically, the sampling theorem says you can reconstruct the exact waveform with a certain number of samples. Adding a bunch more samples bulks up the file, but you didn't need them to restore the exact waveform. However, the unnecessary samples are in the file between you and the next sample you do need. At high enough levels of waste this creates an I/O bottleneck that hampers performance.

Another way to look at is that digital audio is not like digital imaging. There aren't pixels. Increasing the data rate does not continue to make the waveform more and more detailed to human auditory perception in the way that raising the pixel density does for human visual perception.

To describe it intuitively, forget your intuition that audio is like visual and start from "there is no metaphor between these two things."

fusiongyro··on Uber, Mired in Corporate Scandals, Sees Uptick in Bookings
They actually made a joke to this effect about Uber and Lyft on the last episode of Difficult People.
fusiongyro··on Rethinking the D-Bus Message Bus
There is quite a bit of technical documentation about our systems, and the code is supposed to be open-source (though a lot of it isn't publicly accessible as it should be). But I haven't written anything meant to be a high-level overview of how it works. I think I will try and do that in a few days and send you an email.

I have been joking about how we should build a "total sh*t array" out of old Dish/DirecTV antennas, so that we could explore the systems design without worrying too much about whether anything could be done with the data collected. This hasn't interested my coworkers that much :) There is an amateur radio astronomy society, and there are plans for how to build various levels of radio telescope, starting from ~$50 and an old Dish receiver and going up. And our open-skies policy means that you do not have to be a professional astronomer to use our instruments, although I only know of one or two amateurs that have proposed for time. (They did get it, though).

As a rough back-of-the-hand deal, we allow anybody who gets time to access about 25 MB/s of data. The correlator we have currently (WIDAR) can certainly output much more than that, up to gigabytes per second, but the rest of the infrastructure certainly can't keep up at that rate sustained. It's not unusual for an observation to top a few TB in size. ALMA data files are probably even larger on average.

We are already in the early design stage for a next-generation VLA, which will increase the number of antennas to about 300. At that point, we probably won't be able to keep correlated but unprocessed raw data, just because of the sheer size of it.

fusiongyro··on Rethinking the D-Bus Message Bus
We actually rely on multicast here at the NRAO for monitor and control of the VLA. I admit it's the only place I've heard of it being used.

ZeroMQ is getting used more for those kinds of purposes; the Greenbank Telescope uses it for one of their instrument backends and we are now using it for VLITE and REALfast. The new archive system I'm helping build uses AMQP.

fusiongyro··on R7RS Considered Unifier of Previous Standards (2015) [pdf]
Having a language defined by a standard is good if you can't have portable compilers/interpreters. Once your compiler is available on all the platforms you use, the utility seems to fall off a cliff.
fusiongyro··on R7RS Considered Unifier of Previous Standards (2015) [pdf]
Racket is a Scheme descendent, but it isn't exactly Scheme.

https://racket-lang.org/new-name.html

A lot of modern languages seem to eschew what they are derived from; Pharo isn't Smalltalk either, SWI-Prolog now defaults to a standards-incompatible mode, etc.

fusiongyro··on DR70 – A dedicated machine for astrologers
I think it would be interesting if it was like a special-purpose calculator for astronomy, that happened to have pointless astrology window dressing.

I also think it would be interesting, albeit in a totally different way, to know what "algorithms" they're up to in there, even though it's bullshit.

Definitely agree about their quackery.

fusiongyro··on DR70 – A dedicated machine for astrologers
Very curious find! I wonder what sort of calculations it's doing. Anything that would be useful to an astronomer? Or just weird bunko? Are the calculations deterministic?

There's a great book called Practical Astronomy with your Calculator; I wonder what the astrological analog would be.

fusiongyro··on Ask HN: What costly inefficiency do you see at work?
Mandated technology decisions. Strap in for a dozen man-years of technical debt on a platform your team doesn't understand but now must debug.
fusiongyro··on Why We Terminated Daily Stormer
I feel like you can see the problem with this line of reasoning if you finish that list you started there.
← PreviousPage 9 of 34Next →