in my opinion, with java the difference between theory and implementation is minimal as compared to C#. What i mean is that if the theory has 3 components in a concept, then the implementation of that concept in Java would also have 3 components in code. But, in C# the implementation would have 5-10 extra components that we would have to understand. Example, like, in this video you see that java uses existing concepts to implement new functionality, but c# has introduced a separate standard/princple/concept just to add a new feature. that is why there are more than twice as many keywords in C#. Java class library is more natural, while with C# it seems like every different concept has been implemented by a very different person. Although, with .NET Core things are getting better.

You make me want to start doing web development with .Net

Interesting, and a good explanation. I've prgramed in both C++ and C#, and have found myself frustrsted at times with C#. I've ran into a few situations were what would be simple in C++ was not possible in C#. Example: I had to modify an external library to do something that actually requied me to create a thread in it. The thread needed to finish its job before any application using it shutdown or the data would be lost. In C++ the thread would have to complete its job before it would stop processing. In C# the thread would just stop, regardless of its state at the time. Every mechanism, on paper, that was supposed to allow me some control over the thread in C# was bypast completely.

Java is much better

java has also annotation and record😉

Great video

This comparison makes no sense. Two tools for two very different jobs.

Thanks for the video sir, great explanation!, i want to move into C# .NET environment from Java, and found this video and i could get an overview about C# development

I had a small experience developing Java for Android apps and a big experiance working with .NET C# for enterprice apps, APIs and microservices. As somebody who worked on both even though not as same duration you know.. Let me be very fair and non-biased, "C# is just fantastic" and I enjoy deploying my high perf APIs on my servers using Github actions these days

c# all the way.

Really Working 👍

Great course! Thanks for your effort - can't understand why you don't have a lot more subs; hopefully you channel grows :)

you forgot that C# gives you the option to write low level code. So i can just write my Application using all of C#s benefits and only write the performance critical parts in a unsafe way without having to write them in a whole other language. I also like how C# adopts so many functional features, combining the best of both worlds

This is a great set of videos. Are you done with the live streams to continue the playlist or is this the end? I really appreciate the effort you put into these videos.

It is the best concepts video i have ever watched ❤❤❤.

Well am an c enjoyer Sooo... See more...

The power of Java is it’s JVM. You need traditional programming there is regular java. You need a cloud oriented solution for fintech there’s scala. You need rapid prototyping on the web there’s groovy. When I say web I refer to traditional web pages on the internet not intranet applications. You need RPC front end solution for front end web there’s GWT or Vaadin. Kotlin for mobile applications.

c# is too bloated

As much as I dispise Microsoft, they at least have their head screwed on when they sre designing C# unlike the people at Oracle while they were and are designing Java.. Unity is evil, use godot or ue5 That being said, Java actually isn't that bad of language. And the only real experience I have with java is interfacing with nigh on 15 year old code at this point

I wonder why chacked exceptions are a bad Idea? Because without being a Java Dev, it sounds really great. It always bothered me in C# that you never know when a method could throw.

I think it would be more useful if you kept both the C# and Java syntax on screen at once so you can visually compare them. Instead of "transforming" the code into the different language, so you have to rewind to check the previous syntax.

thank you ton

The question is so ridiculous. 😂 C# > Java

Thanks Chuck

Thanks for this great video

Java doesn't suck. It blows.

Does the dotnet vm take less time to spin up than the jvm?

the fact i can do this similar to js/ts makes me pick c#: var foo = new { // Some object props } Thats just one thing without a LinQs example or any of that and C# 12 is on another level.

in my opnion unless you RELLY need that cross plataform natively, and arent willing to use a third party framework, you relly should just use c#, its a better coding experience no questions asked, same thing to learn, java documentation and reference sucks.

C# has checked keyword!

Of course when someone does a comparision of a version of Java released 10 years ago against a comparision with the lastest version of C#, the latter will win.

Blazor is actually a breath of fresh air on SPA frameworks. I still hate developing SPAs.

Please do a similar video comparing both languages to Javascript/typescript.

Thanks

Hi! Thanks for viseo. can you please make a tutorial of aspNet web api + Blazor webassembly (not a `BlazorApp` or `Blazor Server` templates) Identity auth tutotial (new way, .net 8)? register, login, logout features

Very well explanation and differentiation.

Greetings from a web development instructor in STL, MO. Shared this video with my class. Thanks!

Thanks a lot for this valuable information. Actually, after I tried blazor, I would say it's the best framework work I have ever used. Thanks to Microsoft. Finally, with only C#, I can achieve the best results with blazor. As you mentioned, Blazor application looks like a desktop application on the web 😀

at last I FIND someone that teaches and and explains things in the same language a beginner would, maybe I'm to old to understand certain ideas or concepts but you made me understand everything easily since day one, with just your first four videos, thank you, some day youtubes F-up algorithm will find these videos and im sure they will get the attention they deserve, keep at it! you are a natural for teaching, thank you again

Great video! Well explained, thank you.

