I would imagine very little of the training data consists of a question followed by an answer of “I don’t know”, thus making it statistically very unlikely as a “next token”.
1,285 karma · joined March 18, 2015
I would imagine very little of the training data consists of a question followed by an answer of “I don’t know”, thus making it statistically very unlikely as a “next token”.
They also tied that to Trump's desire to get out of Europe and deescalate the Middle East, being that if the U.S. was already stretched across Ukraine and say Iran, it would be way to stretched to also wage anything in the far east.
I'm no expert by a long way, but I can see some logic in the argument.
The next one about the voices is excellent too, so linking both. The care they put into both the show and the people involved is almost as touching as the show itself.
https://www.20k.org/episodes/thesoundofbluey https://www.20k.org/episodes/thevoicesofbluey
Our VS Code extension is trivial to install (https://learn.microsoft.com/en-us/azure/quantum/install-over...) or just try it entirely in the browser with Visual Studio Code online (https://vscode.dev/quantum/playground/)
To support that last scenario, where the language service, debugger, simulator, even package references, can run entirely in the browser, we built the whole thing using Rust compiled to WebAssembly, and our VS Code extension runs as pure JavaScript and Wasm. If interested you can dig into the implementation at https://github.com/microsoft/qsharp .
Happy to answer any questions!
With that base, I’ve found their docs decent enough, especially coupled with the Metal Shader Language pdf they provide (https://developer.apple.com/metal/Metal-Shading-Language-Spe...), and quite a few code samples you can download from the docs site (e.g. https://developer.apple.com/documentation/metal/performing_c...).
I’d note a lot of their stuff was still written in Objective-C, which I’m not that familiar with. But most of that is boilerplate and the rest is largely C/C++ based (including the Metal shader language).
I just ported some CPU/SIMD number crunching (complex matrices) to Metal, and the speed up has been staggering. What used to take days now takes minutes. It is the hottest my M3 MacBook has ever been though! (See https://x.com/billticehurst/status/1871375773413876089 :-)
What do you hope to be doing in 5 years? Architecting quantum solutions? Reselling or consulting on cloud solutions? Building quantum applications?
I think the quantum space will have quite a bit of progress in 5 years, but I think most experts in the space (of which I'm NOT one) think we're still over 5 years out before there's broad adoption on running quantum programs with significant business value. (i.e, it'll still largely be researchers and bleeding edge adopters).
Opinions are my own, etc.
One thing I did forget to mention is that you can play with this stuff in a "familiar to software developers" way in our VS Code playground at <https://vscode.dev/quantum/playground/> . This is a 'code first' approach familiar to software developers leveraging VS Code integration. The playground is pre-populated with a bunch of common quantum algorithms.
You can also install the extension in VS Code directly (<https://marketplace.visualstudio.com/items?itemName=quantum....>), you don't need to run it in the browser, but even in the browser it has a fully working language service, debugger, evaluator, quantum simulator, package management, etc. It's all written in Rust and compiled to either Wasm for the browser and VS Code extension, or native code for the Python package. (I'm thinking about doing a video on how we build it, as I expect it will interesting to this type of crowd. Let me know if so).
Disclaimer: I work in Azure Quantum on the product mentioned. AMA.
https://quantum.microsoft.com/en-us/tools/quantum-katas
The first few lessons do cover complex numbers and linear algebra, so skip ahead if you want to get straight to the 'quantum' coding, but there's really no escaping the math if you really want to learn quantum.
Disclaimer: I work in the Azure Quantum team on our Quantum Development Kit (https://github.com/microsoft/qsharp) - including Q#, the Katas, and our VS Code extension. Happy to answer any other questions on it.
Any pointers to examples? I'd be fine sticking with floats as a first step, but would love to see some (reasonably optimized) low-level GPU code for working with matrices of complex numbers (preferably for Metal or WGPU, which is what I'm using).
I think React peaked with hooks around 2019. I write most of my front-end with the smallest 'React-like' library possible (Preact) using only functional components, and with as little 'magic' from useEffect etc. as possible.
I like to stay close to 'raw' HTML/CSS/JS when possible, but the web platform APIs are just a little to clunky and verbose for me without the JSX abstraction.
I hadn't worked with complex numbers much for most of my life, but getting into quantum computing recently it is ALL complex numbers (and linear algebra). It's fascinating (for a certain mindset at least, which I guess I fall into), but it is a lot of mental work and repetition before it starts to feel in any way 'comfortable'.
I believe they had a big hand in ARM64. Though best reference I can find right now is this very site: https://news.ycombinator.com/item?id=31368489
Sure, maybe that’s a requirement for the type of life we on earth know about, but I don’t see why other elements couldn’t have also formed in just the right way to be able to reproduce, and maybe eventually “think”.
Similar to many other toxic things, once the genie is out of the bottle and the government gets used to the revenue it generates, there is a large disincentive to tackling the problem.
Staff are such a huge part of costs, and the difference between your good staff and bad staff can break a company. Adopting any policy that would encourage the staff who can go elsewhere (the best ones) to leave and be left with the ones who can’t (the less good ones) is such a huge risk, you wouldn’t take that position for a few million dollars, but only if you believed it’s the best strategy long term.
It is interesting to me though that with so many companies taking this stance lately, many of them heavily data driven (like Amazon), that I’ve not yet seen any actual data or research that says “Here are some quantitive numbers on what we think having folks back in the office is worth”. Anyone got any data on this?
I found this line telling. I’m wondering if the Hacker News crowd is biased towards the “hacker” stereotype - the socially awkward coder who likes to be left alone and crank out largely independent work.
I have a couple of folks like this in my team, and they are absolutely as good (or better) working from home, as they don’t really talk to others much or contribute in meetings anyway.
But you can’t build a team/org out of those personality types. Much of the creative work and important decisions _does_ happen face to face, let alone the ad-hoc ideation and brainstorming from being in the same space.
I don’t think it’s a requirement that everyone be in the office 5 days a week (I don’t do that myself), but I do see the negatives of letting the team work from home whenever they want and expecting to get the same level of work done over Teams/Zoom calls and email.
Yet here we all are, reading the comments, looking for insights, knowledge, and entertainment.
I always thought the material had to be forced together at high pressure for the chain reaction to start. Crazy that just dropping it had such dire consequences.
You need inline html fairly often for anything non-trivial, and some of the rules certainly aren’t intuitive or easy to remember.
That said, like JSON, it won by being both simple to grok and good enough for most use cases.
I don’t worry at all about my 8yo boy however, as he’s very cautious and risk averse. My 6yo girl though already scares me to death with the stuff she does when she slips out of sight. I can’t wait for the teenage years! <sarcasm>
If the experts don’t agree on risks, then clearly there’s a non-zero chance.
On some tasks, computing machines passed us by a while ago. I already ask an LLM several questions a day as it has a much “broader” intelligence than I do. Many times the code it suggests is exactly what I was about to write - sometimes better. The capabilities of generative AI today were in the realm of science fiction just a few years ago.
Artificial intelligence will continue to evolve faster than human intelligence. Sticking our head in the sand and acting like we will always be “superior” seems fool-hardy.
Between the various TypeScript module options and various package.json module options (and various code patterns used), modules make JavaScript way more painful than it should be.
I think most of the JS language standards work the past 10 years has been awesome, but modules was definitely rushed and poorly thought though, causing years of frustration.
I don’t see any mention of size optimizations in the blog post. Anyone have any knowledge on this they can share (else guess I’ll just try again with the new release).