Kacper Michajlow (HE12025-07-26): > I don't think moving over is something that requires significant > effort. It just needs clear communication about this. > > Also, I don't think the current ML workflow is very sophisticated on > ffmpeg-devel, so there are likely not many tools to migrate to the new > one.
A statement like that mostly shows a lack of experience with regard to projects like ours, i.e. projects that started at the time JavaScript was a bad joke and kept a stable kernel of developers over time. This lack of experience is corroborated by the use of GMail, something that is to real email what a Palyskool Plastic Toolbox is to a real tool set. Our current setup is in the spirit of Unix: we use multiple tools, each tool does one job and does it well and interacts well with other tools that do another job and do it well. These tools can be connected together to build complex processes efficiently. These forges are like Windows. They look nice and work out of the box is somebody else installed them for you, and simple tasks are very easy. But they require >50 clicks for any non-trivial task, and if something went wrong, you have to redo all >50 clicks after fixing it, because you cannot summon clicks from a command history. And if you want to automate because you are fed up with repeating >50 clicks every time, then your realize that the automation features you were assured where there only covers a third of the features you would need, only half of them are properly documented, and half of those do not actually work as documented. On the other hand, every single person who contributed a lot to the project since a long time have developed over the years our own workflow, our own automation. It can take many forms: shell scripts, macros in an editor or an IDE, pre-populating the shell with useful history lines, etc. Each person's workflow is tailored to our particular strengths (graphic / verbal / procedural memory, etc.). This has let us become very productive. More productive than anybody would be starting with these forges. Possibly more productive than anybody could become even after tuning these forges as much as possible to their needs. You are asking us to abandon most of that. I suggest you spend time learning better tool instead. -- Nicolas George _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
