Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bonzini
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
26 ms
·
481.
▲
by
bonzini
2y ago
If you do so you have to add -fno-builtins (or just -fno-builtin-memcpy).
482.
▲
by
bonzini
2y ago
You have to release the whole system under the SSPL . So there could be a reading where you can't use Linux, you can't use systemd, you can't use glibc, etc.
483.
▲
by
bonzini
2y ago
``` is markdown for pre formatted text. It puts the LLM in the mood of generating machine readable data instead of prose.
484.
▲
by
bonzini
2y ago
Smart pointers are not really about managing memory, they're about managing lifetimes. Even things like the Rust RefCell are smart pointers.
485.
▲
by
bonzini
2y ago
Because it's not about devs, it's about distro packagers. They are an extremely important audience for QEMU. As pm215 said above, we don't want to make their lives unnecessarily harder. For example Debian has the backports re
486.
▲
by
bonzini
2y ago
Well, smart pointers and (sort of) templates and lambdas are in Rust. I definitely want smart pointers.
487.
▲
by
bonzini
2y ago
We already make an exception in that we don't support Debian bullseye (which is supported by the rest of QEMU until the April 2025 release), but not supporting Debian stable at all seemed too much. That said we will probably switch t
488.
▲
by
bonzini
2y ago
In Rust's case it is that when you say "you have IsA<Device> for all types that implement IsA<PCIDevice>" you are actually saying "you have IsA<Device> for all types, but only if they implement IsA<P
489.
▲
by
bonzini
2y ago
No, you only need to assert that the field with that name exists .
490.
▲
by
bonzini
2y ago
The declaration of martial law was already unconstitutional in the part that forbids something that is explicitly mentioned in the constitution (a meeting of the Parliament to request that the president lift the martial law). Which is proba
491.
▲
by
bonzini
2y ago
And really it's not so much fighting the compiler as it's understanding your code better—in ways that help you even when writing C. The times that you do fight the compiler it will suggest the right thing (add clone, add &, ad
492.
▲
by
bonzini
2y ago
> As far as I know, const traits are still on track. Yes they are. My use case is something like the bitflags crate, there are lots of bit flags in emulated devices of course. In the meanwhile I guess it would be possible to use macros
493.
▲
by
bonzini
2y ago
"Your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should." :D Though I admit that Rust also has to include the full list of base classes ( https://github.com/
494.
▲
by
bonzini
2y ago
The object model in QEMU is from 2007-2011. Internally there isn't a lot of inheritance (it's pretty shallow), but yeah I guess "is-a" is what was in vogue at the time. However there is a reason to have the object model,
495.
▲
by
bonzini
2y ago
The legacy reset way is fine, and yeah this is where being more strict and doing more stuff within the language should help.
496.
▲
by
bonzini
2y ago
> There are more wacky compromises listed than there are good ideas. I am happy to learn about other's opinions and especially contrary opinions, otherwise I would not have made a public post. I am myself not 100% sure that the idea
497.
▲
by
bonzini
2y ago
Yes it's https://github.com/qemu/qemu/tree/master/scripts/tracetool . I also found https://github.com/cuviper/probe-rs/tree/master/src/platform which se
498.
▲
by
bonzini
2y ago
Right now the only language-level thing I would like is const operator overloading. Even supporting MSRV as old as 1.63 was not a big deal, the worst thing was dependencies using let...else which we will vendor and patch. Pin is what it is,
499.
▲
by
bonzini
2y ago
QEMU has several tracepoint providers, the main ones are (a slightly fancy version of) printf and USDT. There is a Python program that generates the C code for the chosen backend(s), so the thing to do would be to adjust the script to produ
500.
▲
by
bonzini
2y ago
Hello! Small world. :) For drivers, it's already happening, especially for graphics but not limited to that. 6.13 has some very important changes. A lot of Linux is drivers so that's already a reason to be bullish. Answering for Q
501.
▲
by
bonzini
2y ago
Is Samurai still alive? I have sent a pull request to improve signal handling but it has been sitting ignored for over half a year.
502.
▲
by
bonzini
2y ago
There's also vanadium flow batteries that seem to be improving and might be good enough to provide a smoother peak capacity. https://www.reddit.com/r/dataisbeautiful/comments/17r9q6s/co...
503.
▲
by
bonzini
2y ago
Thanks for posting this to HN! Author here, happy to answer any questions. (By the way, I did not originally start the project, though I've worked quite a bit on the safe abstractions that are mentioned in the roadmap).
504.
▲
by
bonzini
2y ago
Just one nit: contrary to what the article suggests, as far as I remember the compact model was not so common because using far pointers for all data is slow and wastes memory. Also, the globals and the stack had to fit in 64k anyway so com
505.
▲
by
bonzini
2y ago
How are vias manufactured, and why tungsten (I suppose it has something to do with high fusion point?).
506.
▲
by
bonzini
2y ago
> Whereas CoC-driven development risks leading to a chilling effect where you no longer constructively argue about stuff, let alone in a passionate manner (that, admittedly, risks going the wrong side of the fence on occasion), and just
507.
▲
by
bonzini
2y ago
Probably it would forbid "Download Chrome" on Google and "Download Edge" on Bing.
508.
▲
by
bonzini
2y ago
> assuming that the 220 is entirely SWE salaries With 750 employees for Mozilla Corp, that's unlikely. Even if 80% are developers that would be $350,000 salary on average.
509.
▲
by
bonzini
2y ago
There's Mozilla Foundation (where making a browser is not on the road map) and Mozilla Corporation (which makes money by making a browser to finance the foundation). Mozilla Corporation revenue is about half a billion, most of it c
510.
▲
by
bonzini
2y ago
Regressions in upstream kernel exist; they may be security issues, assertion failures, performance regressions, and so on. It's just too much work to validate a whole new kernel every six months, and also much harder to pinpoint a reg
More ›