Experiment Updated 2025-07-16
Physics research institute by country Updated 2025-07-16
Quote Investigator Updated 2025-07-16
Simplicity is the ultimate sophistication Updated 2025-07-16
By Da Vinci: www.goodreads.com/quotes/9010638-simplicity-is-the-ultimate-sophistication-when-once-you-have-tasted
There are infinitely many variants across the ages:
- by Blaise Pascal
- by Albert Einstein
Make everything as simple as possible, but no simpler
- by Antoine de Saint-Exupéry
Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away
- KISS principle
Sponsor Ciro Santilli's work on OurBigBook.com Why you should give money to Ciro Santilli Updated 2025-07-16
So that he can work full time on OurBigBook.com and revolutionize advanced university-level science, technology, engineering, and mathematics eduction for all ages.
Donating to Ciro is the most effective donation per dollar that you can make to:
- improve hardcore university-level STEM education for all ages
- help make every child into the next Nobel Prize/Fields Medal/deep tech unicorn co-founder
Ciro's goal in life is to help kids as young as possible to reach, and the push, the frontiers of natural sciences human knowledge, linking it to applications that might be the the next big thing as early as possible. Because nothing is more motivating to students than that feeling of:rather than repeating the same crap that everyone is already learning.
To do this, Ciro wants to work in parallel both on:
- the multi-user website e-learning platform of OurBigBook.com
- creating amazing teaching content that motivates that platform, and that deeply interests Ciro, notably quantum mechanics and its related applications:
- quantum computing
- molecular biology
- condensed matter physics and chemistry
- slightly more theoretical stuff in somewhat related fields of:
- continue to dump his brain/research in areas Ciro has expertise in: software engineering and open source software
Ciro believes that this rare combination of both:produces a virtuous circle, because Ciro:
- proven passion and capability to learn and teach science, technology, engineering, and mathematics subjects
- proven programming skills, including web development
- wants to learn and teach, so he starts to create content
- then he notices the teaching tools are crap
- and since he has the ability to actually improve them, he does
As explained at OurBigBook.com and high flying bird scientist, Ciro is most excited to make contributions at the "missing middle level of specialization" that lies around later undergrad and lower grad education:in a way that is:
But on that middle sweet spot, Ciro believes that something can be done, in such as way that delivers:
- beauty
- power
- in your face, without requiring you to study for a year
- but also giving enough precision to allow you to truly appreciate the beauty of the subjectCiro's programming skills can also be used to create educational, or actually more production-like, simulations and illustrations.
Ciro believes that today's society just keep saying over and over: "STEM is good", "STEM is good", "STEM is good" as a religious mantra, but fails miserably at providing free learning material and interaction opportunities for people to actually learn it at a deep enough level to truly appreciate why "STEM is good". This is what he wants to fix.
The following quote is ripped from Gwern Branwen's Patreon page, and it perfectly synthesizes how Ciro feels as well:
In addition to all of this, financial support also helps Ciro continue his general community support activities:
- writing and updating his amazing Stack Overflow answers: Section "Ciro Santilli's Stack Overflow contributions"
- saving the world from the CCP: Section "Ciro Santilli's campaign for freedom of speech in China"
Blog Updated 2025-07-16
Endurance sport Updated 2025-07-16
List of sports Updated 2025-07-16
Lists of mathematical problems Updated 2025-07-16
Mailing list Updated 2025-07-16
The only explanation is that the dinosaurs who created the projects are unable to adapt to new superior technologies.
Yes, Ciro is talking to you, big fundamental projects from last century: Linux kernel, GNU Compiler Collection (gcc.gnu.org/lists.html), Binutils (sourceware.org/binutils/), etc.
Some of you are already using Bugzilla for the bugs, so kudos. But if you've seen their benefit, why you still use the mailing list for patches?
Advantages of mailing lists:
- threaded replies, which almost no issue tracker has. GitHub feature request: github.com/isaacs/github/issues/837
Disadvantages: everything else:
- cannot subscribed to a single thread. Which forces you to create an email filter for each one of them you subscribe to.
- no metadata, notably the notion of closing / merging, but also upvotesYou have to read thirty messages before you can know if the bug was solved or not.
- it is insanely hard to reply to messages from before you were subscribed: webapps.stackexchange.com/questions/23197/reply-to-mailman-archived-message/115088#115088
- hard to apply patches locally to test them out: stackoverflow.com/questions/5062389/how-to-use-git-am-to-apply-patches-from-email-messages/49082916#49082916Unless they use Patchwork, which adds one more website on top of the mess.And then Gmail corrupts your patches, and you are forced to use
git send-email, which does not work on some network configurations: stackoverflow.com/questions/28038662/how-to-solve-unable-to-initialize-smtp-properly-when-using-using-git-send-ema or setup ThunderBird. - often have to subscribe to post at all, thus cluttering your inbox further
- you can edit posts to make them clearer.Yes, people could vandalize their answers when they get mad, and threads might stop making sense after edits. But this can be solved with an undeletable post history like Stack Overflow has (but not any other tracker does).Or archive.org :-)In any case, what do you think will happen more often and have greater impact:
- people vandalize their posts
- people fix their silly typos and improve content
- searchable by author, keyword, etc. without Google. Yes, mailing list trackers could have decent implementations to overcome that. But no, GNU Mailman which everyone uses does not have it. Google barely indexes it.
- people have to learn about top posting vs inline posting, and this requires infinite education of new users
- On mailing lists: either put a comment in the middle of a huge patch and let other people find it, or (more likely) copy paste the part of the patch that you are talking about.
- most mail web UIs suck.OK, this is not an unsolvable or intrinsic problem, but still a problem.E.g.:
ezmlmit is not possible to see the entire content in a single page: gcc.gnu.org/ml/gcc/2015-07/threads.html.The alternative: do like LLVM and send attachments. Yes, I we all love opening up attachments on our browsers.The real solution: everyone can create branches and pull requests. Also has the benefit of running CI on the pull requests.
Not sure:
- you can have infinitely many trackers to replicate data in case apocalypse happens in some part of the world.Although I'm not sure this is an advantage, as you don't know anymore which one is the canonical trackers an advantage, as you don't know anymore which one is the canonical tracker.And all web interfaces already have an API to export messages, and someone has already scripted it to import from any web UI to any web UI for you.
Online marketplace Updated 2025-07-16
Review site Updated 2025-07-16
Git tips
diff3 Updated 2025-07-16diff3 conflict is basically what you always want to see, either by setting it as the default as per stackoverflow.com/questions/27417656/should-diff3-be-default-conflictstyle-on-git:git config --global merge.conflictstyle diff3git checkout --conflict=diff3With this, conflicts now show up as:
++<<<<<<< HEAD
+5
++||||||| parent of 7b0f59d (6)
++3
++=======
+ 6
++>>>>>>> 7b0f59d (6)7b0f59d is the SHA-2 of commit 6.instead of the inferior default:
++<<<<<<< ours
+5
++=======
+ 6
++>>>>>>> theirsWe can also observe the current tree state during resolution:so we understand that we are now at 5 and that we are trying to apply our commit
* b4ec057 (HEAD, master) 5
* 0b37c1b 4
| * fbfbfe8 (my-feature) 7
| * 7b0f59d 6
|/
* 661cfab 3
* 6d748a9 2
* c5f8a2c 16So it is much clearer what is happening:and so now we have to decide what the new code is that will put both of these together.
We now reach:and the tree looks like:So we understand that:
++<<<<<<< HEAD
+11
++||||||| parent of fbfbfe8 (7)
++6
++=======
+ 7
++>>>>>>> fbfbfe8 (7)* ca7f7ff (HEAD) 6
* b4ec057 (master) 5
* 0b37c1b 4
| * fbfbfe8 (my-feature) 7
| * 7b0f59d 6
|/
* 661cfab 3
* 6d748a9 2
* c5f8a2c 1and after resolving that one we now reach:
* e1aaf20 (HEAD -> my-feature) 7
* ca7f7ff 6
* b4ec057 (master) 5
* 0b37c1b 4
* 661cfab 3
* 6d748a9 2
* c5f8a2c 1 Git tips It's not a tree, it's actually a DAG Updated 2025-07-16
But not every directed acyclic graph is a tree.
Example of a tree (and therefore also a DAG):Convention in this presentation: arrows implicitly point up, just like in a
5
|
4 7
| |
3 6
|/
2
|
1git log, i.e.:and so on. The best websites of all time Updated 2025-07-16
Multi-user:
Chemical element Updated 2025-07-16
Chemical substance Updated 2025-07-16
Chemist Updated 2025-07-16
Differential equation Updated 2025-07-16
Git tips Linear history vs branching Updated 2025-07-16
Some people like merges, but they are ugly and stupid. Rebase instead and keep linear history.
Linear history:
5 master
|
4
|
3
|
2
|
1 first commitBranched history:
7 master
|\
| \
6 \
|\ \
| | |
3 4 5
| | |
| / /
|/ /
2 /
| /
1/ first commitWhich type of tree do you think will be easier to understand and maintain?
????
????????????
You may disconnect now if you still like branched history.
There are unlisted articles, also show them or only show them.