+- Hack Forums (https://hackforums.net)
+-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444)
+--- Forum: Coding (https://hackforums.net/forumdisplay.php?fid=151)
+---- Forum: Software Development (https://hackforums.net/forumdisplay.php?fid=118)
+---- Thread: CLI vs GUI vs Auto (/showthread.php?tid=6277112)
Pages: Pages
1
2
CLI vs GUI vs Auto - Hackers - Aug 6, 2024
Do you enjoy writing programs that run automatically (script, no interaction), or do you prefer some interaction? For me i think it’s situational, of course.
For CLI vs GUI, the decision can be based on a lot of factors. However, I feel that many times go for a GUI when a CLI tool is actually more than enough. On the other side, some people make insanely complicated CLI programs that could be better with a GUI - this of course also depends on who the users are.
What do you think?
RE: CLI vs GUI vs Auto - globalroot - Aug 8, 2024
A CLI is needed when you need to finish your job ASAP. For example, taskkill. Just its arguments "taskkill /f /im chrome.exe". Or sending basic requests for testing with cURL. A GUI is needed when the shit gets complicated. I wouldn't use tasklist instead of System Informer for example.
That's how it should be, in my opinion.
RE: CLI vs GUI vs Auto - SovietBastard - Aug 8, 2024
in no case a GUI will be better then CLI, by definition GUI is slower and eats up a lot of resources, if you have 8gb ram and you use a gui that eats half of that, you should just use CLI, i don't know, maybe this is personal opinion, but if i have to run some code having the choice between gui and cli i would always chose the cli, spares more resources and it is faster, + it gives you a more technical advantage
RE: CLI vs GUI vs Auto - happygonutty - Aug 8, 2024
I would say I would prefer GUI if it needs to please customers and clients but if you want something done in just a few keystrokes then go with CLI. The would be choice always depends on the preference of the audience or how demanding the results are.
RE: CLI vs GUI vs Auto - SovietBastard - Aug 8, 2024
(Aug 8, 2024 04:09 PM)happygonutty Wrote: I would say I would prefer GUI if it needs to please customers and clients but if you want something done in just a few keystrokes then go with CLI. The would be choice always depends on the preference of the audience or how demanding the results are.
you sound like Jeff bezos
RE: CLI vs GUI vs Auto - happygonutty - Aug 9, 2024
(Aug 8, 2024 05:00 PM)SovietBastard Wrote: you sound like Jeff bezos
Lol. Explain, I am curious? 🙃
RE: CLI vs GUI vs Auto - SovietBastard - Aug 9, 2024
(Aug 9, 2024 01:05 AM)happygonutty Wrote: Lol. Explain, I am curious? 🙃
sure, when someone talks about customer-support, client-request, job profit, etc... that is Jeff :D
RE: CLI vs GUI vs Auto - happygonutty - Aug 9, 2024
(Aug 9, 2024 01:31 AM)SovietBastard Wrote: sure, when someone talks about customer-support, client-request, job profit, etc... that is Jeff :D
I still don't understand your humor but anyway, here is a quick love for you. 🙃
RE: CLI vs GUI vs Auto - Phantom_NiNja - Aug 10, 2024
(Aug 6, 2024 08:41 PM)nodes Wrote: Do you enjoy writing programs that run automatically (script, no interaction), or do you prefer some interaction? For me i think it’s situational, of course.
For CLI vs GUI, the decision can be based on a lot of factors. However, I feel that many times go for a GUI when a CLI tool is actually more than enough. On the other side, some people make insanely complicated CLI programs that could be better with a GUI - this of course also depends on who the users are.
What do you think?
It depends on the situation. I write programs but do have scripts like clean stuff up or check stuff and makes files and deletes files and folders too.
My scripts could have CLI interactions it needs to be like to ask are you sure you want to remove such files.
I think all have purposes. I do like GUI's but..
For me most of the time I Write CLI scripts and then after so many improvements. I convert it to a GUI program when it get too complicated meaning too many options where a CLI would be too confusing to navigate. I then would created a GUI app and use the functions and stuff inside.
That's normally my flow. Figure out what kind of program to make. write it first in cli language. bash, batch, then add features to it when needed. Once it grows big then convert it to a GUI.
RE: CLI vs GUI vs Auto - DeltaNox - Aug 12, 2024
Well, the thing is that the majority of people expect a GUI. Most people don't even know how to use cmd window unless they have linux they'd probably have some basic understanding of the terminal. Still, smartphones and tablets are growing in popularity and a lot of people I know don't even use PC's anymore. So if you're developing a tool for someone else, you'll probably need a GUI because that's all they know. This is of course unfortunate for the developer as it requires more work, especially cross platform. But if I'm developing something for myself I don't really care so I'll just use CLI unless it'd be really convenient having a few buttons and textboxes.
RE: CLI vs GUI vs Auto - Hackers - Aug 12, 2024
(Aug 12, 2024 04:21 AM)DeltaNox Wrote: Well, the thing is that the majority of people expect a GUI. Most people don't even know how to use cmd window unless they have linux they'd probably have some basic understanding of the terminal. Still, smartphones and tablets are growing in popularity and a lot of people I know don't even use PC's anymore. So if you're developing a tool for someone else, you'll probably need a GUI because that's all they know. This is of course unfortunate for the developer as it requires more work, especially cross platform. But if I'm developing something for myself I don't really care so I'll just use CLI unless it'd be really convenient having a few buttons and textboxes.
I also like the idea of doing both
You can set up the main function to accept params, or use a GUI if none are supplied.
However this is a niche use case and isn't as common
Agreed overall - people really aren't using PCs as much. Kids these days don't understand what you can or can't do, it's all packaged neatly for them in an app. It's a shame, we may end up with a future where there is not enough profit in computers to justify the development. Already this trend is true in many niches, where mobile becomes the higher priority.
If a large % of the world doesn't buy computers, eventually people stop producing computers & computer software.
I hope that day never comes - luckily there are enough servers and enterprise companies to justify a computer industry. If it was only based on consumers, that would be scary.
RE: CLI vs GUI vs Auto - SovietBastard - Aug 12, 2024
(Aug 12, 2024 08:00 AM)nodes Wrote: I also like the idea of doing both
You can set up the main function to accept params, or use a GUI if none are supplied.
However this is a niche use case and isn't as common
Agreed overall - people really aren't using PCs as much. Kids these days don't understand what you can or can't do, it's all packaged neatly for them in an app. It's a shame, we may end up with a future where there is not enough profit in computers to justify the development. Already this trend is true in many niches, where mobile becomes the higher priority.
If a large % of the world doesn't buy computers, eventually people stop producing computers & computer software.
I hope that day never comes - luckily there are enough servers and enterprise companies to justify a computer industry. If it was only based on consumers, that would be scary.
i wouldn't be so worried about computer future, computers will never get away, life is just tech as we know it, there is tech everywhere, and wherever there is tech, there are computers, a mobile phone would never be able to run a server or a large language model like a computer, there is need for a lot of power, i would think another way, i would think that computers will become more and more required instead of extinct as we depend on them too much already
RE: CLI vs GUI vs Auto - DarkVision - Aug 12, 2024
(Aug 6, 2024 08:41 PM)nodes Wrote: Do you enjoy writing programs that run automatically (script, no interaction), or do you prefer some interaction? For me i think it’s situational, of course.
For CLI vs GUI, the decision can be based on a lot of factors. However, I feel that many times go for a GUI when a CLI tool is actually more than enough. On the other side, some people make insanely complicated CLI programs that could be better with a GUI - this of course also depends on who the users are.
What do you think?
I couldn't agree more with your observation about GUI vs. CLI; how it's puzzling why some projects that would benefit from a GUI lack it, and vice versa.
As for my own development, i often find myself having a "I would love to" attitude towards the CLI or "under the hood" parts of the development process, and a "I have to" attitude towards the GUI part. In my opinion, it's simply not as fun to "tinker" with the GUI and controls.
Hoping for MSDOS to return. 🙂
RE: CLI vs GUI vs Auto - Mаtt - Aug 12, 2024
I'm going to say it depends on the audience. If we are talking about a program that is used for day-to-day tasks with a lot of customizable options, I would prefer a GUI. I can't imagine trying to write my school papers in a CLI when I want to change anything from the font-size, indent, format, etc.
Whereas if I am doing a CTF, I definitely prefer CLI / Terminal based tools. I only use GUI if it's for an analysis of some kind or if there's hundreds of lines of text to analyze.
RE: CLI vs GUI vs Auto - SovietBastard - Aug 13, 2024
(Aug 12, 2024 03:16 PM)Mаtt Wrote: Whereas if I am doing a CTF, I definitely prefer CLI / Terminal based tools. I only use GUI if it's for an analysis of some kind or if there's hundreds of lines of text to analyze.
is easier but you can do that with cli as well