Java or C# [employment question]?

Question

Java

I know that such a question has bothered everyone, but ...
I'm not interested in "what is better and what is worse." All languages ​​are good and necessary.
I am interested in the following - in what language can you make a faster start and which direction juniors are more willing to hire? Yes, I looked at headhunter vacancies and I see that there are more java vacancies, but I'm interested in the real state of affairs on the market, and not dusty positions.
In Java, I'm afraid that JAVA EE is required, but you have to learn from SE. + we have a huge stack of incomprehensible (to me) technologies, the knowledge of which is also included in the list of mandatory. To look somehow confident you need to know so many things, sho horror.
In seasharp, it’s easier because, in my opinion (maybe I’m wrong), it looks somehow more monolithic and there are fewer incomprehensible words in parentheses in Sharpist vacancies.
This question has matured because some interesting people praise sharp and say that there is "a lot of work, learn ASP.NET and you won't get lost", others say that "there is a big shortage of normal Java coders on the market, and you can go into mobile development , it's more relevant now."
Previously, I had experience in programming in js / php / delphi, at an amateur level, since I did not consider the possibility of working as a programmer.

Answer 1

Both technologies are in demand, you choose.
Java: yes, you can go to android, or to the harsh Java EE, the request for Java juniors is stable, without surges and falls for many years. The banking sector, for example, has traditionally leaned towards Java, and there's a lot of work there.
C#: you can develop under windows, including mobile, Microsoft tools are also generally flexible, you will not live with C# alone. Also, don't forget that C# is a language for Unity development, and this is a large layer of gamedev vacancies that go past headhunters (by the lion's share).
The .Net and Java stacks roughly duplicate each other, maybe a little more options have formed in Java.

Answer 2

1. Well, first of all, there are not dusty vacancies on xx, but the most that neither is the truth, exactly the truth that you are looking for. This is what is now required and for which they give money. Therefore, yes, you need to look at vacancies and plan your studies based on the requirements.
2. A quick start, in my opinion, is impossible to make on either one or the second. Both are complex, both have incomprehensible words in brackets, both are scary and you will have to sweat.
3. For a quick start, in my opinion, that's right to jump into the car, this is a front-end, not a back-end. There are not enough of them and the requirements for them are low. Learn fast. Or a project manager.
4. What about ASP what about Java you are told correctly. Both versions are correct. Javistas are like hot cakes right now. Also node.js and ASP are required.
Are you what you want?
After all, they always write correctly in such matters - what you want to develop, then teach. It won't be easy anywhere.

Answer 3

What prevents you from starting on both and, having run the first hundred meters, already decide what your soul lies in?
"...nothing will make you appreciate the new virtues of a language more than the need to program in another language that, without having them, is similar enough to remind you of their absence" - Jon Skeet, java programmer, who wrote one of the best books on WITH#.
Once in the last century, my friend and I coded websites in a small company and thought about where to develop. I just tried java applets and showed how great it is. A friend objected that since we are working under Windows, we should look towards ActiveX. Now I work as a .NET developer and my friend is a senior java developer. Everything is changing. You have to be flexible.
The front-end advice isn't so bad.

Answer 4

C#/.NET will be easier because you just install Visual Studio 2015 Community Edition and start programming. You don't need any third party components. No command line.
Indeed, there are more vacancies in Java and, by the way, they also pay more than in a similar C# position. And this is a consequence of the first point - more and more new programmers choose C#.