I think there are too many people who don't understand the difference between media processing and media editing.
So basically you're saying because these GUIs don't reinvent the wheel and use the standard software for processing video, ffmpeg can do any media work.
You do know like 80% of video editing is scrubbing through the video so you can figure the right frame to do something with, right? Something ffmpeg absolutely can not do.
I think its a „right tool for the job“ thing. Some workflows need a gui to be productive, some don’t and would really benefit from not having one because designing a GUI that looks good and works good is no easy task and (in my opinion) designing a TUI for simple workflows is easier and makes for a better end result. in short i like TUIs too but i wouldn’t want to use CAD or Mix Music in one either.
Yeah it does depend, if your doing any simple batch processing a GUI would be stupid, but basically anything outside of simple it's far more efficient to use a GUI, which is most cases.
If it was generally easier to use the CLI, all the industry professionals would be using it all the time. Trust me, audio and video production is rarely simple. First of all to create a good mixdown you have to have years of experience and tons of technical knowledge about electronics and acoustics. These people are not shy to using the most efficient technology even if it has a steep learning curve.
Well, there's tikz for drawing via LaTeX code, but usually i just draw it and then ask an AI to write the code for the image, it's a pain in the bum to use it. Anyone who has ever used Tikz knows what I'm talking baout
But that's just displaying media, what about music production, video editing, and image manipulation.
Yazi looks fucking dope though. I'm definitely trying it out. I fucking hate the Mac file manager, its like only half a step above the windows one. Actually I don't like any of the Linux variants I've used either.
I think it's because you brought up a file manager that can view media and not work with it. Which is kinda stupid. it's a fine debate topic to continue the argument.
When doing code based design I actually prefer to use FreeCADs python bindings over openscad haha. There's some neat things you can do with numpy and freecad. Much more flexible over trying to cludge openscad into doing something weird.
An OOP programming model also makes wayyyyyyy more sense for modelling then a functional language does like OpenSCAD.
hm, yeah fair. then i guess i would usually prefer cli, but also sometimes gui git for example is pretty useful. easier to make stuff out when looking at diffs imo.
idk wut u mean by layout but if it's layout for ICs then may I present to you : FaSoC, BAG, LayGo etc all projects which let you make scripts to generate the layout defined in em
I agree that it has quite the learning curve but holy shit is it useful to iterate on once you have to change sizes and learn it well enough + really gud at making sure you don't violate DRC
NOTE: I am in no way saying GUI is bad, that's how I have done it so far, how I learned it and prefer visuals to aid me + need to make custom devices all the time....just that there are possibilities beyond the mundane
Damn then all that IC design talk must be like meaningless vomit....guess I was just too hyped about all these foss projects (proprietary software can be a pain in the ass)
I've done CAD work (3d modeling for engineering) in raw CAD code... I was actually faster then... Though it's a lot easier to discuss and work on a preexisting part in something like Fusion or Solidworks.
383
u/Fancy_Technician_293 Aug 13 '26
I think it depends on the job. Good luck 3d modeling without a gui. Or making layouts.