|
No, never learned that -- but I hear it lives on in Caché. 
Also, I've forgotten all the Pascal, Lisp, COBOL, and Fortran I learned in college.
|
|
|
|
|
You actually learned Fortran I? (I'd guess it was simply called Fortran at the time). I started out with Fortran II, immediately moved on to Fortran IV and Watfor, soon to be followed by Watfiv.
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
Fortran 78? In 1986 on a VAX 11-780. Good times. 
|
|
|
|
|
I was punching cards and feeding them to IBM machinery in the early seventies...
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
But were they good times?
|
|
|
|
|
Most times have been good, however the best is the present, by its very nature.
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
I'd agree, but I've been doing VB.net for the last nine months.
|
|
|
|
|
VB.NET isn't that bad, make sure strict on applies to everything (I know you had it set up by default), then pretend it is C# and you'll be fine...
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
Yeah, right... I ran up against the exclamation point (!) operator today -- I asked around and no one knew what it was so I had to look it up.
I'll stick with C#, thank you very much.
|
|
|
|
|
A little cheat card can go a long way.
The nastiest difference I found between VB.NET and C# is documented here[^].
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
Or how the behaviour of ToString for enums in VB doesn't match the documentation.
|
|
|
|
|
If so, please send your resume here to the VA. We always need more MUMPS programmers. 
|
|
|
|
|
It's the VA from whom I heard about the MUMPS/Cache connection.
|
|
|
|
|
At least we are thinking about moving it off VMS and onto Windows and/or Linux.
We might even upgrade our VGA monitors.
Kidding. 
|
|
|
|
|
GenJerDan wrote: moving it off VMS
Nooooooo!! 
GenJerDan wrote: our VGA monitors
On VT525s?
GenJerDan wrote: Kidding
Phew! Don't do that to me, the ol' ticker can't take much more.
|
|
|
|
|
You should have seen the history of VB6. If that can exist for this long, C# will surely do.
[humor]
Although, there are many claiming that World will not exist for 5 years. So no need to worry. 
[humor]
"The worst code you'll come across is code you wrote last year.", wizardzz[ ^]
|
|
|
|
|
I suppose VB (DIE! DIE! DIE!) can trace its roots back to 1964.
|
|
|
|
|
Look at what is out there now: C (initially developed in 1969) is still in use, C++ (initially developed in the early '80s, named in 1983) is still in use. C# as a logical offspring of these is likely to be around a while longer yet!
Even COBOL is still in use by some poor sods, and that was designed in 1959!
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Manfred R. Bihy: "Looks as if OP is learning resistant."
|
|
|
|
|
OriginalGriff wrote: Look at what is out there now: C (initially developed in 1969) is still in use, C++ (initially developed in the early '80s, named in 1983) is still in use. C# as a logical offspring of these is likely to be around a while longer yet!
I doubt the first two are comparable to the second.
The first two, and especially C++, was pushed into a public specification with a large (disparate) base interested in the language, specification and success.
Both were also the primary language used to support many OSes themselves. Unless all of the OSes that rely on it go away it makes it virtually impossible for the languages to disappear.
As counter example Pascal at one time had broad support but was primarily pushed by several commercial interests. It still exists but is significantly less prominent. (There was even at least one OS based on it.)
|
|
|
|
|
You can not define a future of any Language, specially languages like C# which is highly promoted by Microsoft.
C++ is there from > 20 Years
C is there from > 30 Yerars
Cobol/Fortran is there from > 40 Years.
C# has good future and C# 4.0 has good functionality, I specially like Parallel Programing.
You should better ask what is future of Programmer then answer is they will remain as Programmer as long as they love that job
Regards
Rushi
|
|
|
|
|
Oh definately for a long while yet. As already mentioned there are languages that were consived 50 years ago that are still being used in some way. The popularity of C# is its aid as its ensuring its longevity....
|
|
|
|
|
Thanks you all
I got the idea
|
|
|
|
|
Yeah.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
|
|
|
|
|
It's gonna die of cancer. Doctors say it has max 3 month left
Joke aside, I think it will grow(just like the cancer) rather than "die".
All the best,
Dan
modified on Friday, May 13, 2011 5:23 PM
|
|
|
|
|
supernaturaluser wrote: Is the language going to be around for the next 5 years or maybe more?
Should be around long enough to specialize in it.
However even if popular in 5 years if that is the only language you are familiar with (in 5 years) then you should probably look to learning at least one other.
supernaturaluser wrote: Hope someone has an answer
Anyone that can predict the future should find some other way to use that ability besides programming.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
