@pinkforest I met the guy who created ritc and he recommended me to check out Bevy for audio plugin alike stuff :-) Already found something along the lines of egui-baseview
: https://github.com/kunalarya/bevy_baseview_plugin, which makes it feasible to interface with clap host.
@pinkforest thanks for great comments!
talking about asm, one feature i’m waiting for to become stable is naked functions, which is fortunately in unstable.
one api that was outdated even when rust first came out is File API. it models POSIX golden days of the tape drive part ;-) i.e. it is pretty much in the 70s idiomatically. or what was the latest thing back then.
with modern storage and 64-bit address space only thing that you ever want to use fd for is with sendmsg(SCM_RIGHTS)
when you share it betwen multiple processes.
rest is better to be done simply by mapping the whole thing to address space and let page cache take care of you. initially reserved set size is ofc zero bytes with invalidated page table entries.
it is great way to also deal with large sparse arrays for the obvious reasons.
not a huge issue. i’m pretty happy with https://github.com/rust-vmm/vm-memory but hopefully stdlib will have equivalent functionality some day. despite the name this can be used outside KVM context.
I get that for sure but…
This is the thinking that apply 100% also to any piece of user space code that I might do. I figure out the best possible solution that I can think of with my limited skills and then pick the tool that I try to nail it sometimes succeeding and sometimes failing. So yeah, my world is as plain and simple as that :-) Engineering problem at hand is the first priority, and obviously to pick the right tool I need to exactly compare pros and cons of them for that particular problem.
A recent example is an authentication module prototype that I’m developing for Ethereum ecosystem (and presenting possibly at ethprague). For that I’m most likely using Rust, and ended up to that outcome by comparing pros and cons of possible alternatives.