While shell based RC systems do offer flexibility they also have downsides including copy and paste leading to subtly different behaviour across units. Dependency resolution was also a bit of a hack on top of scripts to deal with concepts like run levels.
The declarative approach of a proper configuration is a better and more scalable solution.
It's about time. I know there was a desire to avoid over regulating the burgeoning internet economy but we reached the era of monopolies a while ago now.
I'm looking at Embassy too for a Pico project and combining it with a nostd mqtt implementation. However I need to understand Futures and if/how they relate to the async paradigm.
So is the theming here for the window decorations or the text colour scheme?
How much theming does a terminal need? Personally my required features were a server and good font support. Currently I use the foot terminal: https://codeberg.org/dnkl/foot
They have been working on VirtIO vulkan support as well as native context support for their cards.
It's entirely configurable but I think by default sudo will "cache" your authentication for a period of time so multiple commands in the same session only need the password entered once. You can even configure sudo to not need a password for certain commands (although obviously you need to be careful you're not opening a hole in your security).
It needs more than that. The NHS has always been a bottomless pit in terms of what it could spend. If we don't as a country invest more in preventive and early interventions it's going to be overwhelmed by an increasingly chronically ill population. We will never be able to throw enough money at the NHS then, especially if an ever larger portion of the population isn't contributing to the economy to fund that.
The ISA may be open but I'm pretty sure the microarchitecture will be totally proprietary. Even with a kick ass microarchitecture they may still struggle if they can't use the latest process nodes to actually manufacture the chips.
Having said that I suspect the main challenge RISCV is going to face is the software ecosystem. That stuff can take a decade to build and requires a degrees of cooperation between all the companies building chips.
I strongly suspect it's underreported as well. Speak to enough women and you hear distressingly familiar stories about public harassment. I think attitudes have improved somewhat since my mum's days (avoiding being grouped on the train to school was apparently just one of those things) but still has a long way to go.
I was sadly stymied by the fact the rocm driver install is very much x86 only.
Yes training is the most expensive but it's still an additional trillion or so floating point operations per generated token of output. That's not nothing computationally.