> the bonus point is that I can have access to its source code
Are you actually reading all the code before you run it? Are you re-reading it for each update? If not, then what's the point of bragging about having access to the source?
The point of sandboxing is that it's impractical to reliably audit, on a continuous basis, the massive volume of software that the average person runs. It's more economical to apply the least-privileged principle, and only give apps access to the things they need to function.
Monolith vs microservices is not the problem. It's architecture and code design in most cases.
When i hear "Rails monolith is a disaster" what it usually boils down to 8 out of 10 times is people putting their business logic inside models or controllers, when really it should live in its own set of classes, usually called services or service objects.
Can someone explain to me what pipewire's goal is? to be a better pulseaudio? if so, in what way is it trying to be better? also, how's the codebase quality? from what i heard, pulse's codebase is a mess, so if it can improve in that sense, i guess that's a win (?)
why does it do video? is trying to do media capture like OBS or be a compositor like wayland? if so why bother? those solutions exist already... maybe it should just stick to audio, cuz that part of it feels like feature creep.
> Now, more free games? It doesn't satisfy an urgent practical need, obviously... But the crucial thing is, free ones might make it easier for some people to say, 'Let's move off this non-free thing, and play a game that is free. So we can have the same pleasure, but without paying freedom as the price.'“
i'm sorry but i just can't read this without laughing. what does stallman think gamers are like?
i can only imagine the average teenage gamer trying to get their friends to stop playing virtually every game on the market and instead play some obscure game and trying to teach them how to install gcc and git to get it running