.NET Core is special because it increases the portability of your .NET code in case your cloud provider decides to jack up costs by 15% for no reason other than you are locked in. cough cough
What Makes .NET Core So Special?
181–190 of 247 posts
Re: What Makes .NET Core So Special?
#182Earlier quoted context omitted.
I'm curious: what was the problem with Go?
The domain experts all write C#, and I don’t have strong language preferences, so it’s easier for me to switch to C# than it is for them to switch to Go. There isn’t a real technology reason, it’s just team ergonomics.
And that is very smart decision making. Professional!
Re: What Makes .NET Core So Special?
#183I want to like .Net Core, I really do. But in my opinion its just not yet ready for serious use. An example. If you want to use .Net Core you can't use entity framework, you have to use EF Core, which doesn't yet support mapping to views or stored procs, only tables. Now you might think that's fine, maybe you only want to map to tables. But it's the same story all over the ecosystem. Many major projects have a separa…
> you have to use EF Core, which doesn't yet support mapping to views or stored procs, only tables.
At least this one is not true: https://docs.microsoft.com/en-us/ef/core/modeling/query-type...
Re: What Makes .NET Core So Special?
#184I want to like .Net Core, I really do. But in my opinion its just not yet ready for serious use. An example. If you want to use .Net Core you can't use entity framework, you have to use EF Core, which doesn't yet support mapping to views or stored procs, only tables. Now you might think that's fine, maybe you only want to map to tables. But it's the same story all over the ecosystem. Many major projects have a separa…
Maybe you will find that rolling a little of your own code instead of depending on libraries as much is less hard than you imagined and has some nice benefits? EF isn't a necessity, many shops prefer not to use it at all. Core is the future so if one wants to keep using .NET at all they should find a way or switch to something else.
.NET Core is the future just like moving on from COBOL and FORTRAN was the move 30+ years ago, eh?
Re: What Makes .NET Core So Special?
#185Earlier quoted context omitted.
You can usually cut the cold start performance in half by enabling Tiered Compilation. It's just one parameter in your project file, or via an environment variable. Disclaimer: I work on performance in the ASP.NET team.
What are you disclaiming?
Re: What Makes .NET Core So Special?
#186I want to like .Net Core, I really do. But in my opinion its just not yet ready for serious use. An example. If you want to use .Net Core you can't use entity framework, you have to use EF Core, which doesn't yet support mapping to views or stored procs, only tables. Now you might think that's fine, maybe you only want to map to tables. But it's the same story all over the ecosystem. Many major projects have a separa…
Funny, I tried .NET Core with EF at a Hackathon and thought EF really went a long way. Had no idea about the restrictions, thanks for the heads up.
Btw, we use .NET core in prod, but we have weird DB access through a third party API, so I didn't need to think about data mapping.
Re: What Makes .NET Core So Special?
#187I want to like .Net Core, I really do. But in my opinion its just not yet ready for serious use. An example. If you want to use .Net Core you can't use entity framework, you have to use EF Core, which doesn't yet support mapping to views or stored procs, only tables. Now you might think that's fine, maybe you only want to map to tables. But it's the same story all over the ecosystem. Many major projects have a separa…
We use .NET core in production and are very happy. A mixture of EF Core (for ad-hoc queries) and Dapper (for stored procs) works just fine. Also, new in EF Core 2.1, you can map views and stored procs just fine: https://docs.microsoft.com/en-us/ef/core/modeling/query-type... . That's your only specific example - what other functionality are you missing? You're not willing to commit to .NET core but you admit that Net…
Yes, totally agree- I worked on a project that wasn't Core but regular MVC + EF and Dapper which surprisingly worked out well. Actually so well I started mentioning it as a feature but really was just too lazy to redo all the dapper stuff since it worked so well.
Re: What Makes .NET Core So Special?
#188Earlier quoted context omitted.
> I really hope the platform can break out of the Microsoft silo and attract talent from other dev communities The problem is often trust. Like so many Microsoft projects, to me the goal of .Net Core seems to be to get as much people as possible on to a proprietary language and/or get as many devs as possible onto developing stuff that doesn't hurt Microsoft. There's no guarantee that MS will not pull the plug at som…
Also why I don't see .NET Core going anywhere, it's controlled by the same old Microsoft who have a massive conflict of interest for directing everyone to use their preferred libraries and services. Unlike every other popular language which is typically developed with a transparent independent governance model whose direction benefit all libraries and services equally, instead of giving their own preferential treatme…
Using .net core, or even framework on other cloud providers is easy enough. .NET Framework is tied to a Windows environment, but core isn't.
I don't get all this hate against Microsoft because they suggest or prefer things they worked on as solutions, without actually tieing you to them. Do you work on software for years and then tell everyone to use something else?
If it was actually tied to their other services then I could see the reason to avoid it, but if using .net core without windows, azure, or sql server then I dony see how you are actually tied to it
Re: What Makes .NET Core So Special?
#189Earlier quoted context omitted.
If your end game is working professionally just check what is more in demand in your geographic location. Personal opinion C# is a lot better than Java. You have less boilerplate code (getter and setter in 2018, really?) and lambdas are great. But really both are similar so you can pretty much just start with one and still find your way in the other.
Honestly, people still using the getter and setter argument in 2018 as a reason to pick a language should not be taken seriously. Indeed Java has more boilerplate, but honestly I've never been bothered by it (as you can generate most within your IDE) and because its explicitly written down it can make code more readable. And Java also has lambda's.
lambda's are much more limited in flexibility when compared with linq. Because of the way java lambda's work, I imagine there are some scenarios where they are more performant, but it probably comes down to the specific problem/usage.
Re: What Makes .NET Core So Special?
#190Earlier quoted context omitted.
If you want to be on the JVM I highly recommend giving Kotlin a look before Java. Great language and excellent tooling.
I would like to learn Kotlin, but I've no prior knowledge about Java... That's a real impediment? If it isn't, do you know (by chance) about some resource(s) for a total newbie/newcomer to the language? thanks in advance.
jetbrains is doing a very good job of creating good error messages, but just like any other jvm language, you can run into huge, messy, jvm stacktraces. In my experience, Java/jvm proficiency is useful