I have no idea...
-
Yet another programming api - sorta similiar, kinda compatible, definately different but given the same marketing name: .Net Hmm... this means once again - that there is motivation to abandon the previous versions. I think they should come up with a decent object model and stick to it.. change underlying code as necessary to match the running platform. This is how myself and others in the field of making libraries usually do it. Now we have .Net 1,2,3 and a four? Do .Net 1 programs run on .net 4? No.. you need to install 100 megs of support junk. You want .net 2? Oh... you have a tiny .net2 program? Grab another load of support software... Compile to true binary versus JIT be tough, you can do it. :)
Know way too many languages... master of none!
-
Yet another programming api - sorta similiar, kinda compatible, definately different but given the same marketing name: .Net Hmm... this means once again - that there is motivation to abandon the previous versions. I think they should come up with a decent object model and stick to it.. change underlying code as necessary to match the running platform. This is how myself and others in the field of making libraries usually do it. Now we have .Net 1,2,3 and a four? Do .Net 1 programs run on .net 4? No.. you need to install 100 megs of support junk. You want .net 2? Oh... you have a tiny .net2 program? Grab another load of support software... Compile to true binary versus JIT be tough, you can do it. :)
Know way too many languages... master of none!
JasonPSage wrote:
you need to install 100 megs of support junk.
Hey, you know, that's why we have such big hard drives now. It's not for user space for things the user wants, it's for Microsoft to clog up with pointless libraries that may never get used. Ah well, another day at work I suppose.
-
Yet another programming api - sorta similiar, kinda compatible, definately different but given the same marketing name: .Net Hmm... this means once again - that there is motivation to abandon the previous versions. I think they should come up with a decent object model and stick to it.. change underlying code as necessary to match the running platform. This is how myself and others in the field of making libraries usually do it. Now we have .Net 1,2,3 and a four? Do .Net 1 programs run on .net 4? No.. you need to install 100 megs of support junk. You want .net 2? Oh... you have a tiny .net2 program? Grab another load of support software... Compile to true binary versus JIT be tough, you can do it. :)
Know way too many languages... master of none!
-
JasonPSage wrote:
you need to install 100 megs of support junk.
Hey, you know, that's why we have such big hard drives now. It's not for user space for things the user wants, it's for Microsoft to clog up with pointless libraries that may never get used. Ah well, another day at work I suppose.
LOL
Know way too many languages... master of none!
-
LOL - Sorry - I've been a little Microsoft disgruntled on various fronts. But - I can put on a good show :) But... that's after our break - stay tuned :laugh:
Know way too many languages... master of none!
-
LOL - Sorry - I've been a little Microsoft disgruntled on various fronts. But - I can put on a good show :) But... that's after our break - stay tuned :laugh:
Know way too many languages... master of none!
There is not a day goes by that I do not say "I hate Microsoft". Of course we use only Microsoft where I work, if we used ABC I would most likely say "I hate ABC". I guess I am in the wrong line of work but what else can I do? :sigh:
-
There is not a day goes by that I do not say "I hate Microsoft". Of course we use only Microsoft where I work, if we used ABC I would most likely say "I hate ABC". I guess I am in the wrong line of work but what else can I do? :sigh:
Naahh... if it pays the bills - or some of them at least - you're not necessarily in the wrong business. I recently went to an oral surgeon for my teeth, and THAT my friend is a racket! We might all be in the wrong business. But back to .Net and Microsoft and whatever - there is a lot of good in that .Net stuff, I've written a lot of code in it - I prefer C# out of the language posse... To answer the original poster... if you WANT to invest in Microsoft Technology, by all means get good on the stuff not out yet, you'll be up to speed when it's released... and you can be sure it will be supported at least a year thereafter (historically speaking)... most likely 2 to 3 years... but .Net 3 hasn't been out that long - and they are already replacing it but in their defense, you still can get .Net 1.0 to run on today's platforms. THAT PART IS GOOD... the code RUNS GOOD (not lightning fast but good) and in all .net you need to obfusciate your code for commercial releases. --Jason
Know way too many languages... master of none!