What’s your take on quantum.

@Northwest quantum computing it will store a qubit as a 01001 equivalent but how it holds ties to super position and other qubits is just crazy to fathom for me.

@userfawkes1105 Not sure I understand what you're proposing/asking.

Are you saying that a qubit is stored as a 01001?

A qubit is not stored as a binary string like 01001. A qubit is a quantum bit that exists in a quantum superposition of states, typically represented as:

|ψ⟩ = α|0⟩ + β|1⟩

Where:

- α and β are complex numbers called probability amplitudes

- |α|² + |β|² = 1 (total probability must equal 1)

- |0⟩ and |1⟩ are the basis states (analogous to classical 0 and 1)

Unlike classical bits which must be either 0 or 1, a qubit can exist in both states simultaneously until measured.

When measured, the qubit "collapses" into either state 0 or 1 with probabilities determined by |α|² and |β|² respectively.

This quantum superposition property is one of the key features that gives quantum computers their unique capabilities compared to classical computers that use conventional binary bits.

@Northwest quantum and conventional procedural programing will co exist because u can represent the qubit in binary too is what I meant if needed. So much like you would aggregate data you could potentially aggregate qubits too.

@userfawkes1105 Programing is not really about aggregating data.

@Northwest I was referring to when you analyze and combine data sets to work of. You aggregate within the database to build new datasets and reports so I think they are highly relevant and if qubits can be binary values you could technically store those qubits in a database and aggregate them there. Then pass those onto the quantum process. What’s your take on programming then if it’s not this? What stack are you coming from?

@userfawkes1105
In database technology, each field either represent a stand alone property, for instance first_name, or is an object, for instance address, an object, that when you unpack, you will find a substructure with the following fields:

street:
unit:
city:
zip:

And is organized as a hash that will gibberish when examined using Sequential Query Language Tools.

The database server can either be SQL(plain fields), NonSQL (fields as objects), or Hybrid.

But that's a technique to package data, store data, retrieve and decipher data. You can throw encryption as a parameter if you want to further complicate things.

When I program, I use a Hybrid technology, and "patterns" to package, encrypt, and retrieve, decrypt and unpack.

But that's a programming technique, not programming.

Quantum computing is going through an intermediate phase, when professionals and researchers are trying to use traditional tools for expediency's sake, but that will go away, when fractal-like templates will be developed to instantly manipulate qubit generated data.

This is something I envisioned 30 years ago, but didn't think would be achievable in our lifetime.

@Northwest well if it took 30 years since it’s still new I’m sure there will be plenty of time where they will co exist and I don’t see why you shouldn’t store the qubits and combining with other columns describing the qubit you couldn’t aggregate its values like with min or something assuming the qubit stored as a binary value also has adjacent columns with human readable values and aggregate new data with joins. And other connections. I’m sure there are other ways to work those but I don’t see why u couldn’t also implement that kind of technique.

@userfawkes1105 Ummm.... No.