Quote:
Originally Posted by Sahir
If I switch to Delphi now, what I am worry about is, if Delphi will do the same thing as microsoft did. I don't know what is the concern of the programming language in the future.
Printable View
Quote:
Originally Posted by Sahir
If I switch to Delphi now, what I am worry about is, if Delphi will do the same thing as microsoft did. I don't know what is the concern of the programming language in the future.
If you mean if Borland will withdraw support or cease to exist, then that is a risk that we all have to live with. There is no certainty Microsoft itself will exist n years from now. What if the sun dies or if the polar ice cap melts ?Quote:
Originally Posted by sukarso
If you mean, is it as good as VB, C# or Visual C++ ? I would say yes, and then some :cool:
My few thoughts:
1) It is not true that U have to pay to secure your .NET application. Beside the fact that U can obfuscate assembly, U can also hide an assebly in unmanaged code using CLR hosting API and cryptography. But it is true that it needs an extra work to achieve it.
2) .NET cannot be ignored. It will be part of all new products from MS and I think it will be better to get know it a little bit more.
3) .NET is no more dedicated to only 1 platform. It is now available on UNIX & Mac OS (see Mono - .NET for linux for example) and portable solutions too.
4) Running unmanaged code can become very quickly as obscure as using DOS application today.
5) .NET application can be as fast as unmanaged code - it is simply a question of design. I know few exaples that show situations in which .NET application can be even faster.
6) C# language was designed by guy that develop pascal language - so it can be seen as pascal (delphi) derrived :D .
7) U can develop your application (in C# for example) totally free (which is IMHO immpossible with Borland Delphi :rolleyes: )
8) Personally I hate VB (disregarding the fact that I was forced to write some applications in it). For example: It is not supporting (directly) multithreading, so it is very hard to develop good nonblocking GUI in it (only COM can help with it). So I won't miss it at all :D
Best regards,
Krzemo.
Yes what you say are true except for the last one (#8), I think our very own Cimperiali has something to tell you with that :D (kidding aside)
Yes, I think VB has come to an end but there are still large number of programmers who are using VB as companies are still embracing the COM technology in their system, some reasons I think because it is cheaper and practical.
It also seems that obfuscators aren't much protection anyway, as the site I pointed to shows.
Anyway, I don't think vb is anything great, but it does have a large developer base, and plenty of user support, since you'll hardly find a windows system without the runtime files. While nothing lasts forever, .net is just not a replacement for vb. At least not from all the facts thus far. Just because we won't be seeing vb in a continuous stream of new versions doesn't mean you can't still use it. It will work until the OS won't run it, and that's not for awhile yet, if at all. The fact that we can take advantage of the system API means we can access newer system capabilities without the language supporting it internally.
Yes...But this depends on the Win32 API future ...?Quote:
Originally Posted by WizBang
"All good things must come to an end".
I'm afraid VB6's days were numbered for a good number of years ? Why ?
Because the programming community has embraced object orientation as the design methodology to use in commercial systems.
You can't go to a job interview in C++ or .NET without getting some OO questions.
VB6 isn't object oriented. And I've seen first hand what a mess can be created for a relatively simple commercial project when it's not designed properly.
You seem to forget : I don't think that Microsoft ever intended commercial applications to be written in VB. I remember VB1 which was simply a rapid-prototyping tool. I get the impression it was first intended either as this or as a teaching tool to gently lead people into using C++/MFC. I don't believe that MS ever intended it to become a language which people would use to code commercial systems.
Eventually C++/Win32 will go away too... or rather become like Machine Language, used for time critical applications.
However C++ is a standard, cross platform language meaning that its longevity will be assured in one form or another until the other platforms start to change. Unfortunately VB6 isn't so it's death has come earlier.
No bad thing either in my book.
Besides if you don't like change why are you in an industry which makes money from it ? Everything in computers (certainly desktop) changes about once every 10 years or so... and remember, this is still a very, very young industry. It's only really 15-20 years old or so and is still trying to find a standard that it can sit comfortably with for a long period of time.
Darwen.
It's not probbable that VB apps will not run on windows platforms in future, but,
when MS will publish a new Office (with new Access), I suppose old VB6 apps will not be able to install on such systems if using Access database.
If MS will not provide a new service pack for VB.
So, we all have to expect problems in about 2-3 years.
Microsoft is positioning C++/CLI as the "systems" language for the managed runtime, analogously to the way that unmanaged C++ is the systems language for Win 32. So in the new MS world, when you want to get close to the metal in the managed runtime you'll reach for C++/CLI.Quote:
Originally Posted by darwen
I for one would embrace .NET tommorow IF I could protect it.
Nothing is 100% secure I know .. but from what I hear in cracking circles .NET stuff is easy pickings .. obfescated .. or not.
So for now its.
NOT .NET
.NET is definetly not easy crackings.
Personally, I am friends with atleast a dozen crackers or so and a few game emu teams. ATM, C# is the language of choice for game emu servers. For example, if any of you play WoW (World of Warcraft), the best emu team right now is WoWEmu, a server completely written in C#. However, this server isn't free, it's $100 USD. Naturally, this priced emu attracts crackers, but even some of the best of them that i know are unable to crack his emu and WoWEmu has only implemented a callback system to make it even harder to crack.
C# and .NET oriented languages ARE the languages of the future. Many have said it, and it's true. If you want my advice, go for C# and learn it quick. Linux and Unix aren't taking over anytime soon, so .NET languages are here to stay, for now.
As far as the MS leaving VB, its good in my eyes. VB has ugly syntax and format and I still to this day am not sure how ppl put up with it and understand it.
Anyway,
Peace.
MAL1C3: A program compiled in C#, C++, and so forth is not the same as one compiled or .net. I keep referring to Salamander, which is just one decompiler you will find just by searching on Google. Here is the URL: http://www.remotesoft.com/salamander/
It is true that .NET assemblies can be decompiled and there are tools available on the internet which can do that for you. But As I had written in previous post, so is Java and you can decompile Java Classes as well. But then people haven't stopped using Java. And it has been around for quite some time now. The reason being that Java is platform independent and complies with the Open Source Standard..
But then .NET has lots of other features which are excellent. With .NET MS is moving slowly in to Open Source Standard.
However, software which is to be sold commercially won't be written in .net, just as Java is not used for this purpose either. Almost any language has a chance to maintain a developer base in some corner of the market, but not all are appropriate for any given task.Quote:
Originally Posted by vb_the_best