another aspect is more practical. building a cli interface allows me to learn go, without the burden of simultaneously learning a gui tool/package. actually I have no idea what gui to to put in front of my first planned "real" app. learning cobra package isn't too bad. of course viper is next and you have the basic to test user functionality and app configuration. bolting on your tui packages is the next step in making it a bit more robust and distributable to my peers. learning new technology on a thin budget of time after work/life almost makes this essential to actually leveling up the professional quality og my code. your content is great eye opener on making a robust tui.i get new idea all the time.
Your project is amazing. I wrote for myself and my team (DevOps) a bash CLI using your charm CLI for managing aws profiles and refresh tokens, and I will implement an EKS context switcher as well. All profiles are read from the existing AWS/EKS configuration files, so it's entirely dynamic. I probably will publish it soon so everyone could use it.
As someone who's been using the terminal since at least 1992, maybe earlier, the reason why I like the terminal *in 2023* is... ALLLLL THE PRETTTTTTTTTTYYYY COOOOOLLLLOOOOORRRSSSS!! 😂😂😂
I personally just use whatever I get used to but some things are really more efficient on the command line. I guess other things would be too, I'm just too lazy to learn/set up stuff. :P In IDEs I use a bunch of hotkeys but also click around some. Also, things like git diffs are prettier in IDEs than the builtin command but I sometimes use git in a terminal for a more complex operation or if I don't actually need an IDE for the project (like simple scripting or just compiling a large project I cloned).
another aspect is more practical. building a cli interface allows me to learn go, without the burden of simultaneously learning a gui tool/package. actually I have no idea what gui to to put in front of my first planned "real" app. learning cobra package isn't too bad. of course viper is next and you have the basic to test user functionality and app configuration. bolting on your tui packages is the next step in making it a bit more robust and distributable to my peers. learning new technology on a thin budget of time after work/life almost makes this essential to actually leveling up the professional quality og my code. your content is great eye opener on making a robust tui.i get new idea all the time.
You forgot the most important reason
COOL
So everyone thinks you're a hackermans 8)
Great Job Bash!
Thank you!! :)
Your project is amazing. I wrote for myself and my team (DevOps) a bash CLI using your charm CLI for managing aws profiles and refresh tokens, and I will implement an EKS context switcher as well. All profiles are read from the existing AWS/EKS configuration files, so it's entirely dynamic. I probably will publish it soon so everyone could use it.
Please let us know when you publish it! That sounds like a great tool that the team would love to see 😄✨
Using a terminal and a tiling window manager. Great workflow for me.
As someone who's been using the terminal since at least 1992, maybe earlier, the reason why I like the terminal *in 2023* is... ALLLLL THE PRETTTTTTTTTTYYYY COOOOOLLLLOOOOORRRSSSS!! 😂😂😂
TRUE
also you can use command line in arch btw
$ sudo btw
8)
great video!
LOL! Bashbunni is as cute as bunny!😄
I personally just use whatever I get used to but some things are really more efficient on the command line. I guess other things would be too, I'm just too lazy to learn/set up stuff. :P
In IDEs I use a bunch of hotkeys but also click around some. Also, things like git diffs are prettier in IDEs than the builtin command but I sometimes use git in a terminal for a more complex operation or if I don't actually need an IDE for the project (like simple scripting or just compiling a large project I cloned).
I use CLI btw
First time I see bash bunny outside of TJ channel
Welcome to another bunni corner of the Internet