Nobody asked for the code to be maintained by DMA. The maintainer blocked a PR outside his subsystem, and even if it was part of his subsystem, the R4L approach is that C developers can break Rust code however they want.
Literally nobody suggested that the DMA maintainers should maintain Rust code.
If I were a maintainer in that position I’d be barring the doors too. It’s not a driver for some esoteric realtek wireless card or something.
This effectively kills R4L. If they can’t include Rust Interfaces for important subsystems, each driver written in Rust that uses these subsystems has to separately track all the Subsystem Interfaces, leading to lots of extra work for no benefit.
If this is the approach Linux takes, they should just cancel R4L completely.
This creates a lot of extra work for no benefit, as every driver that needs DMA would have to include their own copy of the DMA stuff.
Not just that, it’s the reason why it doesn’t need semicolons: https://en.wikibooks.org/wiki/JavaScript/Automatic_semicolon_insertion
*bonk* go to firejail
Oh boy, are you gonna LOVE Javascript
And what are the other e?
You mean on Iraqi landscapes?
Though you’d get the same speedup if you used SIMD intrinsics. This is just comparing non-SIMD to SIMD.
Right - it should have been:
document.querySelectorAll('span#copyright_year').forEach((el) => { el.innerText = new Date().getFullYear() })
so that we update all spans with that ID!
Well… No new ones, at least? Though it was around that time that I started hearing whispers in the night… “You can use WASM to ship Client-Side PHP”
I’ve once written a JS decompiler (de-bundler?) using ~150 regex for step-wise transformations. Worked surprisingly well!
Imma do it this evening, so hydrate up, bud
Just as a warning, the macvlan stuff isn’t well documented and seems to have hard limits. I worked with it a couple of years ago and had to eventually read a lot of Docker code to figure some stuff out, and the host was only able to successfully set up 4 macvlan networks at a time - the fifth (and any following ones) were never reachable, even though I used the same scripts as for all other ones.
Things might have improved in the meantime.
Crazy what other commenters are coming up with.
Not in my code
I sometimes use n as my loop variable (⌐■_■)
The Podman developers did contribute to Docker for a while before starting the project. Docker kept introducing issues and had some fundamentally bad design decisions that they didn’t want to change.
At least try to look into the history of these things before making broad and easily falsifiable statements.
I’d interpret that as a local social network app, not map/navigation.