So does this mean I should stop learning VB?
I could start learning .NET or C++ or C#
I just liked the easy VB syntax
Printable View
So does this mean I should stop learning VB?
I could start learning .NET or C++ or C#
I just liked the easy VB syntax
So does that mean only C/C++ is the language in which we can write commercial software.. I have seen companies like Intel/IBM/HP and lots of biggies using .NET for one purpose or the other.Quote:
Originally Posted by WizBang
And what actually is a commercial software?
Thanx for the insight..
There are still many choices, and that will never change. The reason why .net and Java can be decompiled is that neither is fully compiled, but made into a kind of "intermediate" code. This is because it is managed, for garbage collection and so forth.Quote:
Originally Posted by vb_the_best
Here is a nice explanation:
http://dotnetjunkies.com/WebLog/bhar...les/44112.aspx
I think of commercial software as that which is sold publicly to multiple users (not used proprietarily).Quote:
Originally Posted by vb_the_best
Thanx..
So that doesn't mean that .NET is .NOT!!
Even if .NET will not be a choice for developing commercial software, but i think the best part in .NET is Web Services, the number of languages it supports, the Open Source standard which it is using and the ease of developing customized applications in .NET. Don't these features make it a better platform for development.
I've no doubt that .net will maintain a share of the Web services market. It's just not a replacement for vb, nor languages like C, Assembly, etc..
I totally agree with you..Quote:
Originally Posted by WizBang
C/C++ have been the best things that have happened to computers after Assembly Language.
I personally like VB, but as market changes you have to change so I have moved to .NET.
I am a bit more concerned about difficulty in learning .Net at a good level in few
time rather than in "security" of sources I write, as I am coding for customers
which at last keep the sources, and do not own my code. The sad part is that I
have spent a lot of time and effort on Vb (started with 3, stepped trough 4 an 5,
and landed on 6), and now I feel as if I have to restart quite from the beginning:
what I know is more confusing me than helping in dealing with net, no matter
what pubblicity says: I need more time to do same thing I can do in Vb, or I end
up with poor solutions.
The "commercial" matter is an issue, of course, and I believe Wizbang is right:
.net is not the tool to make "commercial" (=desktop) products but web ones,
held by the owner of a company which has the server where they are installed.
But it seems as if this is the guess: in the future, even more products (at least, all
services, aty first glance, but sooner or later also what till now has been a
product, like a book-keeping software or even a text editor) will be accessed via
internet, and even few will be on client machines.
In any case, even if Vb 6.0 could actually die in a not too distant future, other
compiling languages should not. And, by the way, remeber many said Cobol
should have disappeared more than 10 years ago, but is seems as if it is still
here... ;)
Maybe we'll see Cobol .NET ? How about Forth .NET ? Lisp .NET ? Smalltalk .NET ? *laughs a lot*Quote:
And, by the way, remeber many said Cobol
should have disappeared more than 10 years ago, but is seems as if it is still
here...
I think we already have Pascal .NET kind of with Delphi .NET.
Darwen.
If I am not mistaking, cobol .net is already here.
We will see if Cobol (not dotNet) will survive also at this...
Maybe after sometime we will see myOwnLanguage.NET.. :D
here is what I came across today on the internet....
http://www.apress.com/book/bookDisplay.html?bID=213
This book is titled : Build Your Own .NET Language and Compiler
Will there be issues if one deploys an application made in vb.net to a win98 os?
Don't quote me on this, but I think there might be two different types of cobol.Net. Fujitsu responsible for one, and I'm not sure who did the other... again.. don't quote me. Just a rumour I heard.Quote:
Originally Posted by Cimperiali
Hey, what can you say about this site?
Just what will happen to me if Microsoft would leave VB? I am only just beginning to learn the language and i'm forcing myself to much because i hope that sometimes i can make a good application too. The idea was really frightening.
I disagree with this. We use .NET simply because of the fast turn around times, slowely but surely I think we will see (infact we already are seeing) a shift toward using .NET.Quote:
Originally Posted by WizBang
As the issues around .NET are resolved (including reverse engineering) more programmers will move over to the new technology. The Dotfuscator is one of the first attempts to make code "irrerevsable". But at the end of the day nothing is irreversable... once you have a file that you can run you can decifer what it does and that is essentially reverse engineerig. Even asembler and machine code. The only thing you can do is make it more and more difficult to understand.
If reverse eng proves to be a huge problem M$ will eventually do some thing about it (they'll have to). Over the last few years M$ has become more concious of giving people what they want instead of trying to give people something and MAKING them use it (Office moving to XML is a case in point).
I am not evangalising .NET... its just where I think the market is heading. Time to market is probably on of the most important factors in the current businesses world of coding. (From my experience, companies that haven't realised this tend to go under).
But, how right I am will be determined in time...
At the end of the day most languages are pretty much the same. If you can code in one then you can code in another. It is just the instruction set and syntax notation that differs. The general concepts and algorithm structures stay the same. So, learn VB it is a nice language to write in. Very simple, nothing trying to confuse you, and if you make a mistake VB will try to tell you about it (unlike C).Quote:
Originally Posted by rtolledo
You can still write apps in VB. It will still be of some value for several more years.
But yes, one day you will have to move away from it. But then you'll have a good idea about what is going on inside the PC (and you'll have the option of moving over to VB.NET, which has similar syntax).