65,359 karma · joined June 19, 2010
Previous lives:
gnu hacker (e.g. co-founder of Cygnus back in '89) Pharma developer (Talima) Distributed solar thermal systems (Terrajoule) MIT AI Lab/PARC/MCC/Rodin consumer tabletop AR (CastAR) Etc...
remove-everything-up-through-last-dash-gumby@brachiate.org
Now the resources can be scheduled in a very complex, out of order, and subinstruction fashion. The chip designers guess what the instruction mix will likely be and hopefully make the right call as to how many Xs are required and how many Ys. Too few and operations in flight will wait. Too many and the chip becomes more complex for no benefit, and maybe those unused resources crowd out space for something else useful.
If you stick an ALU on every register you’re guaranteeing to use some area on something not used all the time.
There's a photo in that article that shows the problem: the flip-tab sign that has space for four numerical digits. I was thinking they could just switch from 0-9 to 0-9A-Z but that photo showed why that would be a disaster.
Plus any solution has to be approved for use worldwide.
Fortunately the two-digit IATA codes have already switched to 0-9A-Z (e.g. JetBlue is B6) so allowing constrained airlines to use two codes should work fine.
I don’t understand why your comment was being voted down.
I’m sure ideological archeology can solve that though. That path also has a lot of history.
Well, that’s in the eye of the beholder. Yes, I hate the ‘program command’ syntax (“git add”, “git commit” etc) but I just call git-add etc and for me those commands are pretty clear.
But I understand how git works. I imagine most people treat it as a black box and then its behavior probably is rather obscure. I don’t think it was intended for that use case.
It requires a level of trust and a level of performance, that I now believe doesn’t scale. Note that we had only a single junior developer, an intern, who wrote our bug tracking system but didn’t otherwise interact with the code base. The rest of the team consisted entirely of experienced senior developers, including management. I think at up to about 25 employees, the shortest working experience on the team (apart from the intern) might have been 10 years of shipping code.
But I really respect Rich for taking this approach which is why I referred to him by name.
Git is still a baby as these things go. Software version control systems go back to the early 1960s and descended from manual processes used to manage documents in large organizations, blueprints, and such from the early 20th century. Don’t imagine the Manhattan Project functioned by just passing around bundles of paper! There were staffs of people whose job was to manage document control! And I don’t mean “control” in the sense of secrecy, but making sure everybody was on the the same revision at the same time.
And for a field so steeped in building its own tools and automating human effort in development it is indeed astonishing revision control took so long to be accepted.
IMHO he was overgenerous on the optimization improvement of compilers. Often an optimization will make a difference in a tiny fraction of a percent. The value comes from how often that optimization can be applied, and how lots of optimizations can in aggregate make a bigger improvement just as a sand dune is made of tiny grains of sand.
A big chunk of the essay is about a side point — how good the gains of optimization might be, which, even with data, would be a use-case dependent decision.
But the bulk of his complaint is that C compilers fail to take into account semantics that cannot be expressed in the language. Wow, shocker!
At the very end he says “use a language which can express the needed semantics”. The entire essay could have been replaced with that sentence.
Around 1991 when Cygnus had 6-7 employees and was based in the apartment complex where I lived, none of the GNU codebase was hosted in any sort of revision control. Everything was FTPed around as obscurely named tarballs. We had gathered something like 27 different forks of gdb floating around the net, for example. This was back when forking was generally considered a tragedy, something I managed to change five or six years later).
Rich Pixley came and said “all of our code should be in revision control, and I want to use this newfangled thing called CVS.” Michael was OK with it but John and I were steadfastly opposed. We agreed to an experiment, grudgingly, subject to a whole whiteboard of absurd conditions (“must be transparently integrated into emacs so we don’t have to know it’s there).
Pixley agreed to all of that and then ignored all of it completely. It was immediately such a win that everybody adopted it without complaint, including us two obstreperous a-holes.
A few years later a preventable crisis was how revision control first became client-server.
But that’s what the article is calling for — claiming (correctly IMHO) that the C interface is pretty cruddy.
Unfortunately whichever higher level interface you choose will be inappropriate for most languages that aren’t the implementation language. I didn’t mention the 432 by accident: its baked in “object-oriented” architecture turned out not only not to help but instead slowed down the whole processor for no gain.
The only exception is when only one language is intended and there’s a tight coupling between silicon and that language (e.g. the lispm case).
Just suck it up and put the OS interface (with the appropriate paradigms and affordances for your language) into your language’s standard runtime. That’s part of the work of writing a language.
Whatever model you think should replace it will inevitably only be useful for some languages and as bad as a C interface (or worse) for others. The iAPX 432 was a notorious example — in hardware! Lispms, sadly, were another.
It is irksome that some will consider C the “lowest common denominator”. It ain’t. It’s just a shitty, path-dependent valley in the possibility space. And as for shitty, well, I use the toilet every day, and it’s not the high point of my day, but it’s where we ended up (so far) as part of the mechanism by which we power our bodies and also get to enjoy yummies. No point I’m complaining about it, it simply is what it is.
I strongly disagree with your statement. in fact the two sentences you quoted are quite clear. They aren’t written for a lay audience, true, but you don’t expect such in Cell. They don’t use any jargon at all.
Your own comment is also clear, but you wear your allegiance on your sleeve. The two sentences you quote make it clear that the paper is about people not technology — and wouldn’t even call the paper itself “AI skeptical”.
You may well be right that “AI skeptics will wildly cite this paper on social media”. But that is orthogonal to the paper itself.
I thought the whole point of the Marines was to cause maximal amounts of damage. Are you implying there is a constraint on that?
But now I understand why the marines hate the navy: I had a buddy who'd been in the navy and he said they kept the kids busy by cleaning and painting everything but frequently they'd let 'em blow off steam by tossing cardboard boxes and stuff off the end the flight deck and shooting at them with the 50 cal machine guns.
We were good friends, attended MIT together, but if I thought the Navy would take many people like him I'd doubt their ability to fight a war. He was only in the navy because it would pay for school and AFAIK he managed to avoid getting any rank advancement at all. MIT requires, or used to, a lot of all nighters and he once said "I'm probably only sane with these all nighters because I did so much extra sleeping in the navy"
I think the real fix is secure enclaves, and those have proven to be difficult as well.
Some other languages. Just considering the Latin alphabet: French pronunciation is so far from spelling that spelling bees used to be (may still be) prime time television. Words in Spanish and Portuguese may be written in a deterministic fashion, yet pronounced quite differently in different countries.
And sure, German spelling does reflect pronunciation…because the spelling has been changed from time to time to match shifts in pronunciation…specifically the pronunciation used by a small number of people in Niedersachsen. Elsewhere in Germany (much less Switzerland) the local pronunciation can be incomprehensible. (This was the case in the UK and France until the advent of radio and then especially TV).
And that’s just four examples using basically the same alphabet. This phenomenon is common to all living languages. Even dead languages, for that matter: the Latin and (classical) Greek pronunciation I had to use in high school was a UK version different from that typically used in the USA or (based on one person I met), Sweden!
And do you really think the same thing doesn’t happen with Arabic, Hindi et al?
English ain’t so special.
IME he hates to revisit anything he's already written so this claim is polite but implausible.
$ echo 'int main(){return 42;}' > a.c; make a && ./a; echo $?Obviously that doesn’t scale, but for a beginner it’s simple.