Yes, very funny that these fields have existed for decades but no one knew about it, but suddenly everyone is freaking out because a birthday field has been added.
Sure, let's just pretend that this is totally unrelated to the laws currently being made and implemented that require the operating system to provide user age to applications and websites for age restriction. After all, all those Gecos fields people have filled have been shared across the internet all those years, oh wait never mind, they didn't, and they aren't really being used at all.
Seriously though, what's your point? Can't you see any difference here?
I'm not suggesting anything specific. But the point of rushing to implement your way into software A to prevent each software having their own implementation does not make sense to me. This is not a proper way to standardise. There are many months left to make a proposal that works for everyone.
He thinks it'd be worse if every desktop environment implements their own solution to comply with these laws.
Sure he has a point there, but putting it in systemd means there will need to be at least one other implementation for systems that don't use systemd...
Well sure, software gets forked and continued all the time, but there's quite a stark difference between just using open source software or actively maintain it. Not everyone is a software developer, so I still don't see why "just fork it" is the answer. Those who have the capabilities probably already thought of it no?
I hear this argument a lot about many things but how is "just fork it" the answer? It's not like just anyone can fork any project and continue developing it. The alternative would be forking it and consider it final version or what?
I know where this is, they return here every year! It's amazing that they chose this place as it's quite close to the highway.