So my town had a royally approved rabbit hunter --- who was also a butcher. He was the best butcher in the town.
Unrelated, but we also had a separate fruiterer, who procured fruits. I have never seen someone called a fruiterer anywhere else.
1,485 karma · joined January 11, 2015
I'm a mathematician and software developer. Now I work with libraries (as in books, not as in software --- though I do software for the libraries) in many varied ways.
So my town had a royally approved rabbit hunter --- who was also a butcher. He was the best butcher in the town.
Unrelated, but we also had a separate fruiterer, who procured fruits. I have never seen someone called a fruiterer anywhere else.
The more I work with people using accessibility tools, the more I realize that web accessibility is an afterthought (if thought about at all).
[1]: https://davidvujic.blogspot.com/2022/08/joyful-python-with-r...
I guess this means that I'm reducing the signal they get for what "good" email is, as approximately 100 percent of the emails I get there are promotional or spam.
There is a certain organizational aspect here that I think is important to emphasize: the given paradigm is that vim is a text editor forming one part of the design environment. Assembling this environment inside a tmux session is particularly easy and powerful. And plugins can add some quality of life.
In addition, I also like the vim-slime plugin. All this does is facilitate sending lines/regions/blocks to a REPL (or in principle, any tmux pane). It's similar to the tmux send-keys function described in the OP.
A different paradigm of vim use is growing in popularity, which is the transform vim into a full IDE on its own.
A few years ago I learned that one can also add a new section to man. I've added the `eg` section, which I fill with examples that I think will be useful to future me. For example, typing `man eg awk` opens up my man page of examples for awk, which is more pointed.
[1]: https://en.wikipedia.org/wiki/Abramowitz_and_Stegun [2]: https://www.cs.bham.ac.uk/~aps/research/projects/as/
I didn't write a better stockfish or anything, but I was surprised that it didn't take too long to write a chess engine that could routinely beat me at chess.
I'll also note that chess protocals are very standardized, and it was straightforward to attach the engine to one of the many chess GUIs out there (I used Chess Arena and scid). This was a great project and I highly recommend it.
Too bad!
I also only send plaintext email. This sounds like it should be easier than sending HTML, but many mobile email clients only send HTML or "rich emails". This includes the gmail! (This used to be possible in earlier versions of google's phone email apps. Maybe it was Inbox? I don't remember now. But being unable to send plaintext email from gmail on mobile is what caused me to move away from gmail).
Now I use mutt on my own computer, K9 on mobile, and if absolutely necessary Roundcube webmail. (I do not particularly like Roundcube, but I almost never actually have to use it).
Mutt is wonderful, though I found it highly nontrivial to initially use. K9 is fine. One feature of K9 I like is that it has a surprisingly capable search capability given that I use it purely over IMAP --- it dispatches a search to my mail server and parses the results.
I don't think this is a suitable replacement for an email app. For example, this is an extremely inconvenient way to check email, and having to use a different process to check and read email is too much friction. But this does seem like a workaround to send a plaintext email.
That's what started my migration away from google.
Having said that, K9 is fine. It's good enough that I'm not looking for a replacement.
> What is the single most important factor that has prevented the arXiv to quickly innovate? We believe it is LaTeX. The same technological advancement that has allowed the arXiv to flourish, is also, incredibly, its most important shortcoming. Indeed, the reliance of the arXiv on LaTeX is the source of all the weaknesses listed below.
> The research products hosted by the arXiv are PDFs. A title, abstract, and author list are provided by the authors upon submission as metadata, which is posted alongside the PDF, and is rendered in HTML to aid article discoverability.
It's interesting to me that the authors ignore that it is possible to read the source tex for most papers on the arxiv. The arxiv prefers to be given tex and source files, and then to compile and serve the pdf --- when this is done, you can read the source. In this way the arxiv is a repository of both the plain text source of the document and a formatted output.
In some of my papers, I deliberately include comments or extra data in the source for others. I'm not alone here; I've used the code embedded in this paper [1], for example.
While I think there would be some advantages if the arxiv required all papers to be compilable tex source files, I understand that the arxiv also accepts other formats to not exclude potential writers who do not know tex. [The other formats are pdfs (e.g. converted from Word) or HTML with jpg/png/gif images (which I have never seen in practice)].
I'm very curious how much better the system would perform if the flywheel were attached directly to the drive-train instead of via friction roller. In practice this might not give much higher efficiency, but I would guess that the chain and primary sprocket would wear out slower than a tire friction-running a flywheel.
(They mention that they don't do this because this because it would be harder to build. I believe that. But I'm still curious.)