#thebook — Public Fediverse posts

‘The Art of the Crooked’: take what is not yours, then give what is not yours so you can take more of it. Rinse and repeat. ‘The Book’ was sold a long time ago and has had many forms. #TheBook #TheGreatLie #AbsoluteBeing #SecretKnowledge #Abuse #AbsoluteIdea #TheGreatSteal #TheArtOfTheCrooked #Philosophy #MythologicalBeing #SuperstitiousBeliefs #GriftersWorlds #TheDeathOfSocrates #Virtue #CrookedGods #TheSociety #TheRepublic #DialecticPrinciple #Foundation #TheFederation #AnEthicallySustainableLife ?

Brown university has re-written The Book to make some aspects of rust clearer. Reading their extensive chapter on ownership makes me wonder if I'm not *more* confused having read it!

More often that not, I find compiler messages tells me what I need to do to solve an ownership issue.

#rustlang #TheBook

@brh Melon's recent rants about Wikipedia elevated my regular paranoia level.
A selfhosted instance, even if it's not public, is like knowledge frozen in amber for me, not unlike #TheBook. That said, I'll grab IFixit, too 😁
I just wish there were more frequent updates to keep the library more up-to-date, but having 6-months old dumps is still better than nothing 🙂

Recently I stumbled over the book „Proofs from THE BOOK“ by Aigner and Ziegler. Being in a nerdy mood I had to buy it. The preface says that „.. a modest amount of technique from undergraduate mathematic“ is required. So I should be able to read this. If you‘re unaware of THE BOOK, read about https://en.wikipedia.org/wiki/Paul_Erd%C5%91s

#mathematics #math #thebook

[ THE BOOK. Manuale definitivo per la ricostruzione della civiltà. ]
https://www.the-book.it/ #TheBook

@twisterghost Did you see #rustlang's #TheBook?
https://doc.rust-lang.org/stable/book/

My code got met with nothing but #rustc #compiler warnings about mismatched types. That's rather off-putting, but also part of the learning process, seeing how I'm quite new to #rustlang.

So I spent hours trying variations and reading tutorials, articles, blog posts, and community discussions.

Hey, #rust documenters: it should be documented better! Preferably in #theBook, in the chapter that teaches how to handle #Results for recoverable errors.

Ad 1) Returning an #Error as part of a #Result.

This is a pattern I've been using in my #java #software #applications, instead of raising exceptions, for recoverable errors. Which is the same reason #rustlang uses it.

And #theBook goes into length to explain how to respond to and program against Results returned by the std::io library.

What it fails to show (thus far - have yet to read it all) is how to CREATE an Error.