ebuku VS web

Another option is to use something like ebuku.

i remember looking at that Google style guide a while back, and not being enthused about it. It's true my style across my POSIX scripts isn't yet entirely consistent, as i'm new to writing POSIX shell scripts, and am still working out what's best for me, as the person who's going to be the primary maintainer. Still, i believe my style to be basically consistent within a given script. Having been programming for a few decades now - although i only started coding-for-pay in the late 90s, starting with Perl - i've developed my own preferences regarding code layout (such as in my ELisp packages, e.g. Ebuku), and nowadays take the approach: I'll follow others' style in others' projects, and will generally try to follow common style standards in my own projects, but will modify them as needed when i find they're not conducive to my work.

Well, indeed, i certainly wasn't expecting you to do so! But i already have more than enough volunteer FOSS stuff on my plate as it is (e.g. Ebuku, pulseaudio-control, s6-man-pages, execline-man-pages and guides, amongst various other things), and not using mold with gcc 11 is no problem for me at this point. So i've just noted the issue with the patch on the wiki page, and the patch will have to be updated by someone for whom it's more important.

Fair point. Still, as a FOSS dev myself, i feel that the title might serve as a useful reminder to a number of their readers. Particularly when so many people use FOSS developed by large corporations, and see themselves as 'customers' entitled to 'responsive service'[a] that those of us who aren't a corporation aren't necessarily in a position to provide (even if we do try to provide 'best effort'). The contents of the screencap for one of my FOSS projects is not random. :-)

Based on your post headline, i was going to suggest my Ebuku package, an Emacs frontend to the buku Web bookmark manager - i use it myself, and it has support for both tags and comments on links. But it doesn't meet your requirement of capturing from the browser; i copy-and-paste the URL from the browser into an Emacs prompt.

Me asking for actual data about the the extent to which various arguments to the -O flag is me "trying to argue with you" and "having a bad day"? Er, what? i'm saying your assertions might well be correct, but as a dev myself (here's some of the stuff i've been doing during our exchange), i want some concrete data in support of this, because "premature optimisation is the root of all evil" (cf. "Rob Pike's 5 Rules of Programming").

Not beyond playing around a bit with Squeak. i like Smalltalk's message-passing approach to OO, and i like how thoroughly modifiable the environment is. i haven't spent enough time to know how easily it can interface with the system on which the image is running; one of the things i like about Emacs is that, in addition to being so modifiable itself, it provides lots of support for interacting with software outside of itself. (E.g. i wrote an Emacs package which provides an Emacs UI for the CLI-based buku Web bookmark manager: Ebuku.)

Sure, at some point you're going to be relying on some 3rd party somewhere. We use a VPS and not a bare-metal hand-installed rack, and we rely on an electrical company and not a hand-turned crank to power our servers. As far as email goes, It's simply not possible to self-host transactional email in 2024 if you want it to arrive in an inbox and not a permanent spam blackhole; likewise it's not possible to accept money without involving a 3rd party service like Fractured Atlas or Stripe or PayPal. (Moving away from GitHub towards a self-hosted Git solution is actually on our long-term todo list[1]).

All those things doesn't mean you can't run your web app on a single tiny server, and that outsourcing the basic underpinnings of your web app, like the OS, runtime, and database to some cloud service, or that resorting to flavor-of-the-month frameworks or containers, will result in complexity and bloat.

[1] https://github.com/standardebooks/web/blob/master/README.md#...

Hey a little later to the party here but I'm really enjoying this. I started reading a book with it and while I agree with others it's not great for grammar it certainly shows me many new words without requiring me to read at a glacial pace.

PS: You should def try to include some books from https://standardebooks.org/ which are much nicer formatted than the ones you're using from Project Gutenberg.

Good luck and I hope you can keep building this out. Already the update to tap anywhere to close the word definition is a nice improvement :)

A number of e-book platforms are discussed on my blog, which dives deeply into the technical nuances of typesetting a few[1]. Ultimately, I typeset a classic from Standard EBooks[2], Dr. Jekyll and Mister Hyde[3].

[1]: https://dave.autonoma.ca/blog/2020/04/11/project-gutenberg-p...

[2]: https://standardebooks.org/

[3]: https://dave.autonoma.ca/blog/2020/04/28/typesetting-markdow...

As an aside, for anyone looking for free classic books to read on their various eReaders, these are very well done: https://standardebooks.org

It is the same when you download a kepub book from standardebooks.org. You will have the epub file with kepub features.

> https://standardebooks.org/

Standard Ebooks is seriously impressive. One of my favorite sources of books in the public domain.

I’d also add in addition to this excellent list of DRM-free ebooks, it’s always worth looking into borrowing a book from the library via Libby/Overdrive.