624 karma · joined February 21, 2014
It is? Do you have any supporting evidence for this claim?
I just had a look at a bunch of recent articles, and I would very much dispute it. I saw nothing extraordinary, and found the fonts they used rather ugly (though of course that is highly subjective). The use of bold face to highlight theorem/definition/etc. numbers is IMHO very questionable. The boldface letters you praise stick out like a sore thumb, feeling as if they were being emphasized and highlighted when they clearly are not meant to be.
files = split(read(`ls`, String))
firsttwo = files[1:2]
run(`ls -l $firsttwo`)
and this does the right thing even if you have a filename with spaces in it.
or thisI am also confused by what point you are trying to make regarding FTP? "Web devs wanted to upload files via FTP" sounds pretty normal for a website 15-20 years ago? Of course it also unclear when your story takes place...
The story in the README is also worth reading! E.g.
> At the time we wrote Appler we of course knew that the colors are supposed to be purple, blue, green, and orange, but we had never seen them displayed by an actual physical computer, because the Apple ][ displays that were available in Bulgaria were all monochrome-green. Alex looked at the schematics, and he used the actual resistor values of the DAC to calculate what the 4 primary colors should be.
WHAT??? Awesome
Interestingly, https://en.wikipedia.org/wiki/X86-64 says this:
> x86-64/AMD64 was solely developed by AMD. AMD holds patents on techniques used in AMD64; those patents must be licensed from AMD in order to implement AMD64
Also, Ninja by itself is not really a replacement for GNU make. Rather it's a tool one can build such a replacement on, so the comparison is a bit off to start with...
I don't use tig much otherwise, but for this purpose I've not yet seen a better (and faster!) tool.
That said, of course jargon often is als abused, or used in cases it doesn't have to be, etc. -- that's s bad! And many papers and books suffer from this and would be improved by using less jargon.
But in general I find this negative stance against formal notation, and the expectation that one should be able to dive into subtle and advanced examples without a need of at least some "studying" (not at all necessarily at a university!) quite odd, and unrealistic.
But note that OP uses larger cells (`int` = 32 bit in the C version, `Int` = 64 bit in the Julia version) while GalaxyBrain seems to use 8 bit cells. Not that I expect this to make a major difference (but perhaps a minor one?)
I use such a dongle a lot whenever I am presenting on conferences etc, and have been doing so for many years (even before the all-out for USB-C/Thunderbolt on MacBooks, there were no VGA ports, while many projectors still were; now I see a lot of HDMI, but still need the adaptor).
And I habe yet to have a single issue caused by that! Sure, damaged VGA cables and other weirdness, but never ever anything tracing back to the dongle.
In the same time I helped lots of people who struggled with their laptops with builtin VGA/HDMI Granted, usually not the laptops fault but rather PEBKAC / or people not knowing how to control Windows / Linux. Doesn't really matter: my point is that I see zero correlation between dongle usage and projector troubles.
So I firmly believe they used "sonst".