Ciro Santilli @cirosantilli 40

Sebastian Weidt. He is German, right? Yes at youtu.be/SwHaJXVYIeI?t=1078 from Video 3. "Fireside Chat with with Sebastian Weidt by Startup Grind Brighton (2022)". The company was founded by two Germans from Essex!
Winfried Hensinger: if you saw him on the street, you'd think he plays in a punk-rock band. That West Berlin feeling.

Homepage says only needs cooling to 70 K. So it doesn't work with liquid nitrogen which is 77 K?

Homepage points to foundational paper: www.science.org/doi/10.1126/sciadv.1601540

Video 1.

Universal Quantum emerges out of stealth by University of Sussex (2020)

Source. Explains that a more "traditional" trapped ion quantum computer would user "pairs of lasers", which would require a lot of lasers. Their approach is to try and do it by applying voltages to a microchip instead.

youtu.be/rYe9TXz35B8?t=127 shows some 3D models. It shows how piezoelectric actuators are used to align or misalign some plates, which presumably then determine conductivity

Video 2.

Quantum Computing webinar with Sebastian Weidt by Green Lemon Company (2020)

Source. The sound quality is to bad to stop and listen to, but it presumaby shows the coding office in the background.

Video 3.

Fireside Chat with with Sebastian Weidt by Startup Grind Brighton (2022)

Source. Very basic target audience:

youtu.be/SwHaJXVYIeI?t=680 we are not at a point where you can buy victory. There is too much uncertainty involved across different approaches.
youtu.be/SwHaJXVYIeI?t=949 his background
youtu.be/SwHaJXVYIeI?t=1277 difference between venture capitalists in different countries
youtu.be/SwHaJXVYIeI?t=1535 they are 33 people now. They've just setup their office in Haywards Heath, north of Bristol.

 Read the full article

NumPy Updated 2025-07-16

 View more

The people who work on this will go straight to heaven, no questions asked.

 Read the full article

Passive income Updated 2025-07-16

 Read the full article

Prokaryotic small ribosome subunit Updated 2025-07-16

 Read the full article

PromethION Updated 2025-07-16

 Read the full article

Protein dimer Updated 2025-07-16

 Read the full article

PSL(2,7) Updated 2025-07-16

 View more

The second smallest non-Abelian finite simple group after the alternating group of degree 5.

 Read the full article

Python Protocol Updated 2025-07-16

 Read the full article

x86 Paging Tutorial / Application Updated 2025-07-16

 View more

Paging makes it easier to compile and run two programs or threads at the same time on a single computer.

For example, when you compile two programs, the compiler does not know if they are going to be running at the same time or not.

So nothing prevents it from using the same RAM address, say, 0x1234, to store a global variable.

And thread stacks, that must be contiguous and keep growing down until they overwrite each other, are an even bigger issue!

But if two programs use the same address and run at the same time, this is obviously going to break them!

Paging solves this problem beautifully by adding one degree of indirection:

(logical) ------------> (physical)
             paging

Where:

logical addresses are what userland programs see, e.g. the contents of rsi in mov eax, [rsi].
They are often called "virtual" addresses as well.
physical addresses can be though of the values that go to physical RAM index wires.
But keep in mind that this is not 100% true because of further indirections such as:
- memory-mapped I/O regions
- multi channel memory

Compilers don't need to worry about other programs: they just use simple logical addresses.

As far as programs are concerned, they think they can use any address between 0 and 4 GiB (2^32, FFFFFFFF) on 32-bit systems.

The OS then sets up paging so that identical logical addresses will go into different physical addresses and not overwrite each other.

This makes it much simpler to compile programs and run them at the same time.

Paging achieves that goal, and in addition:

the switch between programs is very fast, because it is implemented by hardware
the memory of both programs can grow and shrink as needed without too much fragmentation
one program can never access the memory of another program, even if it wanted to.
This is good both for security, and to prevent bugs in one program from crashing other programs.

Or if you like non-funny jokes: