It will be interesting to see how this works on the Advantage2, especially when it moves past the prototype stage. The greater connectivity between qubits may allow for an even better demonstration.
215 karma · joined November 17, 2020
It will be interesting to see how this works on the Advantage2, especially when it moves past the prototype stage. The greater connectivity between qubits may allow for an even better demonstration.
Inaccurate. D-Wave did in fact launch a 5000+ qubit system named Advantage in 2020.
I know you just chose this as an example, but clearly it wouldn't be acceptable to anyone to have a failed installation of something like this. On one extreme, it could cause a fire; but otherwise, it's just a button that doesn't work, and damages the quality reputation of the car.
Processor binning only works because it is a black box, indistinguishable from the outside. You can purposely disable components if your yields get high enough, etc. and nobody will ever notice the difference.
For vehicles, automakers will learn from customers that this kind of nickel-and-diming is not appreciated, when people turn to other manufacturers that still "get it", e.g. Mazda.
https://macfolkloreradio.com/2021/06/21/bob-hearn-a-brief-hi...
America badly needs a return to the much lighter S-10 and Ranger of the past, with a 4-banger and a small back seat. These behemoths with V8s are not necessary for most people, and neither is the level of temporary luxury they convey. Let's face it: after a couple years your shiny new truck is just as noteworthy as every other truck on the road, which is to say, most people don't care about it / aren't impressed by it anyway.
Better to get it sorted sooner than later. That GP visit can also be a good time to ask about all sorts of other small issues, and a blood test is a good idea at least every year or two. Ask about hormone levels, iron, vitamins, everything; for you it's just a lab visit.
I can't wait until it's possible to get these tests a few times a year and have all the values charted somewhere tied into the personal health ecosystem. Ironically, as someone interested in online privacy, I find the medical data the least concerning; I'm willing to let all of that go if it means I can get back some good answers or better healthcare. I can understand why some people aren't, of course, and they should always have the right to it; and it's good that this medical industry privacy situation is influencing other industries as well. But still! Imagine if some ML system with access to the data of a million people like me could show me exactly what I should stop eating, or exactly what supplement I need more of....
I suppose this is assuming that there's not going to be water in the future, and that you just want to extract whatever use there is left from an area before giving it over to desertification.
Not only that, but this kind of thing has existed for ~30 years now. I remember MS Word 6.0 on Windows 3.1, 16 bits and 4MB of RAM, with large documents with significant styling, embedded Powerpoint and Excel documents, MS Draw vector art, etc.
I concur that the line-based approach most Git tooling uses is not good enough. At the very least, even for code, it should be integrated with Tree-Sitter etc. by now and be comparing changes at the AST level, not just the raw text; and when it comes to documents, we should get side-by-side diffs showing the rendered document.
But is there a market for this, besides just you and me?
Gate model computers interest everyone because of the potential to factor large numbers; this could potentially render a lot of existing and past cryptography open to decryption that otherwise will be locked up for aeons, especially considering the apparently decaying effect of Moore's Law of late. However, it probably takes millions or billions of gate qubits to do that, whereas thousands of annealing qubits are enough to solve some interesting problems, and to contribute to finding better solutions when combined with classical compute in a hybrid setup.
Anyone smart enough to manage one format can probably manage any of them.
Cool, good to know this nearly 30 year old conflict is still just as active as ever. Tens of thousands of working DEB packages notwithstanding.
I don't need my lights to turn on and off on their own. I don't buy that anyone does, short of perhaps someone who has a physical disability for whomst it would be too difficult. For $20 I can get a timer - perfect for the closet light we always used to leave on by accident.
I think this is basically conspicuous consumption, tasteless pseudo-luxury. I am not impressed by your IoT colorful lightbulbs; impress me with your conversation.
We desperately need sub-20k electric cars and they just don't exist.
Sorry, but the sheer number of people out there working in jobs with "DevOps" as their title and the thousands and thousands of positions that recruiters are trying to fill at the moment means that this idea, which you're far from the first to posit, is simply not correct anymore (if it ever was).
A DevOps is a sysadmin who can program. That's it, end of story. This puts these people in contrast to the non-programming sysadmin (e.g. perhaps of the Windows era of expecting a proper UI to configure things), and the non-administrative developer (again, also very much of the Windows era of producing enterprise software that is "thrown over the fence" to Ops).
The Unix administrators who scripted things in the past are the direct spiritual predecessors of the modern "DevOps" who simply have newer and better tools to accomplish the same goals.
> This means a number of tools can be DevOps as a service.
No, that doesn't make any sense at all. Tools merely provide capabilities; these must be exercised by people who understand them in order to realize value. Even as basic things are automated away, there is still a considerable role for the people who are able to knit systems together, especially for being able to unblock pure-Dev teams (for which there is still a tremendous role), facilitate test engineering and QA needs (again, a specific skillset that shouldn't always be lumped upon developers), and so forth.
Put differently: when you want to take a shop to the level of maturity to have proper automated deployment, or you get stuck with some broken CI problem you cannot figure out, when you need to make your existing product multi-region, when your org acquires some other org and you need to bridge the products together, when you need to expand to a hybrid or multi-cloud system... all of these kinds of situations require the kinds of skillsets that are labelled as "devops" today.
Don't confuse the map for the territory.
https://www.hpcwire.com/2021/10/21/d-wave-embraces-gate-base...
I'm at the point where I would pay 5 figures a year for something purely to do better alerting inside or alongside Grafana. Clicking alerts together is a nightmare when I have a ton of identical systems I need to configure. Same for dashboards - the limitations of the current mechanism are too severe.
I'd build my own templating mechanism for it, but I still want the alerts visible in Grafana itself. Zabbix has the power to do all this but with a UX that is not ideal....