this post was submitted on 24 Jun 2023
15 points (100.0% liked)
C Sharp
1526 readers
2 users here now
A community about the C# programming language
Getting started
Useful resources
- C# documentation
- C# Language Reference
- C# Programming Guide
- C# Coding Conventions
- .NET Framework Reference Source Code
IDEs and code editors
- Visual Studio (Windows/Mac)
- Rider (Windows/Mac/Linux)
- Visual Studio Code (Windows/Mac/Linux)
Tools
Rules
- Rule 1: Follow Lemmy rules
- Rule 2: Be excellent to each other, no hostility towards users for any reason
- Rule 3: No spam of tools/companies/advertisements
Related communities
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I really like the idea of Blazor PWAs. Blazor just makes so much more sense to me rather than dealing with anything related to XAML/WPF/UWP. Developing with those just always felt so clunky and "anti-orthogonal" (best way I can describe it) to me. I felt I always had to remember really specific syntax and patterns to do things different things related to layout, databinding and styling. So much faffing about with custom ValueConverters and templates for something that Blazor can just do seamlessly with HTML. It all seemed so unintuitive compared to how Blazor really naturally extends HTML though C# without having to even touch javascript or its assorted frameworks and their additional hooha and complexity. Plus, if you wanted, you can take existing sites and HTML templates and fairly easily turn them into C# apps and give them access to .NET libraries.