Re: [MLUG] Software development: was mono

[Stephen Montgomery-Smith <EMAIL:PROTECTED>]

Vern Green wrote:
> All I can say about .NET developing is that Microsoft has created (with 
> version 2.0 anyway) a development platform with .NET that will blow 
> anything else away.
>  
> What Microsoft has done is created the means for faster development of 
> software applications. I know for my purposes working with web platforms 
> the new system is such a time saver.

I have never used .NET and don't really know what it is about.

But I have done software development in C.  I have been rather surprized 
to find the Linux/Unix development process much easier than the 
Microsoft development process.

The Microsoft approach is a rather expensive product called Visual 
Studio.  Probably most of my problems are unfamiliarity with the 
product, but I have yet to even figure out how to even start writing a 
program.

The Linux/Unix approach is to use csh or bash along with an editor, my 
favorite is nedit, and a hand built Makefile to put it all together.  I 
just find this so much easier.  But again it is probably familiarity.

Where Linux/Unix wins hands down is the documentation.  I tried wading 
through the Microsoft Class docs, and I just couldn't figure it out. 
(My main goal was how to write Direct-X graphics programs, and to this 
day it is all a mystery to me.)  The docs that come with Linux/Unix, 
that is, the man pages, seem the model of clarity in comparison.

Again, I must admit that I did also read some very excellent books to 
help me with Unix (the books by Richard Stevens, and the red and blue 
OpenGL books).

Well, this is all a totally unfair and unbalanced view of things.

I do admit that using my wireless network in Windows-XP is slightly 
easier than what I do in FreeBSD:

Windows XP - click on the internet icon, and enter the WEP key if it is 
requested.

FreeBSD.  Simply type the following simple list of commands (as root)

kldload bcmwl5_sys
kldload wlan_wep
vi /etc/dhclient.conf
(edit the appropriate entries so that it has the correct ssid and wep keys)
killall dhclient
dhclient ndis0

I mean, what can possibly be easier?

Stephen

_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members