Відео

I needed to add <Routes @rendermode=RenderMode.InteractiveServer /> to the App.razor to get the onclick to trigger, found static rendering is the .net 8 default on a google search

there are three modes (and auto mode) in blazor SSR, Server, webasm

Excellent video! This helped me a bunch

I hate the convention in C# to begin the name of functions with an uppercase letter. It looks disgusting. Generations of programmers have done it in almost all languages with lowercase letters for good reasons.

Sorry but C#/.NET as a language and framework in 2024 is superior to Java in every single way. Expressiveness, performance, ease of use/low learning curve, productivity, all of it. People are still floating along with a 2010 opinion of it and a blind hatred for Microsoft products. Drones.

In my personal opinion, C# has overpass Java since 2007 in performance features and power, Java is lacking vision and planning..

I use Go and C. I am just here to see what it’s about.

It might be something from one of the newest versions but java actually has Record classes. (With a record keyword instead of class)

One more point i believe we missed here is that , C# has awesome community With online resources like Stack Overflow, Reddit, and GitHub, you can easily find help and support for any issues you may run into while programming in C#. 😔

Cuz you know, I'm all 🎶 ... 'bout that LINQ, 'bout that LINQ, no bubble (sort!). I'm all about that LINQ, 'bout that LINQ, no troubles. (2x) Every API is threaded from the bottom to the top.... 🎶

The thumbnail pretty much describes Java's simp status. 😂

This video is riddled with inaccuracies and miss representations, so instead of pointing all of them out three examples: === struct Nullable<T> === The video claims that nullable value types of C# are the same as Optional<T> in Java. This can't be further from the truth. A nullable value type in C# is a value type, not a reference type. In other words it's a stack representation not a heap object. There is no GC allocation, management and freeing required. Optional<T> on the other hand is like all types beside primitives a reference type, because Java doesn't has the concept of value types at all. With all the performance downside especially the need for garbage collection. This is massive for simple types which only take up free stack space (or sometimes get optimized away into registers completely) vs a heavy heap allocation that needs to be managed and even has a negative impact on the rest of the code because the more heap objects you have the slower the overall management of the heap becomes. Additionally nullable reference types are highly integrated into the the language definition and not just syntactical sugar; you can compare value types to the null constant in language which obviously is a translation to check the boolean HasValue property because again, nullable value types are not reference types and cannot be null, it is just thanks to changes in the language standard that it was allowed to behave like it can be compared to null. A similar exception is in place for assignment of null (which again should and was not possible before the language standard got expanded). === operator==/operator!= === The video claims that operator== is the same as equals in Java. operator== is a static member method of a class which needs as argument itself and another concrete argument. In other words, it's the fastest, simplest to inline, boxing free way to have an comparison. The language actually requires you to implement the companion operator != exactly because for performance reasons. There simply doesn't exist something like that in Java - AT ALL. Java equals is on the other hand a virtual call that takes an nullable object, which exists in .net as well, it's object.Equals. This call by it's own by the nature of being virtual is around 20-40 times slower and cannot be inlined at all. === Generics === Java generics are using type erasure, they are a poor mans version of classic C++ templates, pure syntactical sugar. In C# generics are real types. Specifically they consist of a generic definition type (f.e. Dictionary<,>), one pure reference type generic implementation (f.e. Dictionary`2) and multiple mixed or pure value type implementations (f.e. Dictionary<int,object>). All of those can be constructed via reflection at runtime (f.e. typeof(Dictionary<,>).MakeGeneric(typeof(int), typeof(string) - impossible in Java). Implementations containing value types are also constructed because those not only make costly boxing/unboxing obsolete, they are also providing additional optimization opportunities on every layer. For this reason there is always only one pure reference type version (which basically is what Java has). The whole point of it only matters reflection is complete nonsense.

Only seen the start of the video so far but it seems a tad harsh to include type names as keywords since they are really not at all keywords.

This is very good. Too many C++ vs. this or that comparisons usually start with the ridiculous C++ is old and dangerous and should be abandoned kind of stuff.

awesome tutorial! Could you dive in into Localization? i cant find a good way of implementing it using blazor. Also, will you cover hybrids? MVC and Blazor?

i'm definitely in the C# camp... the last time i TRIED to do anything in Java I got totally lost just installing the tools. TO BE FAIR, it's very possible a Java guru would have the same reaction to getting started with C#. I used to believe the same things about performance... and for the desktop you're right. it's fast enough -- and when it's not, optimize the hot path and move on. in the cloud however, performance can affect the bill you get at the end of the month -- so performance needs to be a higher priority. anyway -- excellent and fair comparison of these languages without insulting anybody's mother ;)

I really enjoyed watching this video. I was able to learn a lot from watching this video and was able to enhance and upscale my existing knowledge in C#.

