1,285 karma · joined March 18, 2015
Disclaimer: I work on the Q# project (https://github.com/microsoft/qsharp) in a team under Matthias Troyer (quoted in the article).
Entirely personal option: I do think tempering some of the hype of the past few years/decades and focusing on the areas of highest potential is in general a good thing. Progress hasn't been what some optimists had hoped for, but hardware has been progressing quite quickly & consistently for years now, and I'm confident we'll get there eventually.
If they redistribute the source then yes, but that’s not the concern in the post.
I spent some time in India years ago and remember being amazed that a country with over a billion people could have so much vast open beautiful countryside. It’s incredible how much population can fit into a few (very) dense areas.
We just shipped 1.0, but this slightly older blog post goes into the architecture a bit more: https://devblogs.microsoft.com/qsharp/introducing-the-azure-...
Disclaimer: I work on the quantum team at Microsoft.
Fact is, if you ship enough 'low probability' bugs in your product, your probabilities still add up to a point where many customers are going to hit several of them.
I've used plenty of products that suffer from 'death by a thousands cuts'. Are the bugs I hit "ship blockers"? No. Do I hit enough of them that the product sucks and I don't want to use it? Absolutely.
When I'm thinking where to spend my money, I do appreciate that Tesla (and SpaceX) push the boundaries in high-tech industries, and that much of the R&D and manufacturing spend goes to employees in my home country.
Are you supposed to grow out of that? I’m 51 and I still notice this about myself at times!
(Only half joking here. It is amazing how hard it can be to snap out of a “sulky mood” after some type of frustration or disappointment, even when you’re aware of it and that it’s doing more harm than good).
What I would love to see is some data on why so many companies that previously said during Covid “Oh wow, this remote work is great! We’re going to stay like this” are now saying “Sorry, changed our minds, now we want you back in the office”.
Office space isn’t cheap. Requiring employees be local limits your pool of talent. A lot of people like being remote. Companies must have a strong reason, hopefully with some data to back it up, but I’ve not seen any hard evidence for the about face yet. Anyone got any pointers?
https://quantum.microsoft.com/en-us/experience/quantum-crypt...
It really is insane the level at which current hardware works.
I do think a lot of CEOs are way overpaid. That said, if a couple hundred million package means the difference between a company folding and firing everyone, or being a multi-billion dollar business with thousands of employees, the math works out.
https://github.com/VSCodeVim/Vim/blob/master/ROADMAP.md#repe...
I think worrying about things like single-use shopping bags and compostable straws is great from a "keep pollution out of the environment" perspective, but I doubt they make a huge difference from a landfill usage perspective.
It wasn't cheap, but it looks great and has been very durable (had it about 5 years now out in the sun and still looks like new).
That's part of the goal of Q#. It's designed to be a language which allows you to build up from quantum gates, efficiently work with quantum concepts such as 'adjoint' and 'controlled' operations, and build that up into a higher level of abstraction. You can see an old post as to some of the reasoning when it was first developed at <https://devblogs.microsoft.com/qsharp/why-do-we-need-q/>.
Another consideration to some of the points raised here, is that even on today's state-of-the-art hardware you typically only get a couple thousand gates at best before noise overwhelms the system and the qubits 'decohere' (https://en.wikipedia.org/wiki/Quantum_decoherence). So you do often want to develop at a level where you can squeeze every last gate out of whatever program you're writing. (If you intend to run it on a quantum computer and not just simulations).
Being that the post is about quantum simulation, you can see the one our team built in Rust at https://github.com/qir-alliance/qir-runner/blob/main/sparses... . This uses 'sparse' simulation, which means any state with a probability of 0 isn't tracked, which turns out to be quite a few in a lot of algorithms. This allows you to simulate many more qubits than you can with a full state simulator (where you need to track 2^n states for n qubits). It also does some other nifty tricks where you can elide or combine gates before they are performed to get even more perf. We use it in our new Q# stack (https://github.com/microsoft/qsharp) to run program simulations in our CLI or in the browser (such as on our new https://quantum.microsoft.com site), or inside VS Code (desktop or web)).
We are looking to evolve the Q# language and improve the quantum development experience, with a focus given to a 'scalable' quantum future where gate count and noise is less of a limit, and moving development higher up in abstraction - as you outline. So if it is something you have an interest in, we're more than happy to get the input on the qsharp GitHub repo linked to above.
If you look at what ChatGPT and Midjourney and the like can do now compared to just a couple of years ago, it's pretty incredible. If you extrapolate the next few similar jumps in capability, and assume that won't be 20 years away, then what AI is going to be capable of before even my kids leave college is going to be mind-boggling, and in some possible futures not in a good way.
I remember seeing this talk from Sam Harris nearly 6 years ago and it logically making a lot of sense back then (https://youtu.be/8nt3edWLgIg). The past couple of years have made this all the more prescient. (Worth a watch if you have 15 mins).
For example, if you go to the playground that we publish on every push to main (https://microsoft.github.io/qsharp/), and open the Developer Tools to see the network traffic, you'll see that our WebAssembly module is just 1.5MB (504kb over the wire) - which includes the not just the language (parser, type system, IR, etc.) but also the runtime interpreter and quantum simulator.
Similarly, for the native tools, on my MacBook (i.e. ARM64) the command line compiler ("./target/release/qsc") is 3.9MB, which is entirely standalone with no dependencies.
We do have many features to add, so I'm sure those will grow a bit, but we are focused on keeping things as small, portable, and fast as a general principal.
Yes, targeting WebAssembly, and the ability to then run in the browser, was a big part of it.
WebAssembly (will) also enable our language service extension to run in VS Code for the Web, as well as VS Code for desktop, with largely the same feature set.
It also means the core logic compiles to very performant native code for most platforms, which we use for the CLI.
It's early days for the project, with lots of work ahead of us, but I'm really proud of this first step. Happy to answer any other questions where I can!
Sure the experience was terrible, but that's the same play here. Apple generally takes a technology space which is a little early and poorly done by others, and ships a great experience across hardware, software, and ecosystem to capture a market.
Seems like getting to a point where ~75% of the population didn't need to file would be doable if there was enough motivation for it. If your only income is on a W-2, and your only mortgage / banking / trading is with U.S. companies like Chase or Morgan Stanley, no reason that couldn't all be done for you.