Ciro Santilli @cirosantilli  40

Uses Redux, while reactjs/react-rails appears to do that more manually

Lots of focus on Heroku deployability, which is fantastic: shakacode.gitbooks.io/react-on-rails/content/docs/additional-reading/heroku-deployment.html

Live instance: www.reactrails.com/ with source at: github.com/shakacode/react-webpack-rails-tutorial Not the most advanced web-app (a gothinkster/realworld-level would be ideal). Also has clear dependency description, which is nice.

Trying at github.com/shakacode/react-webpack-rails-tutorial/tree/8e656f97d7a311bbe999ceceb9463b8479fef9e2 on Ubuntu 20.10. Got some failures: github.com/shakacode/react-webpack-rails-tutorial/issues/488 Finally got a version of it working at: github.com/shakacode/react-webpack-rails-tutorial/issues/488#issuecomment-812506821

Oh, and the guy behind that project lives in Hawaii (Ciro Santilli's ideal city to live in), has an Asian-mixed son, and two Kinesis Advantage 2 keyboards as seen at twitter.com/railsonmaui/status/1377515748910755851, Ciro Santilli was jealous of him.

Answers suggest hat you basically pick a random large odd number, and add 2 to it until your selected primality test passes.

The prime number theorem tells us that the probability that a number between 1 and $N$ is a prime number is $1/log(N)$.

Therefore, for an N-bit integer, we only have to run the test N times on average to find a prime.

Since say, A 512-bit integer is already humongous and sufficiently large, we would only need to search 512 times on average even for such sizes, and therefore the procedure scales well.

RSA vs Diffie-Hellman key exchange are the dominant public-key cryptography systems as of 2020, so it is natural to ask how they compare:

As its name indicates, Diffie-Hellman key exchange is a key exchange algorithm. TODO verify: this means that in order to transmit a message, both parties must first send data to one another to reach a shared secret key. For RSA on the other hand, you can just take the public key of the other party and send encrypted data to them, the receiver does not need to send you any data at any point.

A "quantum computer operating system". Or in English, control system + quantum error correction.

uknqt.ukri.org/wp-content/uploads/2021/10/UKNQTP-Strategic-Intent-2020.pdf page 24 mentions UKNQTP investment and gives an overview of some layers.

Sample playlist: www.youtube.com/playlist?list=PLW_HsOU6YZRkdhFFznHNEfua9NK3deBQy

Basically the same content as: Richard Feynman Quantum Electrodynamics Lecture at University of Auckland (1979), but maybe there is some merit to this talk, as it is a bit more direct in some points. This is consistent with what is mentioned at www.feynman.com/science/qed-lectures-in-new-zealand/ that the Auckland lecture was the first attempt.

Some more information at: iucat.iu.edu/iub/5327621

By Mill Valley, CA based producer "Sound Photosynthesis", some info on their website: sound.photosynthesis.com/Richard_Feynman.html

They are mostly a New Age production company it seems, which highlights Feynman's absolute cult status. E.g. on the last video, he's not wearing shoes, like a proper guru.

Feynman liked to meet all kinds of weird people, and at some point he got interested in the New Age Esalen Institute. Surely You're Joking, Mr. Feynman this kind of experience a bit, there was nude bathing on a pool that oversaw the sea, and a guy offered to give a massage to the he nude girl and the accepted.

youtu.be/rZvgGekvHest=5105 actually talks about spin, notably that the endpoint events also have a spin, and that the transition rules take spin into account by rotating thing, and that the transition rules take spin into account by rotating things.

Bibliography:

Pauli matrix.

Framework built on top of React.

Officially recommended by React^[ref]:

gothinkster/realworld blog example by Ciro Santilli: node Express Sequelize Next.js realworld example app.

Basically what this does is to get server-side rendering just working by React, including hydration, which is a good thing.

Next.js sends the first pre-rendered HTML page along with the JavaScript code. Then, JavaScript page switches just load the API data.

Next.js does this nicely by forcing you to provide page data in a serialized JSON format, even when rendering server-side (e.g. the return value of getServerSideProps). This way, it is also able to provide either the full HTML, or just the JSON.

Some general downsides:

In theory, Next.js could be the "ultimate frontend framework". It does have a lot of development difficulties that need to be ironed out, but the general concepts, and things it tries to integrate, including e.g. webpack, TypeScript, etc. are good. Maybe the question is when will someone put it together with an amazing backend library and dominate and finally put an end to the infinite number of Js Frameworks!

In-tree examples at: github.com/vercel/next.js/tree/canary/examples

canary is their master: github.com/vercel/next.js/issues/3211

In order to offer its amazing features, Next.js is also extremely opinionated, which means that if something wasn't designed to be possible, it basically isn't.

No prerender with custom server? It forces you to write your API with next as well? Or does it mean something else?

TODO can it statically generate pages that are created at runtime? E.g. if I create a new blog post, will it automatically upload a static page? It seems that yes, and that this is exactly what Incremental Static Regeneration means:However, Ciro can't find any mention of how to specify where the pages are uploaded to... this is pat of the non-Vercel deployment problem.

Can't ISR prerenter by URL query parameters:That plus the requirement to have one page per file under pages/ leads to a lot of useless duplication, because then you are forced to place the URL parameters on the pathnames.

"Module not found: Can't resolve 'fs'" Hell. The main reason this happens seems to be the that in a higher order component, webpack can't determine if callbacks use the require or not to remove it from frontend code. Fully investigated and solved at:

Overviews:

TODO answer:

Determines energy. This comes out directly from the resolution of the Schrödinger equation solution for the hydrogen atom where we have to set some arbitrary values of energy by separation of variables just like we have to set some arbitrary numbers when solving partial differential equations with the Fourier series. We then just happen to see that only certain integer values are possible to satisfy the equations.

Fixed total angular momentum.

The direction however is not specified by this number.

To determine the quantum angular momentum, we need the magnetic quantum number, which then selects which orbital exactly we are talking about.

Fixed quantum angular momentum in a given direction.

Can range between $\pm l$.

E.g. consider gallium which is 1s2 2s2 2p6 3s2 3p6 4s2 3d10 4p1:

The z component of the quantum angular momentum is simply:so e.g. again for gallium:

Note that this direction is arbitrary, since for a fixed azimuthal quantum number (and therefore fixed total angular momentum), we can only know one direction for sure. $z$ is normally used by convention.

This is a bit "formal hocus pocus first, action later". But withing that category, it is just barely basic enough that 2021 Ciro can understand something.

By: Tobias J. Osborne.

Lecture notes transcribed by a student: github.com/avstjohn/qft

18 1h30 lectures.

Followup course: Advanced quantum field theory lecture by Tobias Osborne (2017).

Followup to Quantum field theory lecture by Tobias Osborne (2017).

When the word "advanced" precedes QFT, you know that the brainrape is imminent!!!

Big goal: explain the Standard Model.

React setups:

One problem with Django is that it does not expose its ORM as an external library: stackoverflow.com/questions/33170016/how-to-use-django-1-8-5-orm-without-creating-a-django-project which is wasteful of development time.