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.
stsquad
joined 1 year ago
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.
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).
So I may be biased but what is vmwares USP? From my limited experience it was a slightly more polished GUI for creating VMs and the ability to run on older pre-virt hardware. Is the experience still objectively better than the alternatives?
I certainly agree with a lot of that analysis. I also worry how signal continue to fund their app sustainably without compromising their users.
It is most likely another filesystem mounted where the flatpak can see it. A terminal tool like ncdu or even du will take an -x option to not cross file-system boundaries. That will show the true usage of everything bellow where you call it (even though it is a ramfs so not persisted across reboots).
Don't delete it. It's an area of the filesystem where the current user session data is kept. This includes things like sockets to communicate with other session components and lock files. It's usually hosted on a ram disk so takes up no space in the system and goes away when you shutdown your machine.
You can end up with a lot of boiler plate code and with duplication you run the risk that one unit tweaks the boiler plate in a way that behaves differently. This isn't insurmountable and a lot of rc scripts source a library of common functions shared between units. However from the point of view of the executor each unit is it's own whole ball of shell script code.