You were actually helpful. I took no offense to the fact Java is slow. It blocking IO vs Node.js Non-blocking IO is something I knew. C# being faster then Java is not something I am surprised at even though I have been in Java for 27 years.

Nice

❤ C#

Wonderful efforts... Lots of respect and love

Thanks Dear

When I see things like this I don't know why I would go back from Python

When I need java I use kotlin.

With C# you can do so much! Dot net alone is huge add to that unity in your free time. Just so warm all around

Okay sure but how does this impact readability?

7:03 And this is the worst idea anyone can have. The "Result" type (as well as other strategies) that some modern languages ​​use to return errors explicitly, has been solved in Java with checked exceptions since the beginning. Using RuntimeException is simply a lousy (and cheap) way to handle errors...because in most cases, they simply won't be handled. This is why in Java philosophy "RuntimeException" were only intended for PROGRAMING errors, "Error" for unrecoverable errors (That is why there is no need to explicitly declare that they will be throwed, and in fact they should rarely be captured.), and the other exceptions (the checked ones) for manageable situations (for example, retrying, rolling back a transaction , or notifying the user of the reason for the error so that they can provide a manual solution). Checked exceptions make boilerplate code, but not fragile software. The only case where checked exceptions make the code weaker is when they are caught but not handled (which is easy to see is a terrible practice. Just as bad idea as making everything a RuntimeException). If you don't know/can handle a checked exception at a certain point, just throw it again (but handle it as early as you can). If you use a knife incorrectly and cut yourself, it's not the knife's fault, it's yours. With this it is the same.

So basically, C# is harder but richier than java.

Pretty good summary. I think one historical difference had been start-up time. With Red Hat's Quarkus and using GraalVM, this issue has been fairly addressed. I think one area not covered may be library SDK Ecosystem in relation to Cloud Providers. If using Azure, both are covered fully, with edge to C# (broader functionality). If one is talking Google Compute Cloud or AWS, they may or may not be as fully comprehensive for C# as they are for Java. As for speed, as long as one follows standard best practices, either are adequate and you are correct, absolute speed really means another choice (C++, Rust, or even Golang depending on specific coding requirements).

I code in both. They are just tools for creating value to the customer and myself. If customer requires java, I'll code in java and viceversa.

It‘s Java. Everything is there. If you want lesse boiler plate code, use Lombok.

For me the only reason for Java exist is portability. It's a awful language, extremely bureaucratic, the solution for dependencies is a nightmare and everything has XML involved which really sucks! Moreover, Java is BORING! Everything has to get more time to do comparing with any other program language. C# is very performant, but .NET is so fat that performance decreases over time when more and more components( which developer doesn't have any control over it) is added to the program. As a program language I have no complains about it except for some "excentric" and exclusive keywords and concepts. The problem is have to pay to access the productivity features on Visual Studio. And it's expensive! Python is slow! That is the problem! But, the simplicity(thus, productivity) is the trade-off. So true, that scients choose the language as main language to solve their problems. It has a ton of libraries for anything a developer need and the new versions is getting better regarding to the performance issues. The GIL(Global Interpreter Locker) is finally going to an end which will unleash threads for Python a real feature instead a pain in the ass. For web I think is the best of three languages.

C# is what Java should have been

They all languages it's up to you as developers Java can't handle some things same as c#

Great Job!!! Thanks a lot! Can you do the same for .NET 8 and all these wonderful explanaitions:)?

Both Java and C# are not native languages. You have to install Java runtime environment or .Net framework to make Java and C# app work.

The only good programs I know that is written on Java are JetBrains IDEs and Minecraft. The rest Java app are bad. I do not know any good program written on C#

Awesome tutorial. Thank you.

Thank you Chuck love your teaching style. I've just subscribed to your channel.

Hey Chuck. Just want to tell you that I am happy to discover your channel. Keep up the great work spreading the knowledge in such a clear way and hope you get a much bigger audience

The statement about generational garbage collection "since Java 8" is wrong. They had it earlier, just gave it another name.

Java is faster where c# takes less memory

Can you do a comparison between C; C++; Rust; Zig; and an assembly -- which is faster?

Is it compatible with each other? 😂

New sub here! Perfectly explained, thank you!👏🏽

C# is bloated even more bloated than Java and you can't do any serious work without shoving a few pennies in Microsoft pockets. The average C# repo is impossible to read with knowing the ins and outs of VS.

Don’t understand why anyone would mix technologies in the same project unless you are migrating from one to another. Personally think mixing technologies is a bad idea, it makes maintaining a large application so much harder. What I like about Blazor by virtually eliminating all JScript debugging the UI is so much easier.

Good video.

A very interesting explanation. I also noticed that C# seems to be more adapted for Virtual & Augmented reality developer.

But I think Kotlin is going to replace Java. And maybe it's much better than c# :)