What should I choose, C# or Java? | Sololearn: Learn to code for FREE!
New course! Every coder should learn Generative AI!
Try a free lesson
+ 5

What should I choose, C# or Java?

for deep understanding.

30th Jan 2017, 1:33 AM
Ankur Soni
Ankur Soni - avatar
6 Answers
+ 5
I'm not sure that this is the right discussion, but I'll write here anyway. I'm learning c# more as a hobby and I'm not that experienced as a developer to apply for employment in a software company. I'm more interested in code I can write solo in order to win some money as a side job. C# is applicable in all sorts of software, therefore my question is: What is the shortest way to profit with coding in C#? And what I have to learn in addition: SQL ,.NET etc.
30th Jan 2017, 2:10 PM
Stoyan Todorov
Stoyan Todorov - avatar
+ 3
C# is used with Unity, so if you plan on going into console/PC game development, go with C#. If you want to program something for Android, learn Java. There's nothing stopping you from learning both at once, though. They're very similar languages, so if you learn one, learning the other shouldn't take much time.
30th Jan 2017, 1:44 AM
DaemonThread
DaemonThread - avatar
+ 3
@Stoyan from what I've read into the business side of tech startups, the general consensus is that the quickest way to profit from software in general is to release a Minimum Viable Product version of an app/service/game that you are making, that will be loved by some small group of customers (a niche) that you understand well. Refine and perfect your project with updates (according to feedback from users, as well as analytics data), so that you really are number one for that niche, and also add functionality that broadens your appeal, whilst not ruining the experience for your initial userbase. Basically you can't make a profit on code that has not been released yet, nor code that nobody sees the benefit of, nor software that is being done better by an obvious choice, and often people tell you what they are looking for in comments - so the MVP (Minimum Viable Product) shouldn't have all the features you want to eventually have, you shouldn't spend extra time making code neat (at this stage) but it should have a way to get feedback and monitor what isn't working and what people use lots. The MVP should be good enough that people won't just ignore it, and it should be different enough from mainstream apps that for that specific niche, this app does it better.
31st Jan 2017, 1:35 AM
Phil
Phil - avatar
+ 1
love to hear u all.
31st Jan 2017, 4:17 PM
Ankur Soni
Ankur Soni - avatar
+ 1
I think u go with java
31st Jan 2017, 7:59 PM
Saurabh Jakhar
Saurabh Jakhar - avatar
+ 1
both. they have different purpose.
1st Feb 2017, 5:29 PM
Mohsen
Mohsen - avatar