New articles - OurBigBook.com

, which is quite little information! This idea is basically what is behind the importance of the ralationship between Lie group-Lie algebra correspondence via the exponential map. In the more general settings of groups and manifolds, restricting ourselves to be near the origin is a huge advantage.

Now suppose that we want to calculate

e^{1}

. The idea is to start from

e^{0}

and then then to use the first order of the Taylor series to extend the known value of

e^{0}

e^{1}

E.g., if we split into 2 parts, we know that:

e^{1} = e^{1/2} e^{1/2}

(3)

or in three parts:

e^{1} = e^{1/3} e^{1/3} e^{1/3}

(4)

so we can just use arbitrarily many parts

e^{1/ n}

that are arbitrarily close to

x = 0

e^{1} = (e^{1/ n})^{n}

(5)

and more generally for any

x

we have:

e^{x} = (e^{x / n})^{n}

(6)

Let's see what happens with the Taylor series. We have near

y = 0

in little-o notation:

e^{y} = 1 + y + o (y)

(7)

Therefore, for

y = x / n

, which is near

y = 0

for any fixed

x

e^{x / n} = 1 + x / n + o (1/ n)

(8)

and therefore:

e^{x} = (e^{x / n})^{n} = (1 + x / n + o (1/ n))^{n}

(9)

which is basically the formula tha we wanted. We just have to convince ourselves that at

lim_{n \to \infty}

, the

o (1/ n)

disappears, i.e.:

(1 + x / n + o (1/ n))^{n} = (1 + x / n)^{n}

(10)

To do that, let's multiply

e^{y}

by itself once:

e^{y} e^{y} = (1 + y + o (y)) (1 + y + o (y)) = 1 + 2 y + o (y)

(11)

and multiplying a third time:

e^{y} e^{y} e^{y} = (1 + 2 y + o (y)) (1 + y + o (y)) = 1 + 3 y + o (y)

(12)

TODO conclude.

 Read the full article

Cangue by

Ciro Santilli 40 Updated 2025-07-16

 Read the full article

Crucifixion by

Ciro Santilli 40 Updated 2025-07-16

 Read the full article

Kin punishment by

Ciro Santilli 40 Updated 2025-07-16

 Read the full article

Theft by

Ciro Santilli 40 Updated 2025-07-16

 Read the full article

Censorship by

Ciro Santilli 40 Updated 2025-07-16

 View more

The opposite of freedom of speech.

For censorship in China see: cirosantilli.com/china-dictatorship/censorship

 Read the full article

Police by

Ciro Santilli 40 Updated 2025-07-16

 Read the full article

Ciro Santilli 40 Updated 2025-07-16

 Read the full article

Derivative work by

Ciro Santilli 40 Updated 2025-07-16

 Read the full article

Freedom of panorama by

Ciro Santilli 40 Updated 2025-07-16

 Read the full article

Creative Commons license by

Ciro Santilli 40 Updated 2025-07-16

 Read the full article

CC BY version by

Ciro Santilli 40 Updated 2025-07-16

 Read the full article

CC BY 3.0 by

Ciro Santilli 40 Updated 2025-07-16

 Read the full article

CC BY-SA by

Ciro Santilli 40 Updated 2025-07-16

 View more

This one strikes the right balance between restriction and permissions. NC and ND are simply too restrictive.

TODO where does the SA boundary end? E.g.:

Does source code need to be redistributed: opensource.stackexchange.com/questions/1849/does-the-cc-by-sa-license-require-that-source-code-of-derivative-works-be-shared

Case law list on the CC wiki: wiki.creativecommons.org/wiki/Category:Case_Law

 Read the full article

CC BY-NC-SA by

Ciro Santilli 40 Updated 2025-07-16

 View more

Too restrictive. People should be able to make money from stuff.

The definition of "commercial" could also be taken in extremely broad senses, making serious reuse risky in many applications.

Notably, many university courses use it, notably MIT OpenCourseWare. Ciro wonders if it is because academics are wary of industry, or if they want to make money from it themselves. This reminds Ciro of a documentary he watched about the origins of one an early web browsers in some American university. And then that university wanted to retain copyright to make money from it. But the PhDs made a separate company nonetheless. And someone from the company rightly said something along the lines of:

The goal of universities is to help create companies and to give back to society like that. Not to try and make money from inventions.

TODO source.

The GNU project does not like it either www.gnu.org/licenses/license-list.en.html#CC-BY-NC:

This license does not qualify as free, because there are restrictions on charging money for copies. Thus, we recommend you do not use this license for documentation.
In addition, it has a drawback for any sort of work: when a modified version has many authors, in practice getting permission for commercial use from all of them would become infeasible.

en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license#Defining_%22Noncommercial%22 also talks about the obvious confusion this generates: nobody can agree what counts as commercial or not!

In September 2009 Creative Commons published a report titled, "Defining 'Noncommercial'". The report featured survey data, analysis, and expert opinions on what "noncommercial" means, how it applied to contemporary media, and how people who share media interpret the term. The report found that in some aspects there was public agreement on the meaning of "noncommercial", but for other aspects, there is wide variation in expectation of what the term means.

 Read the full article

 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!

Video 1.

Intro to OurBigBook

. Source.

We have two killer features:

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
Video 2.
OurBigBook Web topics demo
. Source.
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:
- to OurBigBook.com to get awesome multi-user features like topics and likes
- as HTML files to a static website, which you can host yourself for free on many external providers like GitHub Pages, and remain in full control
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.
Internal cross file references done right:
Infinitely deep tables of contents:
Figure 6.
Dynamic article tree with infinitely deep table of contents
.
Live URL: ourbigbook.com/cirosantilli/chordate
Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade