What does it mean to have a distributed quantum computer? Because if these distributed quantum computers are connected by classical communication channels (e.g. the internet), then it has been proven that this cannot provide any quantum speedup over just a single quantum computer.
So to actually get a quantum speedup, these quantum computers will need to be connected with quantum channels, which are possible IRC with fiber optic links (eg. by using the quantum state of the photons). But that is not the case.
A distributed quantum computer is one that is entangled over a photonic link either by satellite or terrestrial connection.
You are correct to say that these are not in broad distribution today, but we are building for the future where we do have ubiquitous quantum repeaters and interconnects. We are working with manufacturers, universities, government labs, and NGOs to do early research in this space and centering these operations in Wyoming, Colorado, and New Mexico.
In the meantime, it is also important to build the infrastructure for distributed hybrid applications and incentives that enforce cooperation in the presence of adversarial nodes.
For a short review of papers that are relevant to this area of research, see below:
Experimental demonstration that qubits can be cloned at will, if encrypted with a single-use decryption key
https://arxiv.org/abs/2602.10695
Well what makes you think the VPN providers are not tracking?
You would have to either self-host your own VPN server somewhere (maybe on a public cloud provider) or if you are truly paranoid, use something like Tor.
They have been subject to warrant requests, and had nothing to turn over. There are only a few vpn providers that I genuinely trust. (Mullvad, airvpn, etc)
Really though, I am not worried about 3 letter agencies performing legitimate law enforcement duties. I am worried about corporations hovering up more data about me than I'd want to reveal, and either using that as a basis to charge me more, or worse, they get hacked, and that data is used by bad actors to target me.
It's the gzipped size that matters a lot more. Also wasm is significantly faster to parse and run than Javascript so although 500kb seems like a lot for JS, for WASM it's not that much.
A general website will likely need a lot more data in the form of images and other media so all in all this is not too bad.
The reason why bundle size for JS is so important is that the browser needs to first download the JS, parse the JS, then JIT compile it before it can start running. For WASM on the other hand, the browser can in fact parse it while downloading in parallel and then run it almost immediately since WASM is much lower level. So for WASM the main bottleneck is downloading whereas JS, it is parsing and compiling.
Disagree. The bytes have to be read and extracted and the bigger it is, the more you are putting onto clients to load your page.
I'd also point out that this doesn't appear to be just simple runtime stuff like I thought. The fact that there's a 2x size difference between a simple webpage and a simple todo blog indicates this might be quiet expensive. That doesn't bode well for more complex applications.
I'd also point out that I just looked at the wasm. The bindings javascript themselves took up 37kb. That's bigger than react just for bindings.
> A general website will likely need a lot more data in the form of images and other media so all in all this is not too bad.
Yes, and a general website can function without those images. The part that makes the webpage functional is what I'm focusing on.
> The reason why bundle size for JS is so important is that the browser needs to first download the JS, parse the JS, then JIT compile it before it can start running. For WASM on the other hand, the browser can in fact parse it while downloading in parallel and then run it almost immediately since WASM is much lower level. So for WASM the main bottleneck is downloading whereas JS, it is parsing and compiling.
Before the browser can run a wasm blob, it has to download the javascript bindings which it has to parse and jit compile. It can be compiling the wasm while it's parsing the javascript, but it's not a free lunch. The wasm cannot start running until after the javascript is finished.
The browser is also free to start parsing the javascript while it's being downloaded. There's nothing special about javascript syntax that stops a browser from starting parsing while it's in flight (other than it might end up being dead).
If you actually read the README.md file, the first few lines say that there are hosted versions available that you can view directly in your browser. I also mentioned this in another comment. I don't know what else you want...
I just see a lot of open source projects fail on the basic "get the message out".
And, I actually would like to use a Rust / Wasm UI.
That's what was frustrating. I'm looking for this. And still, had to wade through site to find some slick demo showing the merits of the speed and responsiveness. You want some snappy demos to show zip. It says 'reactivity', so I was expecting some super fast demo.
Sure. Ok. Now, put those links on the main page with a big bold "Examples Here". Is it that hard. Why make potential users wade through 5 clicks to get to an example, and then see if they are interested enough to persue further.
If you want users, put in bold, splashy, easy to get to.
It isn't that hard.
Viewing on examples.sycamore.dev
All the examples are hosted under examples.sycamore.dev/<example_name> with <example_name> being the name of the example you want to view. For instance, the todomvc example is hosted on examples.sycamore.dev/todomvc.
Yes I plan on adding doc search. Although I'm not sure if I should try to build one from scratch (never tried building full text search before) or using something prebuilt like Algolia docsearch.
If algolia is close to deepwiki as I suspect, that does not replace the original doc site: it needs to index an existing doc site before.
So adding (even a simple) search to this site would be worth it imho.
No I think that's a different product. What I had in mind is what is on, for example, https://tailwindcss.com/ and many other open source project websites. If you open the search menu, you'll see at the bottom that it's powered by Algolia docsearch.
Basically its a service that automatically crawls your docs and creates a search index and widget that you can include on your website.
What kind of examples were you expecting? There are plenty of examples in the examples/ folder on GitHub as well as plenty of other projects using Sycamore as can be seen from GitHub’s reverse dependency page
But Sycamore does have ambitions to have native GUI support as well. I'm currently looking at GTK, Iced, and GPUI and see if it would be possible to add Sycamore support. This would make it possible to create GTK, Iced, or GPUI apps using building blocks from Sycamore.
I'm personally not to big of a fan of the Elm pattern for UI. Although it can be quite elegant, most of the times, it ends up being quite verbose even for simple things.
I feel like combining the drawing layer from one of these existing native UI frameworks with Sycamore could be interesting in reducing some of the boilerplate with GTK, Iced, GPUI, etc...
See Jozsa & Linden 2003: https://arxiv.org/abs/quant-ph/0201143
So to actually get a quantum speedup, these quantum computers will need to be connected with quantum channels, which are possible IRC with fiber optic links (eg. by using the quantum state of the photons). But that is not the case.