Hey guys,
I was wondering what your preference and experience was with command line interface and graphical user interface. My first exposure to a computer was PC Limited computer running MS DOS. I fell in love with CLI and didn't actua use a GUI OS until Windows 98SE when my parents bought an e-machine. It was an okay experience. Windows didn't wow me like DOS did.
I kept using Windows like most people till I attended vo-tech and discovered Linux. That rush I got from DOS was back in full force. Computers felt excit again. I was ecstatic that I could run and do anything I wanted from the CLI that would only work in the GUI on Windows.
Over the years I switched back and forth between Windows and Linux. The new in Vista felt sluggish and slow. 7 was alright and felt like XP. But Linux f a lot faster and speedier than either of the Windows out at the time. Then I saw Windows 8...
Windows 8 was the final straw for me in terms of using a GUI. The tiles are absolutely confusing and the placement of certain things is very unintuitive tried to help my grandmother with her Windows 8 computer and I had absolutel no idea wtf I was doing. I couldn't even find the shut down button even afte looking online. This flicking the mouse to the rightof the screen like a tab just to shutdown the computer is ridiculous. MS went too far with the GUI in I've heard people who enjoy it, but I can't wrap my head around it. I never thought I would see the day where Linux made more sense to me than Windows.
So I mostly do muds and started getting into bbs to keep my CLI skills sharp Sometimes I will surf the web with Lynx and play old DOS games in DOSbox. It familiar territory to me and I feel more comfortable seeing black and white text than fischer price tiles.
Which do you prefer? I'd love to hear your stories and experiences and what programs you use. Consider this a nostalgia thread if you want because I fee nostalgic everytime I open a Terminal.
---
þ Synchronet þ Decker's Heaven -//- bbs.deckersheaven.com
Offensive_Jerk wrote to physalis17 <=-
@VIA: VERT/RDBBS
@TZ: 41a4
Re: CLI vs GUI
By: physalis17 to All on Thu Nov 13 2014 03:15 pm
Hey guys,
I was wondering what your preference and experience was with command line interface and graphical user interface. My first exposure to a computer was PC Limited computer running MS DOS. I fell in love with CLI and didn't actua use a GUI OS until Windows 98SE when my parents bought an e-machine. It was an okay experience. Windows didn't wow me like DOS did.
I kept using Windows like most people till I attended vo-tech and discovered Linux. That rush I got from DOS was back in full force. Computers felt excit again. I was ecstatic that I could run and do anything I wanted from the CLI that would only work in the GUI on Windows.
Over the years I switched back and forth between Windows and Linux. The new in Vista felt sluggish and slow. 7 was alright and felt like XP. But Linux f a lot faster and speedier than either of the Windows out at the time. Then I saw Windows 8...
Windows 8 was the final straw for me in terms of using a GUI. The tiles are absolutely confusing and the placement of certain things is very unintuitive tried to help my grandmother with her Windows 8 computer and I had absolutel no idea wtf I was doing. I couldn't even find the shut down button even afte looking online. This flicking the mouse to the rightof the screen like a tab just to shutdown the computer is ridiculous. MS went too far with the GUI in I've heard people who enjoy it, but I can't wrap my head around it. I never thought I would see the day where Linux made more sense to me than Windows.
So I mostly do muds and started getting into bbs to keep my CLI skills sharp Sometimes I will surf the web with Lynx and play old DOS games in DOSbox. It familiar territory to me and I feel more comfortable seeing black and white text than fischer price tiles.
Which do you prefer? I'd love to hear your stories and experiences and what programs you use. Consider this a nostalgia thread if you want because I fee nostalgic everytime I open a Terminal.
---
= Synchronet = Decker's Heaven -//- bbs.deckersheaven.com
I would have to agree on the Windows 8 interface.... Complete trash.
So confusing. I also had no idea what I was doing when I was trying to work on it.
---
= Synchronet = RetroDigital BBS - rdnetbbs.com
Jazzy_J wrote to Offensive_Jerk <=-
Which do you prefer? I'd love to hear your stories and experiences and what programs you use. Consider this a nostalgia thread if you want because I fee nostalgic everytime I open a Terminal.
My biggest nod to Windows 10 is the cli. After decades, they finally
gave us a shell that I can expand way past 80 columns. Additionally,
they are incorporating a BASH shell from Ubuntu that is compiled
natively. You can edit the repos and everyting. Although X programs cannot work at the present time, the ncurses and other terminal-based
apps work beautifully. I actually removed *nix from my personal laptop and used 10 for about a year. I'm back to *nix on my laptop as
managing my services is just plain easier with a *nix system.
Performance wise, a well developed cli with a knowlegeable developer is considerably more powerfull than any gui I have ever used, and faster.
With this knowlege, Microsoft has worked on Powershell considerably. I haven't found something that I couldn't script with PS, yet. It is a beautiful, albeit confusing as hell at first.
I was a key player/developer in the migration of 15,000 XP systems to Windows 7. There were somethings that we could not do with the
gui-based system. However, you could call a script. VBscript to the rescue. The system would take control of the end-point. From there,
we would call our scripts and accomplish the tasks as needed.
BASH is my shell of choice, out of laziness. It was the first one I
ran into when I started using *nix (very early versions of RedHat,
Debian and Slack.) I learned it and stuck with it. I guess I should
get off my duff and learn other shells, but it works for me, so the motivation is low.
The cli in Windows 10 is well developed, but still not as good as BASH.
A brief thing about Win10 Desktop: Microsoft has upped the
configurable options in it and you can run it pretty lean. I find it running better on certain models that drag with 7. 8 was a joke and
not worth comparing. MS filled it with cycle- and memory-eating fluff.
10 is done much better. Although, it is like running Fedora in the Enterprise. In my test beds you basically are rebuilding the system
with every major "feature release." Downtimes to migrate are about 2-3 hours and require user interaction. This is beyond bad.
Jazzy_J wrote to Offensive_Jerk <=-
Podcast recorder - this is a 100% self maintaining system. At set times,
it records off air from a local radio station, so I can make podcasts of selected shows (all with the the permission of both the station and the proesenters of the programs that I podcast). This system also has a backup facility, which captures the streaming audio from the station and saves that, in case something goes wrong with the off air recording (real world cases include the cat disconnecting the antenna and a link failure at the station). The system deletes the off air recordings weekly, and the stream captures (being compressed) are kept for 4 weeks. Maintenance scripts run from cron look after this.
Vk3jed wrote to Jazzy_J <=-
Podcast recorder - this is a 100% self maintaining system. At set
times, it records off air from a local radio station, so I can make podcasts of selected shows (all with the the permission of both the station and the proesenters of the programs that I podcast). This
system also has a backup facility, which captures the streaming audio
from the station and saves that, in case something goes wrong with the
off air recording (real world cases include the cat disconnecting the antenna and a link failure at the station). The system deletes the off air recordings weekly, and the stream captures (being compressed) are
kept for 4 weeks. Maintenance scripts run from cron look after this.
... The most popular labour-saving device today is still a husband with money. --- MultiMail/Win32 v0.49
= Synchronet = Freeway BBS in Bendigo, Australia.
Ennev wrote to Vk3jed <=-
What is Podcast recorder ? As a super simple low tech linux solution
I'm using bashpodder. ( http://lincgeek.org/bashpodder/ ) I cron this
on this box and get some podcast this way. It all in bash so super easy
to adapt and modify.
Jazzy_J wrote to Vk3jed <=-
I absolutely love the podcast recorder idea. I picked up a server out
of the trash and it seems I can run an unlimited (overstatement, I
know) number of *nix vms on it, but dear Lord. If I put 2 Windows 7
vms on it.... forget it. (not an overstatement, 2 shuts the server down
to a crawl). I can tune the *nix vms to use under 512 MB. and that is giving them comfortable room. I dedicate a healthy portion to the
MySQL and Apache vms (in case someone ever visits my web sites....) but the background data-acq and process servers run beautifully on minimal resources.
I do suggest these two things:
1) get busy with windows 10. I have a bad feeling that MS is going to bolt on Win 7 support. My suspicion is based on the veracity that MS
is dogging Win 10. I feel they are going to use a ploy very similar to the Win XP Driver SNAFU, but in reverse. When XP was introduced,
getting drivers "Microsoft Certified" was a huge issue. I see MS, not certifying drivers for Win 7 after some date, there-by forcing people
that would want to put 7 on new hardware, no option but to run 10. I
hope I'm wrong. It's just a feeling I'm getting.
2) Reportedly, Processors released after October 2017, will not have
BIOS support for anything except UEFI.
Building systems with UEFI are not that terrible, but it is different.
I would rather be versed in the problems with UEFI than not be able to deal with anything but legacy hardware.
However, the command line is generally by far the more powerful option, providing the OS offers a decent shell (these days, that's true of Windows, as well as Linux and OS X). The command line also lends itself to automation. With GUI apps, you usually have to have the automation built in (though VBScript often does help on Windows), while on the command line, you an write a fairly clever script and have it do as much as possible automatically. If it needs to run at a specific time, the system's scheduler can arrange that.
irEnnev wrote to Vk3jed <=-
What is Podcast recorder ? As a super simple low tech linux solution I'm using bashpodder. ( http://lincgeek.org/bashpodder/ ) I cron this on this box and get some podcast this way. It all in bash so super easy to adapt and modify.
I'm not sure we're trying to do the same thing. My setup records both off a
and streaming audio, which is manually edited down and compressed for uploadto
podcast sites.
I'm not sure what your're doing with your setup.
... Cursor: An expert in four-letter words
There are ways to automate a GUI without having to have it built in. AutoIt is a tool for Windows that lets you write scripts to automate GUI actions, I've seen a similar tool on OS X. A GUI app normally exposes the IDs of
all of the GUI elements, and it's possible for other apps to find those elements and work with them.
Nightfox
Nightfox wrote to Vk3jed <=-
There are ways to automate a GUI without having to have it built in. AutoIt is a tool for Windows that lets you write scripts to automate
GUI actions, I've seen a similar tool on OS X. A GUI app normally
exposes the IDs of all of the GUI elements, and it's possible for other apps to find those elements and work with them.
Ennev wrote to Vk3jed <=-
Oh!, mine is dealing onlt with podcast base with rrs feed, it's not dealing with real time streaming. For real time I was doing it manually with audacity, but havent done that with ages. My approach must be
dusty.
I use streamripper to capture streaming audio off the net. Some sites have got clever and started blocking it, but you can tweak the user agent
setting and make it look like a copy of Winamp or something else, which satisfies the server. :)
Offensive_Jerk wrote to physalis17 <=-
I would have to agree on the Windows 8 interface.... Complete trash.
So confusing. I also had no idea what I was doing when I was trying to work on it.
Jazzy_J wrote to Offensive_Jerk <=-
The cli in Windows 10 is well developed, but still not as good as BASH.
Ennev wrote to Vk3jed <=-
I use streamripper to capture streaming audio off the net. Some sites have got clever and started blocking it, but you can tweak the user agent
setting and make it look like a copy of Winamp or something else, which satisfies the server. :)
Interesting. Will have a look :-)
When I ran Windows 8, I ran Classic Start Menu, and replicated m
Windows 7 look and feel. I bit the bullet and upgraded to Windows 10,
and I'm fine with the new start menu. It just took time for me.
Ditto with office apps. I used Office 2007 with an add-on that gave
you a standard menu bar. With 2010 I was mostly OK without it. Office
2016 has a search bar, which they should have done a long time ago.
Instead of hunting through menus, you can search for whatever tool you
need.
Have you tried powershell? The tools guys I work with swear by it.
I use streamripper to capture streaming audio off the net. Some sites have got clever and started blocking it, but you can tweak the user agent setting and make it look like a copy of Winamp or something else, which satisfies the server. :)
Man, I tried Classic Shell and the start menu (to me, at least) just looked way out of place, regardless of what theme I choose.
Poindexter Fortran wrote to Vk3jed <=-
I started using the relay-agent feature, too -- let streamripper rip
the stream and relay audio to WinAmp, too. I didn't want to have 2
inbound streams showing up in the firewalls.
Poindexter Fortran wrote to Jazzy_J <=-
@VIA: VERT/REALITY
@TZ: 41e0
Jazzy_J wrote to Offensive_Jerk <=-
The cli in Windows 10 is well developed, but still not as good as BASH.
Have you tried powershell? The tools guys I work with swear by it.
jagossel wrote to Poindexter Fortran <=-
I wanted to look into using PowerShell Core on my Antergos GNU/Linux system, but between a bad wireless adapter and the fact that
Microsoft's servers does not support resuming downloads makes it hard
for me to even get it.
-jag
Lofi-Samurai wrote to physalis17 <=-
It may very well be anathama but I prefer OSX. I've used all kinds of
CLI based OSs over the years from a commie Vic=20 to my last DOS 486. Switched to GUI with Windows 3.1 upto 10. Rolled my own Linux and 'next-next-finish'ed plenty of Ubuntu/RedHat/Mint installs. Setup a few hackintosh boxes. (They don't run all that well though)
Re: CLI vs GUI
By: physalis17 to All on Thu Nov 13 2014 03:15 pm
It may very well be anathama but I prefer OSX. I've used all kinds of CLI based OSs over the years from a commie Vic=20 to my last DOS 486. Switched to GUI with Windows 3.1 upto 10. Rolled my own Linux and 'next-next-finish'ed plenty of Ubuntu/RedHat/Mint installs. Setup a few hackintosh boxes. (They don't run all that well though)
With OSX you basically get all of the OSs you could ever want to use.
The GUI is top-notch. If CLI is your bag, the back end is (more or less) Debian Linux. If you need to run anything Windows, you can dual-boot or run it in an emulator.
Macs are expensive, but out of the dozens (if not hundreds) of computers I've dealt with over the years they've been consistent quality wise.
---
â– Synchronet â– RetroDigital BBS - rdnetbbs.com
But when it comes to servers, Linux wins hands down. I can run it without a GUI, meaning more resources for daemons, and scripting means one can do almost anything. Linux boxes are also much easier to run headless, thanks to SSH, screen and friends.
MacOS feels more like Windows than Microsoft's product does nowadays. It's feeling crufty in places, although I admittedly couldn't tell you quite what those places are.
MacOS feels more like Windows than Microsoft's product does nowadays. It's feeling crufty in places, although I admittedly couldn't tell you quite what those places are.
like a step backwards.. I liked the Windows 7 Aero as well as classic Windo which I think look better than Windows 8/8.1/10. And I liked OS X's appeara
Win8-> Start menu was designed for touch screens. (They want you to buy a X>Surface). It is still mediocre and unremarkable at even that. I would say tha X>it is a total fail on MS's part.
LoFi-Samurai wrote to Vk3jed <=-
I'm with you on the Linux, for sure. I can pack Linux servers into VMs
on a host with far more efficiency than Windows ones. And, although
Putty is pretty good I do like iTerm a little better for SSH
connections. Do you implement much in the way of web based GUIs for
Linux? phpmyadmin, etc..
Re: CLI vs GUI
By: physalis17 to All on Thu Nov 13 2014 03:15 pm
It may very well be anathama but I prefer OSX. I've used all kinds of CLI based OSs over the years from a commie Vic=20 to my last DOS 486. Switched to GUI with Windows 3.1 upto 10. Rolled my own Linux and 'next-next-finish'ed plenty of Ubuntu/RedHat/Mint installs. Setup a few hackintosh boxes. (They don't run all that well though)
With OSX you basically get all of the OSs you could ever want to use.
The GUI is top-notch. If CLI is your bag, the back end is (more or less) Debian Linux. If you need to run anything Windows, you can dual-boot or run it in an emulator.
Macs are expensive, but out of the dozens (if not hundreds) of computers I've dealt with over the years they've been consistent quality wise.
---
â– Synchronet â– RetroDigital BBS - rdnetbbs.com
Re: CLI vs GUI
By: physalis17 to All on Thu Nov 13 2014 03:15 pm
CLI all the way. Okay, I use GUIs extensively but I love the CLI.
Re: CLI vs GUI
By: Deavmi to Lofi-Samurai on Wed Jun 21 2017 01:01 pm
Great thread... I'm also a CLI junkie, and a friend and I are actually working on a project to offer shell accounts with some fun perks. It's still in the planning phase, but hopefully in short time we'll have it off the ground. It's geared for command line junkies.
If anyone's interested I'd love to hear feedback in another thread (dont want to hijack this one).
---
... Synchronet ... Vertrauen ... Home of Synchronet ... telnet://vert.synchro.net
It may very well be anathama but I prefer OSX. I've used all kinds of CLI based OSs over the years from a commie Vic=20 to my last DOS 486. Switched GUI with Windows 3.1 upto 10. Rolled my own Linux and 'next-next-finish'ed plenty of Ubuntu/RedHat/Mint installs. Setup a few hackintosh boxes. (They don't run all that well though)
With OSX you basically get all of the OSs you could ever want to use.
The GUI is top-notch. If CLI is your bag, the back end is (more or less) Debian Linux. If you need to run anything Windows, you can dual-boot or ru it in an emulator.
Macs are expensive, but out of the dozens (if not hundreds) of computers I dealt with over the years they've been consistent quality wise.
CLI all the way. Okay, I use GUIs extensively but I love the CLI.
Great thread... I'm also a CLI junkie, and a friend and I are actually worki on a project to offer shell accounts with some fun perks. It's still in the planning phase, but hopefully in short time we'll have it off the ground. I geared for command line junkies.
If anyone's interested I'd love to hear feedback in another thread (dont wan to hijack this one).
One of the things I do like about the CLI is when someone non-technical is watching me do mundane tasks, they seem so impressed. Or if I want to look like I'm busy, I run htop in a large term window and stare at it intently when anyone comes in the office.
Nightfox wrote to Lofi-Samurai <=-
I've known Mac users who have not used the command line in OS X.. Even though there's a lot of command-line tools there which let you do a lot
of useful things..
When I had the Mac, I always had a terminal open. Couldn't live without it. :)
Knightmare wrote to Vk3jed <=-
When I had the Mac, I always had a terminal open. Couldn't live without it. :)
I still do :)
| Sysop: | Ragnarok |
|---|---|
| Location: | Dock Sud, Bs As, Argentina |
| Users: | 136 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 19:36:46 |
| Calls: | 15,171 |
| Calls today: | 4 |
| Files: | 19,858 |
| D/L today: |
101 files (8,417K bytes) |
| Messages: | 1,692,104 |