The point is that in the correct hands it does not.

Nah, they just would have either used something else, or fucked us with some other way. The kernel license just allowed them to do it like this.

One init system is the new standard, widely adopted by all serious distros, installed and configured by default. It is opinionated, spits in the eye of most experienced IT admins but is the only real alternative for who needs to earn a living with linux. It is well supported and understood… The others are well established standards that did not survive the test of time and are slowly dying out, kept around by nostalgic hobbyists that will catch any mention of systemd as an excuse to profess their hate for poettering, binary logs or some udev or logind babbling.

Tldr: systemd if you don’t want to bother, any other if you want to play

Good engeneering solutions are better than steering clear of hypocrisy. The rust zealots will happily tell you that this is just an implementation detail, YOU should write rust, because you will have no bugs, they instead need to ship, so concessions need to be made.

I mean, have you ever looked at any low level code from any language that came out in the last 30 years? Its always C.

Greybeard dev here, just stepping by to say I would do the same, this works and does nothing weird if there is nothing to commit.

I don’t know what the problem of the other crying person is, but robust IO watching should not be done in bash and whatever the fancy solution is it will not work as reliably as this.

Someone has to pay the bills, so they need to earn some money. If you ain’t paying you are the product is always a good metric, but in the email case the problem is also that a lot of the effort is manly IT admin rather than just the backend software.

You can roll your own dovecot and run your own emails at home in theory, in practice you need to be trusted by the major email providers to be able to send emails not tagged as malicious by anyone.

To protect their trusted status most providers collaborate on a lot of elements to be mutually sure they are not flooding each other with worthless spam. This is a lot of SPF, and other technical bullshit to be able to run a mail provider someone has to pay for

In case it is not clear: most use foss backend (dovecot or other), but this will not cover the whole software stack needed for an email provider

Flathub is crap

Snap is double crap

Docker would be useful if the networking wasn’t triple crap

You are completly missing my point.

I never said you should or should not do something, for all i care you can use wayland protocols in some hellbent way instead of systemd itself.

What I am saing is that it is bad form to complain the devs are not making what you want if you neither pay nor develop yourself to bring something to the table.

I said it the forth time now, I am out.

My point is they are not corporate overlords, that is the good thing smh

And yes, feature parity with a thing written in the eighties might not be a good idea either

Wayland devs develop stuff for wayland and most of them work for free, those that are payd are usually payd to do stuff that is needed by their employer. Spoiler alert: employers don’t give a damn about screensavers.

If you need additional stuff you need to either develop it yourself, or pay someone to do it for you.

This attitude of pressuring devs to do the work for you works if you pay for something, in opensource it is usually frowned upon.

People can complain all they like, if it ain’t useful to those who pay or those who work on it, it won’t be done.

In my opinion that is a feature not a bug.

Why are screensavers still used?

Nothing that causes pixels to change color “saves” anything these days, unless you have some kind of old LCD display.

Wayland has no limitations for how a traditional screensaver should work, nobody bothered to implement one, that is why there isn’t one yet IMO.

Hate to be the guy but if you need one you either need to hack something on top of xscreensaver like others in the thread said, or implement something native for those that need it to protect their old monitor.

That said, in case you don’t actually need a screensaver but a looping video for a kiosk type of situation you might just setup a videoplayer in a loop and turn off screen power saving.

Yes, screensavers are for sure among the top 300 features needed for this.

Cat too. It works largely the same way

This works. You can also cat image.iso >/dev/sdx

I always laugh at windows users with their external random apps to do something elementary

Its about sending the message: fuck ubuntu, w debian to the mint maintainers

All these projects for sure are cloned on multiple backups, if something happens and github is no longer viable it is a minimal effort to clone the source code and bug tracking and move it somewhere else. Serious projects will have contingenties in place for this, lesser projects will do what the big guys do

You seem to think that the idea is that linux and most FOSS projects are some carebear nonprofit charity organization. You are wrong.

In most cases the idea is that open source work is there because it is easier to share technological progress if multiple companies work at it. And because of this it is just better than the alternative. The linux kernel is worked on by multiple large corporations that are in the business of making money using servers. If these servers run better then they make more money. To make them run better for them they need to implement their features and because of the licence and the ecosystem they need to publish these modifications back to the upstream.

All this works so good because a lot of companies make a lot of money with it.

Github will be used as long as it does not interfere with the workflow or with the legal aspects, nobody cares about the spirit nearly as much as you think

Yet again a reminder that flathub solves a problem most people don’t have, and most users het confused with what it does.

We have had granular permissions for users on systems for 50 years, and virtual machines for 30 years, yet people keep using the wrong tool for the job just because the wrong tools keep getting popilar for some damn reason.

OP you are using your flatpack terminal wrong, the processes it launches do not inherit the constraints, or at least are not forced to follow them. Use a separate user account for that.

The main issue is that nobody is able to come up with anything better. I use systemd because it made my job hugely easier and soved many problems. The main guy is an asshole but his work is good when you use it as he intended, which kind of is the point of open source.

If you don’t like it you fork and do your own thing, until now nobody bothered, and this is telling.

Poettering did respectable work in snarky fields like audio and init nobody wanted to do something in and everybody complained about. I respect that despite he behaving like a spoiled asshole