If a developer asked me which the learn, one of my first questions would be what kinds of companies do you want to work for? If you want to work on line of business apps in established companies, C#. If you want to work in west coast startups or big tech, Java. I definitely like the C# language and tool stack better, but because C# started out life as Windows-dependent, Java ended up dominant in cultures that didn’t want to depend on Windows. Thankfully the dependency went away, but the inertia from that history remains

What about readonly? 😉

Nice to see Microsoft JavaScript features being added to Microsoft Java, I love this!

First!

8:28 hah, the standard library laughs in std::basic_stream

c# now has var you can use with variables, it's will auto guess the type and sets it. e.g. var bla, and later bla receive a string, it will assign the type string to bla

I prefer the classical way of using templates. This one will make code uglier if i am going to define a variable that has the same type as an argument. Let alone, one can’t use concepts. Sorry, hard pass.

Good video. I'm not sure I agree vis-a-vis the cross-platform support in C#. I say that as a 20 year Java veteran who has written Java applications for Mac, Linux, Windows for Desktop and Server and mobile (as far back as Java ME / MIDP / CLDC on Symbian Series 60) and with plenty of experience of AWT, Swing and SWT on the desktop. I developed with C# on Windows for a while back in 2013/14 and, though I could see the benefits of .NET framework, felt that compared with Java it was very much the poor relation at that time. Especially for enterprise use and high volume applications on super stable unix or linux machines. And writing installers with WiX Toolset for Windows was necessary rather than optional and effectively an entirely different skillset to pick up over and above C#. Today I think the reverse is largely true. C# is now an excellent cross-platform development tool. These days I almost always develop on a Mac and target MacOS and Linux for the most part. I think the C# community have a far better handle on developing with domain-driven design and event driven architectures than the Java community do and this is reflected in the relative popularity of libraries and their maturity to support this. The dotnet CLI it very useful and I find that I very rarely use Visual Studio at all these days. If you want a great IDE, Rider is to C# developers what IntelliJ IDEA is to Java and Scala developers (and from the same source: JetBrains). C# is now an excellent tool for browser-based client-side apps. As a long-time Angular and React JavaScript/TypeScript developer (with 14 years of doing this) I really like Blazor and find it very productive. Indeed I prefer it to Angular and React these days. Linq has been around for ages and if outright performance isn't your highest priority it makes application code very readable and pleasurable to maintain. EF Core is pretty good as an ORM and combined with the built-in dependency injection container (or any of the alternatives) and/or Dapper, C# is comfortably as pleasant to use as Spring Framework & Hibernate and personally I prefer it. I much prefer NuGet to Maven, too. And to NPM for that matter. I've used recent versions of Java and it's okay. But it's still very "blue collar", which I guess is no bad thing in its own way. I genuinely have come to very much appreciate C# though and, team skills aside, it would be my first choice for application development these days. It does virtually everything pretty well (from Browser and Mobile through to Desktop and Server). Java excels on the server, is totally outclassed on the desktop (and I say this as a former Eclipse plugin developer), is next to useless on the browser and pretty reasonable on just one mobile platform (Android). Altogether I think you can't really go wrong with C# and something like TypeScript as a fallback on the browser. I'm now doing a lot of Rust, too, these days which is great on the browser (with Leptos in my case), fantastic for CLIs (and better than C# here), really good for embedded applications (where C# and Java are totally lacking) and with luck will be a decent mobile platform (running on Tauri) in the not too distant future. That's still very much a niche, though. Though a very nice niche, particularly with WebAssembly (browser and Wasmtime). Rust has become very exciting this last year. Having said that, though Rust, C# and Java are all super-practical on the server, Go is by far the best of the lot for its concurrent programming model. Overall I'd still end up using Rust if stability and security (as well as good performance and low resource use) were critical. But Go is still a super-practical alternative when it comes to micro service development and positively shines compared with Java and C# for certain kinds of server-side applications. Go has got a very quick and shallow learning curve for new developers if you're onboarding them but a very steep learning curve (close to vertical) when you get to the more complex stuff and/or find problems that can't be solved easily. The initial simplicity can be a little bit deceptive. If you had to have just one language to develop with, though, for me C# is a clear winner as an all round do-it-all language that does virtually everything pretty well. If you've programmed in other languages (Rust and Go in particular) then you'll yearn for what these provide from time to time. And JS/TS developers may hanker after the odd thing on the browser. But if you haven't used any of those then you won't miss them. I can't think of a single reason (other than the large ecosystem of libraries or a team that only had Java skills) where I'd now opt for Java over C#. C# is better and more productive almost all of the time. Like Cobol, Java will be around for decades. And it's still a very good all round programming language. It's a bit dull to work with but it gets the job done. Modern Java code is a little bit more compact, even if it can't quite match the (relative) elegance of C# in quite a few areas. C# by and large just makes things 15% easier day in day out.

I spent sometime converting a C++ CLI service over to C#. In terms of syntax, I'll take C# over C++ CLI every time.