Hardware is from Mars(well Vulcan actually); Software is from Venus

[DimViesel]

We know what hardware is made of, we can state that quite specifically; as specifically as we ever would need, or reasonably wish to.

Ever wondered what software really is?
What is it really made of?

I thought this was quaint and yet had its insights which may open the eyes of some of the more inquisitive and rose-tinted-spectacles-wearing (towards computers and computing at least) amongst you.

Follow the URL and select the article whose title you recognise:
http://www.informit.com/articles/

As of today (13/05/03 - uk format date btw) page was slow in downloading but then that is from here in the UK, no relevance to your world and net experience just a prosaic observation, anyway 4th article link down. Just in case you thought I was sending you on a search mission or wild goose chase.

Who's it by? - This dude:
Winn Rosch

Winn L. Rosch has written about personal computers since 1981 and has penned nearly 1000 published articles about them – a mixture of reviews, how-to guides, and background pieces explaining new technologies. He won The Computer Press Association aware (sic) for best feature article. He is a contributing editor to PC Magazine and has been a contributing editor to PC Week, PC Sources, Computer Shopper, MacUser, and PC World.

... go figure, I believe is the right term here.

[DimViesel]

* SUPER POWER BUMP!!!*

The URL location of the article that seemingly none of you wished to read has changed:
http://www.informit.com/articles/article.asp?p=31697

It is an informative article written from quite a personal viewpoint (unusual for a science/engineering topic) ; however it results in a chatty informal style that makes light reading of a potentially dry subject which even 'NEWTS' should find rewarding. Go to it!
(No I don't get money for this! - You simply should be interested!
The part about the number of processes a simple window click calls on is humbling for want of a more apt word! )

[Kaitain]

A good find there! By way of analogy: I had a fairly long-winded debate with a family member a while back over a painting on display in the restaurant in which we were eating. To said relative, this picture was absolutely amazing, highly emotive and spoke volumes about the mood and mind of the artist. To me, it looked like someone had put a firecracker in a tin of Dulux.

I took the functional definition of the image - the "software" if you will - that it's "just a load of splattered paint". To the other half of the debate, the abstracted idea held all the importance. I'd make a lousy software developer

[Gizmo]

Originally Posted by Kaitain

I'd make a lousy software developer

Dunno about that. I've seen a lot of 'art' that got people all agog, and I STILL have no idea what they were talking about.

[DimViesel]

Yep. That image is just the conduit, serves that purpose, the result of a set of emotions that creates a need for communication of another set of emotions which in return hopes to enlicit or educe a further emotional/coherent response from the viewer. I think that is the real reason behind non-documentary works (& even some of those whose primary purpose is to record the pedestrian & 'real' faithfully) not the work itself but the thoughts that resulted in its creation & realisation & the sum of the reasons why it was not created differently.
(What's paradoxical about the abstract is: how can one gauge sincerity in the abstract? How can one discern when there is sincerity & when a work is merely aping a sincere work for visual effect? Does it matter? Since both were created by a human 'feeling' mind... for another thread,.. I know )
Not quite sure I understood how your anecdote relates to the theme(s) in the article Kaitain - but then I have not read it in a while & vividly recal the section on OS interoperability & not much else.. Did you find the time to read it?

They also have a interesting one on hack threats found using Google.

[Kaitain]

Originally Posted by DimViesel

Not quite sure I understood how your anecdote relates to the theme(s) in the article Kaitain - but then I have not read it in a while & vividly recal the section on OS interoperability & not much else.. Did you find the time to read it?

From the first page - the "what is a program" discussion