Introducing pure C# FLAC encoder based on Flake Reply #8 – 2009-08-27 21:12:26

hah yeah i was checking out your code on sourceforge or wherever you have it and i noticed an awful lot of the recent revisions had been all related to FLAKE.. i figured something was up



kind of made me want to get back into programming looking at it, to be honest. used to be a hobby of mine, but i lost it over the years.. and I was kind of getting away from it when .NET framework started coming out... I remember a couple of the System namespaces, etc provide a lot of the base functions for the programs, but by no means was I a pro at it, just experimental. I had always been a C/C++ fan, so the idea of C# and .NET framework seemed interesting to me.



Ah yes... I remember.. I was an ASM programmer for 2-3 years there, and the last thing I wanted to do was go home and code. What is a good resource for getting a good overall idea of the .NET framework? I suppose MSDN would be a good start to just look up the different namespaces and what all functionality each provided. I know and understand the code part of it (as far as like the part that is based on C/C++ coding).. but I need to find something to help tie that in with .NET.





Couple of questions.. sorry to really get off the 'main' topic, but I have a couple of questions...



What are the differences between the different major versions of .NET framework... 1, 2, 3, 3.5, etc. I'm assuming added functionality, but were there any major changes or additions, etc that changed the way the framework was used, or what it could do?



I just need to get to google and look it up.. but I just wanted to say that I did look at certain parts of your code for CUETools, and it gave me a little bit of motivation/interest to maybe get back into it as a hobby --- so thanks for that!



Btw, I heard that the compiler for .NET apps basically converts all the languages into some intermediary code, then compiles that... essentially suggesting that no one coding language was necessarily 'better' in terms of the end compile's speed/memory footprint/functionality.. meaning that regardless if you create the same program in visual basic/c#/c++, they should all result in the same optimized code in the end, since a lot of it is all sharing the same codebase via .NET. is this true? (i do understand that it is up to the programmer to make their code efficient, optimized, etc and that can definitely have a huge impact on performance).. but essentially, if the same coder wrote the same program the same way in each of the languages, the end compile is going to be about the same? i know that ASM programmers used to brag how compact, efficient, and powerful their code was and laugh at visual basic programmers, "drawing" their programs, writing simplistic code with all of these DLL/OCX dependencies and it basically being "kiddie coding".... but it seems technology like .NET has kind of leveled the playing field out a bit, considering each of these languages are relying on the same set of "dependencies", etc. I mean, to me... I have no bias really, because I have written programs in visual basic before, and i coded ASM programs for a living too... so really, i don't see something like visual basic or visual c# to be "coding for beginners". it's code that is easier to understand, write, and manage.. is that a sin? depends who you ask i guess...



IMO, i feel that visual C++ can sometimes get a little more complicated with stuff like dereferencing of pointers and this type of thing, and of course visual basic is at times a little too... basic, as it is a bit copy and paste this, drag this here... then do something like whatever.Color = blue, it's almost like programming in english -- it seems to me that C# is a nice compromise between the two languages... the power of c++ with the simplicity of visual basic -- and i believe that was probably the intended result.



anyways, enough of the ramble.. got to get back to work.

