Software toy by Ciro Santilli 35 Updated +Created
Ciro Santilli's TODO there:
Open source video game by Ciro Santilli 35 Updated +Created
Why would anyone ever waste time playing a closed source game, when this will inevitably lead to endless hours of decompilation down the line when you want to:
Those who devote their time to the useless development of open source video games, before we even have decent open source development tooling, will, without a doubt, have their place in Heaven.
Video game console company by Ciro Santilli 35 Updated +Created
Pokemon by Ciro Santilli 35 Updated +Created
One of the main children cartoons Ciro Santilli liked to watch. Part of the Pokemon Mania of the 90s of course.
Ciro could not understand why Nintendo won't make a proper 3D MMORPG Pokemon with actually 3D Pokemon roaming the land, which is obviously what everyone wants. There are even fan games getting there!
until this explaiend it beautifully Video 1. "The Downfall Of Mainline Pokemon Games by GONZ media (2020)":
Figure 1.
Instead of risking anything new, let's play it safe by continuing our slow decline into obsolecense cartoon by Tom Fishburne
. Source.
Video 1.
The Downfall Of Mainline Pokemon Games by GONZ media (2020)
Source. Great video, explains things Ciro had never thought about, e.g. how the Nintendo Switch unified handheld and console for Nintento, this could open the doors for a more ambitious Pokemon release.
Super Mario by Ciro Santilli 35 Updated +Created
Quantum computer type by Ciro Santilli 35 Updated +Created
The Legend of Zelda by Ciro Santilli 35 Updated +Created
Particle in a box by Ciro Santilli 35 Updated +Created
Quantum computing outreach by Ciro Santilli 35 Updated +Created
The Legend of Zelda game by Ciro Santilli 35 Updated +Created
The Legend of Zelda: Ocarina of Time by Ciro Santilli 35 Updated +Created
This game was mind blowing to Ciro Santilli and all kids. It felt so real. The perfect contrast between peaceful town work and saving the world. OMG.
Super Nintendo Entertainment System by Ciro Santilli 35 Updated +Created
Bra-ket notation by Ciro Santilli 35 Updated +Created
Notation used in quantum mechanics.
Ket is just a vector. Though generally in the context of quantum mechanics, this is an infinite dimensional vector in a Hilbert space like .
Bra is just the dual vector corresponding to a ket, or in other words projection linear operator, i.e. a linear function which can act on a given vector and returns a single complex number. Also known as... dot product.
For example:
is basically a fancy way of saying:
that is: we are taking the projection of along the direction. Note that in the ordinary dot product notation however, we don't differentiate as clearly what is a vector and what is an operator, while the bra-ket notation makes it clear.
The projection operator is completely specified by the vector that we are projecting it on. This is why the bracket notation makes sense.
It also has the merit of clearly differentiating vectors from operators. E.g. it is not very clear in that is an operator and is a vector, except due to the relative position to the dot. This is especially bad when we start manipulating operators by themselves without vectors.
This notation is widely used in quantum mechanics because calculating the probability of getting a certain outcome for an experiment is calculated by taking the projection of a state on one an eigenvalue basis vector as explained at: Section "Mathematical formulation of quantum mechanics".
Making the projection operator "look like a thing" (the bra) is nice because we can add and multiply them much like we can for vectors (they also form a vector space), e.g.:
just means taking the projection along the direction.
Ciro Santilli thinks that this notation is a bit over-engineered. Notably the bra's are just vectors, which we should just write as usual with ... the bra thing makes it look scarier than it needs to be. And then we should just find a different notation for the projection part.
Maybe Dirac chose it because of the appeal of the women's piece of clothing: bra, in an irresistible call from British humour.
But in any case, alas, we are now stuck with it.
Nintendo 64 by Ciro Santilli 35 Updated +Created
This is the one that hit Ciro Santilli the hardest, coming in at the point in which he started to discern between games and the real world a little better. His parents bought it for him during a trip to Disney World in Florida in 1996 (?), since electronics were much cheaper in the USA.
So as Ciro became older, and turned into a software engineer, he started to become more and more morbidly curious about "N64 internals": tool-assisted speedrun, how the devkit looks like, how games were developed for it, hardware leaks, etc.
Luckily Ciro's mind is not interested enough by that useless shit for Ciro to seriously study it himself. But that's what YouTube is for, right? Why do useless stuff when other more useless people can do it for you?
The console has only 4 MB of RAM memory. It is quite incredible what can be done with 8 MB, from the point of view of a 2020 worls where 16 GB laptops are the norm.
Mupen64Plus by Ciro Santilli 35 Updated +Created

Pinned article: ourbigbook/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 5. . 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.
  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