All action scenes are useless crap, but the premise with Ciro's precious simulation hypothesis subject, related physics and the illusion of life.
It is a shame that the key premise of using human bodies to produce energy is completely and impossibly stupid. You would obviously get more energy by directing burning the food you feed into humans.
If the film had been made later, maybe the much more plausible concept of AI alignment would would have been used instead. What a shame.
- www.youtube.com/watch?v=aau8qa3xgFs Neo takes the blue pill mashup with Office Space with deepfake faces
Some/all courses expire in 4 weeks: www.futurelearn.com/courses/intro-to-quantum-computing. Ludicrous.
Can be seen as a cheap form of DNA sequencing that only test for a few hits. Some major applications:
- gene expression profiling
- single-nucleotide polymorphism: specificity is high enough to detect snips
Breakdown:
Zen master and the little boy scene from Charlie Wilson's War
. Source. This is how Ciro Santilli first heard the old man lost his horse! The scene happens after the Americans seem to have had sucess in arming the Taliban in the 1980s to fight the Soviets, and then they decide to stop all monetary help to rebuild the country, which then leads to a terrorism threat many years later.Appears to be a Wikipedia clone but with much lower/no notability requirements guidelines, which overcomes one of Wikipedia's main issues: deletionism.
They do have the interesting idea of importing deleted Wikipedia pages as a source of content, which leads to some epic "most viewed pages" such as en.everybodywiki.com/List_of_erotic_and_sex_workers_with_unnatural_death which currently reads:
Stop Being Pervs, Go Watch Lichfaop/Faoplich Instead and you can also visit MR Info 24 for more details.
We can for example see Ciro Santilli's deleted entry PsiQuantum at: en.everybodywiki.com/PsiQuantum, Wikipedia deletion page: en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/PsiQuantum. Their attribution is atrocious however, e.g. it does not seem possible to find any mention of "Ciro Santilli" on the edit history, which just points to the delete article which is not visible anymore. They could really get into trouble for this one day.
Their main use case, as suggested by the website itself, if for people/brands to create pages about themselves.
There is only space for two languages at most in the world: the compiled one, and the interpreted one.
Those two are languages not by any means perfect from a language design point of view, and there are likely already better alternatives, they are only chosen due to a pragmatic tradeoff between ecosystem and familiarity.
Ciro predicts that Python will become like Fortran in the future: a legacy hated by most who have moved to JavaScript long ago (which is slightly inferior, but too similar, and with too much web dominance to be replaced), but with too much dominance in certain applications like machine learning to be worth replacing, like Fortran dominates certain HPC applications. We'll see. Maybe non performance critical scripting languages are easier to replace.
C++ however is decent, and is evolving in very good directions in the 2010's, and will remain relevant in the foreseeable future.
Bash can also be used when you're lazy. But if the project goes on, you will sooner or later regret that choice.
The language syntax in itself does not matter. All that matters is how many useful libraries and tooling it has.
This is how other languages compare:
- C: but cannot make a large codebase DRY without insanity
- Ruby: the exact same as Python, and only strong in one domain: web development, while Python rules everything else, and is not bad on web either. So just kill Ruby, please.
- JavaScript: it is totally fine if Node.js destroys Python and becomes the ONE scripting language to rule them all since Python and JavaScript are almost equally crappy (although JavaScript is a bit more of course).One thing must be said tough:
someobject.not_defined_propertysilently returningundefinedrather than blowing up is bullshit. - Go: likely a good replacement for Python. If the ecosystem gets there, will gladly use it more.
- Java: good language, but has an ugly enterprisey ecosystem, Oracle has made/kept the development process too closed, and API patenting madness on Android just kills if off completely
- Haskell: many have tried to learn some functional stuff, but too hard. Sounds really cool though.
- Rust: sounds cool, you will gladly replace C and C++ with it if the ecosystem ramps up.
- C: Microsoft is evil
- Tcl, Perl: Python killed them way back and is less insane
- R, GNU Octave and any other "numerical computing language": all of this is a waste of society's time as explained at: Section "Numerical computing language"
- Swift: Ciro would rather stay away from Apple dominated projects if possible since they sell a closed source operating system
My online university and why it is needed interview with Jordan Peterson (2018)
Source. Cheaper and online. Initial focus on social sciences.
Some have actually been preserved: en.wikipedia.org/wiki/File:Blue_Box_in_museum.jpg
Archive example: web.archive.org/web/20130726224338/http://librarianhelper.com/
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!
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-calculusArticles 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/derivativeVideo 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: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.
- 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
Figure 2. You can publish local OurBigBook lightweight markup files to either OurBigBook.com or as a static website.
Figure 3. Visual Studio Code extension installation.
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. 
- Infinitely deep tables of contents:
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