Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Bad... No.
But you should read the release notes, get an understanding of the differences between .NET FW and .NET Core.
Visual Studio is never required to build C# projects... ;) -
Well... It depends on your tolerance level.
Technically debugging could be done via windbg, compiling / building via command line...
Hence the smiley. ;)
But I think there are other solutions for C#
Eg.
https://www.jetbrains.com/rider/ -
Bubbles66126y@IntrusionCM I personally prefer command line for stuff with a text editor but I still wanna use VS for the bigger stuff
-
Voxera113886y@filthyranter .net core is a major performance upgrade over fw or mono so I fail to see why you avoid it.
And since netcore runs natively on linux you get all improvements directly when they are released. -
@Voxera
Do you have any reliable sources for this? Afaik the main difference is the support for multiple OSes - and as such only supporting a part of the APIs .NET Framework supports. -
devTea219106yI learn most of the basic on .Net, there’s also more .Net question on SO. Ehh working on them feels kinda same more or less
-
Learning C# trying to avoid VS? Why would you not use the best IDE ever (at least for C#/.NET stack)? You don't go learn to be a carpenter but avoid using a hammer.
-
Voxera113886y@IntrusionCM according to multipel blogs from people working on net core they have been doing a lot of under the hood rewriting using for example the new span of T and like to improve performance. More so than has been done on the net framework implementation since they are rewriting a lot anyway for net core.
I know specifically the aspnetcore stack is supposed to be a LOT faster than asp.net. -
@IntrusionCM you can basically look at the code for .net core and prove this for yourself.
If you think about it it makes sense too. An open sourced platform made to work everywhere(.net core) vs an unofficial distribution(mono) its pretty much a no brainer. -
@bubbles i would recommend sticking to .net core. You can use vs code with it if you don't want to use visual studio ide and you will be fine.
-
@AlexCx04 that's ... pretty dumb.
Reading or infering performance from code is - especially given complexity - impossibro.
And stating that unofficial means slower... Especially in conjunction with the previous sentence of OS compatibility... That's beyond stupid.
Especially for something like the Dot Net framework which is so closely tied to Windows APIs that they cannot be ported to an OS independent API...
And seriously... We are talking about a compiler platform mixed with several APIs for OS abstraction / GUI and so on...?!
There might be a lot more complex stuff out there, but saying you can 'easily' understand if a compiler generates better code by looking at the source code... Is insane. -
@IntrusionCM reading comprehension ain't your strongest suit isn't it? The reason why I mentioned that you can READ the source code and find for yourself is so that YOU can SEE the performance improvements from one platform over the other.
And show me where I said you can "easily" verify this? It takes skill bud. If you don't have it then that is on you. Not on me.
What I did mention that it would make sense to believe that an official open source port with the full backup of a multinational company would have better improvements than an unofficial port. This is not a moronic assumption, whereas believing any different is just delusional. Whereas you believe in it or not thats fine, but there is no reason to go full asshole on someone without proper context. -
@AleCx04
There was a reason I used the quotes around easy...
And No... What u are saying isn't true.
Mono is developed by Xamarin... Which was bought (officially) 2016 by Microsoft. And I guess wildly that the main reason was to foster .NET core 1.0 which was released... 2016. (after 5.0 which began in 2014...)
And afaik .Net Core used a lot of Mono, eg the linker...
And the reason I got very upset is because it has nothing to do with skill... Saying you can read the source Code and compare the Performance.... Sorry. But for a Project of this size, this would require months of work....
And that is when I get angry. I Love FOSS and Open Source, but be realistic when posting about reading the Source Code. -
@IntrusionCM negative homeslice. I never said it would ve easy or timely. You got upser for assuming too much shit and looking for stuff to get mad at.
Peace buddy!
Related Rants
So I’m starting to learn C# is it a bad idea to use .NET Core to learn the basics of the language? And for the advanced stuff use visual studio when it’s needed? I’m just trying to avoid Visual studio tbh
question
dotnet core
c#
dotnet