Are CLI applications relevant today? does anyone build CLI apps over apps with GUIs...

are CLI applications relevant today? does anyone build CLI apps over apps with GUIs? do people even use CLI apps minus a python interpreter or mysql cli?

Other urls found in this thread:

github.com/andmarti1424/sc-im
twitter.com/SFWRedditGifs

no
no
no

not ever?

no!

You dropped your avatar, idiot.

Im using

>are CLI applications relevant today?
It fucking is, most of the software written to this date is created by CLI applications

your dumb

When I was a sysadmin I pretty much spent all day at a powershell CLI.

You forgot the OP, shitheel.

baka

cli makes me feel like a smart hacker when i use it
GUI doesnt scare away the normies. IT wages are probably going down once everything is perfectly reliable from the gui.

a cli spreadsheat application would be god tier

sc

yes. cli is great whenever you need to automate anything. and when youre used to it, much more convienent then point and click and drag.
gui is good for manual use, and for amateurs,
but its often very limiting if you want to have your computer work for you.

you can easily create a gui wrappers around a cli program, which gives you the benefits of both, so its often the best choice to develop a lot of programs as

sc-im github.com/andmarti1424/sc-im

No they aren’t relevant

Yes they do in LOONIX land.

Yes they do in LINCUX land.

It’s a way to signal to the other lintards that they are members of the same, much like a blue bubble on an iPhone.

The shitnux fanboys and Apple fanboys are so alike, you don’t even know.

Define CLI, do you mean small one-task apps which can be assembled into a powerful task by combining IO of several apps, or into a script? Or do you mean a tryhard curses hipster bullshit trying to be a DOS app from 89?

>curses

that's called a TUI not a CLI

op here. i was making a cli app that allows for easily applying various transformations to pixel arrays. i'm working on edge detection algorithms and i was finding it annoying to manually change filter settings, applying different types, etc. so i made a CLI that you can load images into, apply various filters/transformations, and draw the subsequent image without having to close the script, change parameters, and reload the script.

currently, you can add as many images you want into 'memory' by storing it within an array and then giving it a special name. you can change your working image and apply various filters, save it, and redraw at will. then you can load different images, draw, and compare the outputs.

i programmed specific 'commands' that you can issue and it allows you to do various things like an image convolution, gaussian blurs, sobel magnitude, difference of gradients, etc. and you can apply them in different orders to get different outcomes.

eventually you can apply a canny edge detector on these images and see which does the best. it logs the transformations done so you can easily get a code snippet that does exactly what you did to get to that image

Linux
Yes, yes and yes. it gives you the ability to bash script but if you're not into that a terminal can sometimes be more comfy than a gui.

Windows
Not really, maybe some innovative new shit that developers make before giving to computing novices. Some exceptions to this are altcoin clients like monero.

FWIW not so long ago many great Unix apps were a cli, and the GUI was just a wrapper for checking off flags and applying the command to a batch of files from the file selector. Now these things are often more tightly integrated with the gui being part of the command but optional, allowing scripting.

Although I think back to the AmigaDOS2 days when applications were wholly GUI and presented an AREXX API port, allowing you to glue together your application with AREXX scripts. Pretty interesting concept and much cleaner than the shitty object buses that modern systems have.

Really, a CLI is just an easy, human-friendly wrapper for a library. Give it a function and it's arguments, and it will give a result. You could make a GUI too, but often times this is cumbersome and impractical.

And of course CLI programs are much easier to make than GUI programs.

When I build tools for my own use, I make them CLI only unless they strictly need graphics for their intrinsic functionality (like, an image viewer). It's much more convenient to use, and it's far, far more convenient to write.

CLI is used extensively in Linux, so yes.

I am writing a program to map acceleration to a line or curve equation for cli use in key remapping. am i reinventing the wheel or can octave do the same thing?

Yes.

plz elaborate

do people typically use off the wall CLIs that have their own custom naming conventions and functions? i feel like there is a learning curve on learning a specific api/cli so i feel like most arent inclined to just use any random CLI unless its really good

considering that I need CLI to compile GUI programs

yes if you are not an end user

They are used extensively by sysadmins, pen testers, and programmers who aren't pajeets. So yes they are very relevant.