.NET is huge. Too huge. 2

[IonelBurtan]

I just installed Net Beta 2 on my computer (of course I changed the date so that it wont expire on July 31 ).

Anyway I found a lot of IDE bugs to lame about, I don't know about the others. But this is not the question, this is:

HOW CAN YOU LEARN SOMETHING LIKE THIS? (.NET)

Even if you know all elements implied (ASP, VB Script, JScript,XML, VB, VC++ and the way Java work) I think you can mess with NET about an year to understand their relationship.

I also wouldn't wanna be in place of a newbie who has to learn .NET as the first programing environment. He will probably grow old before understanding it.

How about this? s-)

Blessed is he who in the name of justice and good will, shepards the week through the valley of darkness...

http://www20.brinkster.com/ionelb

 

[BlindPete]

Oh perhaps your are right at least with newbies. I think mostly heavy programmers will be compartmentalized into their familiar lanuguage(s) VB, C or whatever.

As I understand it, the IDE is the same no matter which language you use... so what's the real difference between the languages... syntax? Same IDE and all compile to same VM or whatever they are calling it these days. It could be argued that .NET is simplfiing programming by combining the languages in a single IDE and compiling to a single VM. Since all .NET languages can access each others resources which language you use in the end becomes irrelevent, it is all just syntax to get you to the same end result.

I must be over simplifiing things. I'd like to hear what other testers/previewers are thinkning or ahve seen.
-Pete

 

[neilkonitzer]

I've heard many references made to the upcoming Visual Studio 7 as 'Crybaby.NET'. It's got a lot of neat features. The previous poster is correct in stating that the developers that use it will most likely stick with their forte, whether it's VB, C++, or if they migrate up to C#. For us developers that develop in both VB and C++, I think that it's beneficial to have an IDE that has a common look and functionality. I also like what they've done to VB. It's becoming more of a true object orientated language. Yes, there's much to learn to get it's full use. There's probably much more functionality included in .NET, than I'll never use.

Part of becoming a successful developer is the versatility in learning new things. It may be a little overwhelming at first, but hang in there, you'll get through it.
Neil Konitzer, President
Freisoft

http://www.freisoft.com

 

[fluteplr]

I agree with Neil. Being mostly a Foxpro programmer, we went through a similar experience 5 years ago when Foxpro became Object Oriented with Visual Foxpro. About 60% of the existing Foxpro programers never made it over the 'learning cliff' as we called it. The rest of us figured out OOP and have been happy campers ever since.

It was about a 6 month struggle for me until I finally had an 'AHAH' experience and OOP and event driven programming finally sunk in over procedural programming.

As to the other 40% over the last few years I would guess about 1/2 that group finally caught on and the rest are rapidly becoming dinosaurs.

 

[icici]

Are there any good tutorial(s), which explain how to use OOP and not the theory only. Also most of the tutorials don't take actual (live) example, lets say BOM Explosion (Bills of Material) or Inventory or Payroll to explain the concepts.


I hope those who have understood the concepts may post a detailed paper on the Forum for the benefit of others giving a live example and how they used the OOP.