Tip for learners: find an early edition of a book. They're often vastly cheaper and much better written. It stands that if a book warrants a 12th edition, then the 1st edition must have been decent enough to get wide adoption. Often revisions are bloat or, when they're not, it's educational to see the difference between then and now (eg Andre Tanenbaum's OS books)

Because I see so many people who believe otherwise, here's a direct quote from a prior contract:

> I UNDERSTAND AND ACKNOWLEDGE THAT MY EMPLOYMENT WITH THE COMPANY IS FOR NO SPECIFIED TERM AND CONSTITUTES "AT-WILL" EMPLOYMENT. I ALSO UNDERSTAND THAT ANY REPRESENTATION TO THE CONTRARY IS UNAUTHORIZED AND NOT VALID UNLESS SIGNED BY THE PRESIDENT OR CEO OF THE COMPANY. ACCORDINGLY, I ACKNOWLEDGE THAT MY EMPLOYMENT RELATIONSHIP MAY BE TERMINATED AT ANY TIME, WITH OR WITHOUT GOOD CAUSE OR FOR ANY OR NO CAUSE, AT MY OPTION OR AT THE OPTION OF THE COMPANY WITH OR WITHOUT ME NOTICE. I FURTHER ACKNOWLEDGE THAT THE COMPANY MAY MODIFY JOB TITLES, SALARIES, AND BENEFITS FROM TIME TO TIME AS IT IS NECESSARY.

Every job I ever held but the unionized ones had some variation of that.

Otherwise, in Fossil, any text is just another artifact. Wiki pages can be stored as files in the repo ("embedded") and versioned in the same manner as code files (that is, exposed through the same interface), or tracked behind the scenes (in a separate database, IIUC, with a different interface). Tickets and forum entries are also tracked and versioned similarly to non-embedded docs.

Aside from everything being versioned, the visibility of the objects is quite good. The user interface, both command and web, is light-years better than anything Git related.

I highly recommend you check it out. Even if you find it doesn't meet your needs, many of the design decisions are instructive. I find it quite inspiring.

I find this hard to believe. I searched the Fossil forums and found no mention of such an attempt (and failure). Unfortunately, I don't have a computer handy to verify or disprove. Is there any evidence for this claim?

I'll be honest, I don't understand your point here?

The purpose of Handmade Hero was to show people that they are capable of making a game themselves and to learn things which have a reputation for being too hard. There was, of course, an emphasis on the hard things being hard because of complexity introduced by things like OOP, C++, etc. But the main purpose always felt like education and enablement. Casey's a great teacher and the videos are very informative.

The Network, on the other hand, was some weird "we want to make stuff by hand", whatever that means. That's fine. But that's not what Casey spent like 7 years doing. He didn't do it "just cuz". Instead, it was to teach and share. That seemed lost on the Network.

As a result, it seemed just like a less toxic Suckless project without the focus on making a new ecosystem. It was just a forum to say, "Hey I made this thing", all the while co-oping the feel-goods from Casey's Handmade Hero.

Peaceful protest is the key. Riots, violence, and fighting are not peaceful and only play into the administration's aims.

When Americans resist and protest peacefully, as they have been in the largest numbers ever in the country's history, it exposes the brutality and baseness of those commiting the heinous acts.

Through such peaceful protest as we see, America will overcome this.

The big question is, what next? How to hold people accountable, fairly, while rebuilding the system and rebuilding trust?

Nonetheless, random access history is cool.

In this instance however, I agree, barf is more accurate.

Regarding how computers work under the hood, i can recommend Nand2Tetris.

https://www.nand2tetris.org/

Yes, it has an info manual and, I agree, info is the superior documentation viewer. However, a good browser is no replacement for bad writing.

The Guile manual is not well written. The organization seems almost random. The text emphasizes minutia while glossing over fundamental details. It off-loads much to RnRSs and SFRIs (whatever those are). Basically, it suffers badly from The Curse of Expertise.

The documentation's shortcomings might be okay except that Guile is, or was, the premier extension language for the whole of the GNU project.

I considered trying to improve the manual, but why would I dedicate time and effort to a language that I don't know and whose community can't follow it's own advice?

Consider the following:

"Make sure your manual is clear to a reader who knows nothing about the topic and reads it straight through. This means covering basic topics at the beginning, and advanced topics only later. This also means defining every specialized term when it is first used." https://www.gnu.org/prep/standards/html_node/GNU-Manuals.htm...

Most of these points: https://www.fsf.org/campaigns/gnu-press/GNU-Press-styleguide...

Maybe at FOSDEM this year, people could do a Hackathon and knock out some basics, like defining acronyms or using terms only after they're defined.

PS: every Python tarball for quite a while has instructions for building the documentation, including in info format

Is it some Viktor Frankl level acceptance or should I buy a copy of the Art of Electronics or what?

Advice welcome.

It just says "decades of neglect". It gives little vignettes of bad experiences and a quote from a French person saying the French would revolt.

Any actual explanation?