The website moved from AsciiDoctor to OurBigBook Markup in 2020, making this section mostly useless. But hey, history!
Ciro's website is powered by GitHub Pages and Jekyll Asciidoc.
Build locally, watch for changes and rebuild automatically, and start a local server with:
git clone --recursive https://github.com/cirosantilli/cirosantilli.github.io
cd cirosantilli.github.io
bundle install
npm install
./run
Source: ./run.
The website will be visible at: localhost:4000.
Tested on the latest Ubuntu.
Publish changes to GitHub Pages:
git add -u
git commit -m 'make yourself look sillier'
./publish
Source: ./publish.
GitHub forces us to use the master branch for the build output... so the actual source is in the branch dev.
Update the gems with:
bundle update
git add Gemfile.lock
git commit -m 'update gems'
His website was originally written in markdown, however those were deprecated in favour of AsciiDoctor when Ciro saw the light, rationale shown at: markdown-style-guideuse-asciidoc
This is how Ciro Santilli evaluates himself on the Big Five personality traits:
Give students answers to all questions.
Explain in extreme detail how each result was reached.
Students have the amazing capacity of not looking at answers if they don't want to.
And when they've had enough, then can read answers and understand while the problem is fresh in their minds.
If you don't give answers, no one will be able to use your online material without you being there to hold their hands.
Forbidding students from publishing their answers also goes against let students learn by teaching.
2021-08 bedroom battery out, 7.29V out of 9V duracell duralock. Buying pack of 12 Energizer nine-volt batteries. Measurement on new battery: 9.68V.
Price fixing would require every single company selling something to cooperate. And if they do, another person sick of them can start a new company and undercut them. Price fixing would also destroy any goodwill towards these companies and many customers wouldn't patronize them even if they lowered their prices again.
Yes, most of the very rich have acquired their wealth through unfair means, be it through unfair government action like intellectual property, subsidies, bailouts, low-interest loans, etc., or violence, historic or current. Regarding pure socialism/communism, a war to fully redistribute the riches of the wealthy will likely never happen, and cause great devastation if it did.
In a libertarian system, even if everyone started out equally wealthy, some would end up richer than others, as people of differening competency and diligence should. But libertarianism makes things fair even if some are very wealthy.
One who owns a lot of resources can rent or loan it to others without much additional cost to themselves, and make a percentage return. But by making them compete with other rich people, assuming resources are plenty, the ones that offers it for the lowest price, ie., makes the closest to zero profit, will get all the customers.
As for why even partial wealth redistribution isn't preferred in a libertarian society, note that the company that provides the customer with the most value for their money wins. The riches of a wealthy person are assets to be used to finance their business, even if turned into houses or jewelery, since they can be liquidated when needed. Taking these away punishes the best company, which is counter-productive. If a lot of it is turned into stuff like parties and luxury vacations, the company isn't being very efficient, and will likely be replaced quickly in a free market. If not, that means people who can afford it are willingly transferring their money by overpaying due to their affinity for the entity, in which case libertarians would argue they have every right to spend that fairly earned money.

Pinned article: Introduction to the OurBigBook Project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 2.
    You can publish local OurBigBook lightweight markup files to either https://OurBigBook.com or as a static website
    .
    Figure 3.
    Visual Studio Code extension installation
    .
    Figure 4.
    Visual Studio Code extension tree navigation
    .
    Figure 5.
    Web editor
    . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
    Video 4.
    OurBigBook Visual Studio Code extension editing and navigation demo
    . Source.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact