<!DOCTYPE html><html><head><title></title><style type="text/css">
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Fri, 28 Aug 2020, at 09:55, Rémi Denis-Courmont wrote:<br></div><blockquote type="cite" id="qt" style=""><div>It's patently obvious that some people do need/want scheduled VLC usage. But it's also obvious that they don't use VLM schedules for that.<br></div></blockquote><div><br></div><div>No, it is not obvious that they don't use VLM for that. I've seen numerous usages over the years of people using that.<br></div><div><br></div><blockquote type="cite" id="qt" style=""><div>They use custom wrappers and/or OS services (e.g. crond), via CLI, RC or HTTP.And that's the right way to do it. Afterall, <br></div></blockquote><div><br></div><div>Not all of those exist on all the OS we support.<br></div><div><br></div><blockquote type="cite" id="qt" style=""><div>VLC can't persist and automatically start or restart itself anyway. It can't even handle non-UTC civil time, nor weekdays. FFS, it doesn't even warn about pending schedules when you try to quit it.<br></div></blockquote><div><br></div><div>All this is true.<br></div><div><br></div><div>But I still object: removing this VLM feature opens the removal of all the depend code, notably scheduling for recordings. And then, when we need to add the feature back, it will be 20x time harder to put it back, because people will object about this. Bugs must be fixed, instead of removing features.<br></div><div><br></div><div>So, no, I totally disagree.<br></div><div><br></div><div><br></div><div id="sig60240713"><div>--<br></div><div>Jean-Baptiste Kempf - President<br></div><div>+33 672 704 734<br></div><div> <br></div><div><br></div></div><div><br></div></body></html>