Discussion Forums > Technology

Apple releases new... everything

<< < (22/53) > >>

molbjerg:
I don't remember Opus on the Amiga, so I'm not really sure.


Oh, I forgot to mention, Litestep has a pretty powerful commandline interface too....

chubbysumo:

--- Quote from: iindigo on March 09, 2009, 06:48:45 PM ---
--- Quote from: chubbysumo on March 09, 2009, 06:11:34 PM ---
--- Quote from: molbjerg on March 09, 2009, 09:15:43 AM ---
--- Quote from: iindigo on March 06, 2009, 02:15:49 PM ---"better side of computing" my arse. Macs are for idiots.

--- End quote ---

That's personal opinion. Ironically, I've found that OS X generally does less hand holding and expects the user to be more technically adept than Windows does, which is odd considering that Macs are supposedly better for computer noobs than Windows is.

Besides, going to Windows means giving up my commandline (cmd.exe is a poor excuse), which is something I'm not willing to do >_>


--- End quote ---

What?? i use windows and i have all the commandline i want.  CMD.EXE is still in windows, and its a handy thing too. Windows comandline tools are the same as in macs, basically, they just run stuff from a specified set of paramiters.  All are the same, windows command line tools just mean you have to be a bit more experienced in how to use them.


--- End quote ---

Well more accurately, the Mac commandline is exactly like that of any other Linux or UNIX distro, which happen to be very powerful when in the hands of someone knowledgeable.

As for the power of cmd.exe, what all does it come standard with? Can I use sudo to force things the system doesn't normally allow because of permissions? Can I use it to SSH into other machines and control them remotely? Does it have the full arsenal of file management tools (including batch permission changing)? Does it allow full control of open processes, allowing you to kill them no matter what or limiting their processor usage to a certain amount, or even temporarily "freeze" or pause a processor-heavy app? I could go on and on.


--- End quote ---

Yes you can use sudo to force things the system wont normally allow, You can use it for SSH into other machines for remote operation, IT DOES HAVE BATCH PERMISSION CHANGES for files, as well as full file management tools, I have had to use it to save some files becuase of bad permissions on a old HDD, It does allow full control of open processes.  Like I said, CMD.exe just makes it so the user has to have more knowleged about how the OS works, because it doent hold you hand in the process.  IT relies on YOU the user to know all the commands, and what they do.  You can run all of windows thru CMD.exe.  It just makes you have to know more.

molbjerg:
I seem to remember discussing why xcode sucks.. and I found a funny website.

This one's for you iindigo:

http://www.xcodesucks.com

AceHigh:

--- Quote from: iindigo on March 09, 2009, 06:48:45 PM ---As for the power of cmd.exe, what all does it come standard with? Can I use sudo to force things the system doesn't normally allow because of permissions? Can I use it to SSH into other machines and control them remotely? Does it have the full arsenal of file management tools (including batch permission changing)? Does it allow full control of open processes, allowing you to kill them no matter what or limiting their processor usage to a certain amount, or even temporarily "freeze" or pause a processor-heavy app? I could go on and on.
--- End quote ---

Yes you can do all that.

However I prefer PuTTy for SSH and TeraTerm for Serial ports. (Yes I use serial ports when messing with electronics at work)

Meh, cmd.exe is a poor choice for me when I have to try gaining access to a CPU which I accidentally program with wrong fuses and wrong internal frequency (yes, today was a bad day at work), however attempting to use a Mac for that would be simply ridiculous.

So in other words when it generally comes to things like communicating with something else on an advanced level, Mac is pure garbage.

flaresignal:

--- Quote from: chubbysumo on March 11, 2009, 06:48:45 PM ---Like I said, CMD.exe just makes it so the user has to have more knowleged about how the OS works, because it doent hold you hand in the process.  IT relies on YOU the user to know all the commands, and what they do.  You can run all of windows thru CMD.exe.  It just makes you have to know more.

--- End quote ---

Sounds like code for "is poorly documented", honestly. Almost every Unix distribution has a good, searchable set of man pages for available commands, including Mac OS X.

Also, bash and other Unix shells generally put cmd.exe to shame in scriptability and command entry (tab completion, history, etc.), though Microsoft's made a good effort at bridging that gap with PowerShell.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version