Earlier quoted context omitted.
> But rubyists would’ve loved C#. As a Rubyist, I'll admit that C# is the least bad of the C++/Java style of static OOP languages, but it was that it was always too tied to the .NET ecosystem and heavyweight enterprise tooling more than Microsoft's “supervillian role” with regard to FOSS that made it unattractive for lots of places where I would want to use Ruby. That's improved with Core, somewhat.
Yeah, .NET Framework was an absolute pain to work with also, there was a lot of boilerplate, especially when it came to ASP, and like you said it was tied to Windows and Windows API. Now with Core it's multiplatform and they're opening up all of the traditionally Windows-based SDKs to Core architecture and making them multi-platform while having them open source. .NET Core is an absolute pleasure to work with, and wh…
.NET Core 3.0
81–90 of 183 posts
Re: .NET Core 3.0
#82I have been developing in .Net MVC 5 and now the last 6 months in .Net Core 2.1. Core is pretty awesome, I would say the learning curve is pretty high, but I'm very satisfied. Previously, I used Java in school. The .Net stack offers a lot of jobs in enterprise companies, if you are someone that dislikes SV mindset. Also, Visual Studio is an insane IDE. Although, I recently did have some nasty bugs but updates are com…
VS is very good but I've been using Rider since the start of this year for most work, I found it to be a very strong competitor.
Re: .NET Core 3.0
#83Non nullable reference types are so awesome! I'd love for the C# team to publish some posts on the creation of this feature. Most of the non nullable type systems exist in functional, or pseudo functional languages (Rust has rather functional semantics). It's very neat to see a honest to god mutable object oriented language implement non nullability. They probably had some interesting implementation challenges. Also,…
Re: .NET Core 3.0
#84Earlier quoted context omitted.
C# has very minimal boilerplate for a lot of uses. I can throw together a simple CRUD UI app in WinForms in well under a day. Visual Studio handles writing all the data binding code for me, code that I'd have to write myself in any other language. Using one of the enterprise frameworks, sure, those all have boilerplate, in any language, especially the older frameworks. And for some tasks, the amount of boilerplate is…
Under a day ?? Make an app with pyqt5 or kivy and it's under an hour...
Re: .NET Core 3.0
#85Earlier quoted context omitted.
Memory usage difference should be something like an order of magnitude better with .NET. It's not a direct comparison, because the features aren't quite the same, but the Electron Teams app uses about 10x more memory than the relatively heavy WPF Skype for Business client that it's supposed to replace.
Skype has been replaced by an electron app https://electronjs.org/apps/skype
Re: .NET Core 3.0
#86Re: .NET Core 3.0
#87Earlier quoted context omitted.
C# has very minimal boilerplate for a lot of uses. I can throw together a simple CRUD UI app in WinForms in well under a day. Visual Studio handles writing all the data binding code for me, code that I'd have to write myself in any other language. Using one of the enterprise frameworks, sure, those all have boilerplate, in any language, especially the older frameworks. And for some tasks, the amount of boilerplate is…
Under a day ?? Make an app with pyqt5 or kivy and it's under an hour...
Last CRUD app I did in WinForms:
1. Auth
2. Real time push updates from my database
3. Platform native looking UI
4. Automatic 2 way data binding between my backing JSON and my UI controls.
I hadn't used C# for ~2 years, I had never used that particular DB library or done any work with JSON in C#.
I got it done in under 4 hours.
If I did it now, yeah, even faster.
The amount of code I wrote is insanely tiny. I wanted some custom date/time formatting stuff so I had to implement that myself.
I just checked the source out, I wrote under 120 LOC total, and that is including the repetitive ~70 LOC I did for handling days of the week and auto-formatting user entered times. (Time sucks, working with time sucks.)
Without that my code would've been limited to:
1. Wiring login button up to sending username/password to the DB 2. Attaching a listener to the DB (C# has had native event handling as a primitive type since forever!) 3. The save button to push stuff to the DB.
Did I have to drag and drop some UI elements onto a page? I sure did. It was rather nice.
WinForms was the go to solution for CRUD apps for a reason. Sure VB6 was probably better at popping CRUD apps out in no time, but after that died out, WinForms was a really good replacement.
Re: .NET Core 3.0
#88Earlier quoted context omitted.
> But rubyists would’ve loved C#. As a Rubyist, I'll admit that C# is the least bad of the C++/Java style of static OOP languages, but it was that it was always too tied to the .NET ecosystem and heavyweight enterprise tooling more than Microsoft's “supervillian role” with regard to FOSS that made it unattractive for lots of places where I would want to use Ruby. That's improved with Core, somewhat.
It improved with mono and it's great to see continuation with core by ms. I don't use it atm but I remember learning c# from their beta book before v1, it was better than java even at that time. I've used c# from objective-c macos app maybe 6 years ago, it was pleasure to write c#/objc interop with mono and see same codebase used on windows app working fine (even faster) on macos via mono. The state must look much ni…
There's a parallel world out there where the Gnome project and Linux distributions rallied around C# as a strong way to write applications, instead of the weird backlash/demonization they all soon received that ended such a brief "golden age".
Re: .NET Core 3.0
#89Earlier quoted context omitted.
VS is very good but I've been using Rider since the start of this year for most work, I found it to be a very strong competitor.
I've been Rider almost exclusively for about 2 years now, ever since I've been coding Core. VS is fine, but VS w/Resharper is a dog. With Rider, R# is a first class citizen, which makes a huge difference. Not to mention that the vim emulation and other addons are solid due to being shared with the intellij suite of apps.
Re: .NET Core 3.0
#90Earlier quoted context omitted.
It's great to see the enterprise world catching up with the tech world
I fail to see what the point of trying to use VS Code for .NET development would be. I suppose if you like tying one hand behind your back and making things more difficult for yourself for some reason. Or maybe you like cobbling together a rickety pile of plugins. If cost is a concern, there's Rider or even MonoDevelop.
Since dotnet core includes a CLI executable, I interact with the project through the CLI. I manually edit the config files. I could run the stack from a netbook if I wanted to.