This pairs very neatly with cool-retro-term[1] :-)
WTF – A personal information dashboard for your terminal
101–110 of 182 posts
Re: WTF – A personal information dashboard for your terminal
#102Honestly curious - why do people live mostly in their terminal? Is it a productivity thing?
Familiarity and low resources needed .. I can use a $5/year natted VPS and program (via Git/Vim), run scripts, surf the web (links), chat on IRC (Weechat) and continue my Tmux/Screen workflow on basically any *nix machine with at least ~16MB memory.
why do you need to use low resources?
Re: WTF – A personal information dashboard for your terminal
#103Honestly curious - why do people live mostly in their terminal? Is it a productivity thing?
In my experience, it is easier to automate a workflow using command line applications. The GUI versions of tools have to try and predict every possible workflow, while terminal applications can be easily combined in scripts. That being said, there are definitely major productivity features to be had with GUIs, such as those with web browsers and IDEs.
what's an example of a workflow you've automated on a terminal?
Re: WTF – A personal information dashboard for your terminal
#104There's a detailed screenshot but I can't zoom to see the detail because the website designer has gone the extra mile to make it non-zoomable. Why do people do this?
I was able to click on the screenshot to open it up in a modal, and that was zoomable.
Re: WTF – A personal information dashboard for your terminal
#105Honestly curious - why do people live mostly in their terminal? Is it a productivity thing?
In my experience, it is easier to automate a workflow using command line applications. The GUI versions of tools have to try and predict every possible workflow, while terminal applications can be easily combined in scripts. That being said, there are definitely major productivity features to be had with GUIs, such as those with web browsers and IDEs.
But this application loses all those benefits, since it's just a GUI that happens to be displayed in ASCII on a terminal.
Re: WTF – A personal information dashboard for your terminal
#106This pairs very neatly with cool-retro-term[1] :-) [1]: https://github.com/Swordfish90/cool-retro-term
Someone please install this and try it and take a screenshot. I just want to see it but don't want to do it myself haha
Re: WTF – A personal information dashboard for your terminal
#107Earlier quoted context omitted.
In my experience, it is easier to automate a workflow using command line applications. The GUI versions of tools have to try and predict every possible workflow, while terminal applications can be easily combined in scripts. That being said, there are definitely major productivity features to be had with GUIs, such as those with web browsers and IDEs.
But this application loses all those benefits, since it's just a GUI that happens to be displayed in ASCII on a terminal.
I would imagine if someone sat down to create a dashboard for the browser, it would take as much if not more work, and building interaction with each element would be a whole new thing altogether.
I think the purpose of a dashboard is not to give you detailed interactions, but to let you know the status and you can take actions outside the dashboard as you like.
Moreover, not so sure about this application but you can always have key shortcuts to take you to run a default task for one of the sections of the dashboard. Hence, imo, there is no real loss of functionality here.
Re: WTF – A personal information dashboard for your terminal
#108Honestly curious - why do people live mostly in their terminal? Is it a productivity thing?
It is a productivity thing. CLI tools have consistent interfaces and once you are familiar with the common tools and workflow, it is considerably faster to do what you are looking to do. One particular trait that has personally made my workflow a lot faster is being able to repeat a command from history (by pressing Ctrl-R) and then writing only part of the command to run it. It saves a lot of time and makes it less cumbersome to type in very long commands.
Now to contrast this with GUIs, even the simplest things would require me to jump through menus, type some stuff, etc. Everything in the command line is precise and repetitive steps are easy to replicate.
Piping is another aspect that the command line enables, which basically feeds to output of one command into another. One common example of this is to look at lines of a log file that contain a certain set of words: `cat log.txt | grep "[ERROR]"`.
But perhaps the strongest selling point of working in the command line is consistency among tools. If you want to be productive as a developer, use of various tools for doing various tasks is common. Using the CLI for all these tools keep everything a few commands away, even interoperability is enabled seamlessly due to piping and consistency.
So yes, there is a fairly steep learning curve, but in my opinion learning how to use CLI tools over GUI is well-worth the hassle.
Re: WTF – A personal information dashboard for your terminal
#109Honestly curious - why do people live mostly in their terminal? Is it a productivity thing?
Familiarity and low resources needed .. I can use a $5/year natted VPS and program (via Git/Vim), run scripts, surf the web (links), chat on IRC (Weechat) and continue my Tmux/Screen workflow on basically any *nix machine with at least ~16MB memory.
How beneficial is surfing the web in 2019 with links? I was just using it yesterday on a raspberry pi zero and couldn’t download go from the very minimal golang.org site. I couldn’t imagine trying to use it day to day.
Re: WTF – A personal information dashboard for your terminal
#110Earlier quoted context omitted.
In my experience, it is easier to automate a workflow using command line applications. The GUI versions of tools have to try and predict every possible workflow, while terminal applications can be easily combined in scripts. That being said, there are definitely major productivity features to be had with GUIs, such as those with web browsers and IDEs.
what's an example of a workflow you've automated on a terminal?
-> download 1000 files using curl, then validate their checksum, then build stuff
-> take an almost-CSV report generated by one piece of software, remove a bunch of extra garbage at the top to turn it into an actual CSV file, then send the CSV file to data analysis pipeline.
-> join two CSV files selecting columns 2,3 from one file and 4,5 from the other file, keyed on column 1 from both files. like excel but for CSV files sized in hundreds of megabytes
-> take a bunch of CSV files and pump them into a rabbitmq queue
-> query whether a queue is empty. if so, start a new analysis job. if not, sleep another hour
-> grep for data in a directory to find specific files containing that data, then point those paths to another service
I can go on all day. CLI tools are far more wieldy than GUI tools IMO. CLI tools give me a generally-stable interface (or at the very least, a straightforward method of parsing and adapting to changes) and usually have _way_ better documentation than GUIs.