Click here to Skip to main content
14,085,361 members
Rate this:
 
Please Sign up or sign in to vote.
See more:
Hi,

Is it true that .net is going to be obsolete by year 2016? I am beginner and one experienced Java programmer told me that .net will be out of the market by 2016 or they will change the name of it. Whole co-operate world knows about it. He also tole me that .net has security flaws and its market going down each day.

Please help me out and tell me if it is true, I love .net but I am afraid that I am going to loose my entire career.

Thanks
Posted
Updated 27-Mar-14 18:51pm
v2
Comments
pwasser 27-Mar-14 22:45pm
   
Learn to be critical and when someone makes an assertion such as this ask them to show you the source of their information. Don't allow them to wave you off and then be your own judge.
Richard MacCutchan 28-Mar-14 5:07am
   
Have you ever heard of COBOL?
Ravi Bhavnani 28-Mar-14 11:40am
   
> one experienced Java programmer told me that .net will be out of the market by 2016
Considering that Java is playing catch-up to C#, I highly doubt the veracity of that statement. See:

http://leftoblique.net/wp/2013/07/25/java-8-a-k-a-oracle-finally-catches-up-to-net-framework-3-0/

/ravi
Rate this: bad
 
good
Please Sign up or sign in to vote.

Solution 1

I would be sorry about it, too, but if your "entire career" could be lost due to such state of affairs and decline of yet another platform or a framework, even the very important one, it means that you are not developing any carrier. Carrier in software is not learning any particular APIs and not even languages. This is knowledge of fundamentals, the theory, ability to make it working together and deep understanding of ideas. Platforms and frameworks go and come, but ideas remain actual and develop. And I believe some idea remain actual forever.

(Besides, just looking at present-day market dynamics and listening to "one experienced Java programmer" hardly can be considered as reliable source of information.)

Now, about 2016. No, nothing can make me believe that anyone can reliably predict what will happen in two years. Nothing. I can give you serious arguments supporting the idea that future is unpredictable in principle. At the same time, if you want to build your career strategy based on the observation of present-day events and trying to keep up, you are already too late. I think the most productive approach is looking into future. Guess why? Do you think I mean the ability to guess what is going to be on top of the market and be ready for that? Wrong. Such strategy does not work, and the orientation to top-notch fashionable knowledge is not a productive idea. You need to be able to identify some fashionable trash which cannot have future and try to skip it. Our life is too short to get involved in some activity just because it is fashionable or on top of the market.

—SA
   
v9
Comments
BillWoodruff 27-Mar-14 23:31pm
   
+5 This deserves my vote if only for the delicious phrase: "identify some fashionable trash which cannot have future and try to skip it" ! Sergey, perhaps you'll allow me to use a condensed form of this in a short-story I am writing ?
   
Thank you very much, Bill.

As to the use... I would love to... But are you going to give the attribution to the original source? Is so, how can it be condensed? I mean... it can be, but perhaps I would like to agree on it. If you just want to borrow the idea, you probably would not have to ask.

You see, I value some of those thought much, but I wrote these three paragraphs in a rush, edited the text several times (I often get back to my previous posts and find some mistakes, type or bad wording, edit some of them many times), but still not sure I conducted my idea well... it is not so easy. Added the very last sentence.

And of course I would love to know about your writing...

Cheers,
—SA
   
Speaking of writing: please look at my recent article, you may find it interesting: http://www.codeproject.com/Articles/752137/Power-Over-IP-Testing-of-the-First-Experimental-Fa.

I hope you will participate in discussion, because I know you are the one who would ask some really difficult questions. :-)

—SA
Rate this: bad
 
good
Please Sign up or sign in to vote.

Solution 2

At the risk of playing Sergey's melody in a different key:

The skills in critical thinking, problem analysis, strategic problem-solving, creating meaningfully structured, and documented, code with robust error-handling ... the skills in understanding and using algorithms, and design patterns ... the skills in UI design, database access, file-system manipulation, vector and bit-mapped graphic manipulations ...

All those skills will not be lost !

But, the nature of the "game" you are playing ... software development ... is characterized by rapid evolution, mutation, and change: seemingly at an accelerating rate.

And, it is almost certain that you will have to continually refresh your knowledge of principles, and techniques, optimizations and heuristics, in the context of working with changing hardware and software stacks.

I would tell your friend not to quit their day-job and try and make a living as an independent fortune-teller :)

My crystal-ball (cloudy and cracked, as it is) tells me C# and .NET will be around longer than I will be in this body. But, think for a minute: consider what a great increase in functionality in .NET that Linq brought.

The C# and .NET of the future will have evolved.
   
Comments
   
Yes, with some risk... possible lack of comprehensiveness... randomness... uneven in value... very good points. A 5.
—SA
Rate this: bad
 
good
Please Sign up or sign in to vote.

Solution 3

Hii,


Thanks for supporting me and precisely to open my eyes. I should do exactly what i love to do most and I will keep it in mind that "Idea, Logic and purpose" remains the same in the whole process of software development.

Love youuuuuuu
   

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month


Advertise | Privacy | Cookies | Terms of Service
Web01 | 2.8.190518.1 | Last Updated 28 Mar 2014
Copyright © CodeProject, 1999-2019
All Rights Reserved.
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100