Very Computer

*CROSS POSTED TO comp.unix.solaris  

Yes, Unix was created by people who know CS and programming concepts.
Don't you think an OS created by such people will be better than a knock-off
of the MAC OS, that when you look under the hood is a beastly mutation
of a 16-bit CP/M derivative? Smell the coffee, man.

Also, MAC OS itself has BSD Unix purring under its hood. Apple, the people
who make the most user-friendly OS around, recognize the power of Unix.

Unix is the foundation for technical computing and networking that made
the internet, pro/e, nastran, and scores of other codes possible.

Unix scales from desktop PC's through to supercomputers, and your code
compiles and runs on these platforms. No problems, as long as the code
was written properly.

The people that choose to stay with Windows are the eunuchs, cause they
don't want to learn an operating system that enables the civilized world
to do all the things that enable people to get things done.

Quote:>* The VI editor (don't swoon, now, gnurus) ~ need I say more! (I can you
>know, much more!)

vi is a text editor, not a word processor. But vi is used for basic
text editing, right through to preparing text for typesetting. vi is
a small program that is spectacularly efficient... if you spend the time
to learn its command set. You can find, change, and manipulate text more
powerfully than any comparable Windows-based editor. Any editor that runs
on Windows that even competes is usually a port of an editor such as emacs
which itself came from Unix.

Quote:>I could go on, it's a very long list, but I tire of this vituperative

I'm tiring of this nonsense too...

Don't blame Unix for PRO/E's design/usability flaws.

S.
--

From the desk of Sanjay,                        |\      _,,,---,,_  
                 Shadow,                  PRrrr /,`.-'`'    -.  ;-;;,_
                 & Niji                        |,4-  ) )-,_. ,\ (  `'-'

Why?

The striking coolness of ProE's *nix roots are exemplified in, of all
places, Intralink.  I'm off topic. . .forgive me, but. . .

We've been updating files to I'link that once included rev letters in
the filename.  <Ech!>  You've had your past *brilliance* catch up to
you before, right?  Now by virtue of regular expressions, I can rename
multiple files from '1234-01a.prt' to '1234-01.prt' in Intralink by
using a character class thusly: <dialog has a _from_ textbox:>
*[a-z].* <and a _to_ textbox:> *.*  Dozzat make sense?  Any lowercase
can be excluded from the new name. (Either case can be handled w/
[A-z], of course.)  Small time, but cool if you need it!

Such are the relics (from vi, sed, awk, shells) you are blessed with
because ProE started on a vital OS with _thinking_ authors.  Someone
breathe for a moment!