Live data from Hacker News

.NET Team Survey: Native AOT

github.com

91–100 of 103 posts

Re: .NET Team Survey: Native AOT

#91
post #38

Unfortunately reflection is so widely used in .Net libraries and core frameworks that code removal during linking becomes more or a less impossible without spending A LONG TIME decorating an xml file with code removal exceptions. I have done it on Xamarin iOS, it is not fun. So one of the prime dreams of having .net AOT of having an easy way to create a COMPACT self contained native exectuable dies when it hits real…

> So one of the prime dreams of having .net AOT of having an easy way to create a COMPACT self contained native exectuable dies when it hits real code.

They are working on improving that: https://github.com/dotnet/designs/blob/master/accepted/2020/...

Re: .NET Team Survey: Native AOT

#92
post #31

Earlier quoted context omitted.

Right, but I think the complaint was that it was still immature and missing some use-cases covered by the old framework. Anyway, I do hope they succeed and the .NET 5 unification goes smoothly. I want those C# 9 features - but I also need some old third-party libraries to keep working.

Which ones, if you don't mind me asking out of curiosity?

Which features? Mostly data classes, a.k.a. records, and (from C# 8) non-nullable references. Kotlin has had these features for years and it makes things so much easier and cleaner IMHO.

Re: .NET Team Survey: Native AOT

#93
post #87

Earlier quoted context omitted.

Starting with .Net 5, there will be one major release exactly once a year, and one LTS release exactly once every two years. (see https://devblogs.microsoft.com/dotnet/introducing-net-5/ )

.NET 5 is a no go for those of us who are stuck on netfx. There is no compatibility.

> There is no compatibility

That's not true.

Re: .NET Team Survey: Native AOT

#94

Earlier quoted context omitted.

.NET 5 is a no go for those of us who are stuck on netfx. There is no compatibility.

> There is no compatibility That's not true.

I mean for existing pre-built binary libraries built for netfx (which is what we are stuck with as dependencies in many cases) there is no way to use them under core/net5 that I’m aware of (I’d be happy to learn that it was!).

E.g I have a huge library from Autodesk that targets 4.6.2 and I consume it from 4.7.1 now. I don’t think they have a plan to support a Core/net5 framework so my app can’t either.

Obviously you can rebuild libraries and target both/netstandard/whatever but that’s not what I mean.

Re: .NET Team Survey: Native AOT

#95

Earlier quoted context omitted.

> There is no compatibility That's not true.

I mean for existing pre-built binary libraries built for netfx (which is what we are stuck with as dependencies in many cases) there is no way to use them under core/net5 that I’m aware of (I’d be happy to learn that it was!). E.g I have a huge library from Autodesk that targets 4.6.2 and I consume it from 4.7.1 now. I don’t think they have a plan to support a Core/net5 framework so my app can’t either. Obviously you…

Seems to me more like the issue is with Autodesk and with an unmaintained binary dependency, not with .NET at all.

Re: .NET Team Survey: Native AOT

#96
post #2

I’ve been a C# developer for two (almost) decades, how do people even keep up with these rapid changes in the post Core world and what/when to use them? This is a serious question by the way.

Every (halve? ) year I check the just c# release notes and create an application that incorporates the new things.

C# 9 is next on the list.

Re: .NET Team Survey: Native AOT

#97
post #7

Earlier quoted context omitted.

>The new "open" development style of .NET Core is not my cup of tea. It's now riddled with MVP features that are 80% complete, bug-ridden, and undocumented other than couple of blog articles. .NET Framework is a product, .NET Core is a OSS project. When .NET 5 will ship it will be even worse since .NET Framework people will just expect things to work.

> It's now riddled with MVP features that are 80% complete, bug-ridden, and undocumented other than couple of blog articles I work full time with ASP .NET Core 3.1 projects, and I don't recognise this at all. I don't think that it's correct.

Same here, this is just utter nonsense. I have to assume the person that wrote that comment hadn't actually been using dotnet Core at all. I note how they provide no examples of bugs from this "bug-ridden" and "undocumented" platform.

I've been using dotnet since it was originally created many moons ago, and dotnet core is the best incarnation yet. Documentation is excellent - I don't think I've ever once came across an undocumented feature?!

Re: .NET Team Survey: Native AOT

#98

Earlier quoted context omitted.

Just this week I wanted to spin up a minimalist ASP.NET page for "tyre-kicking" of new infra builds. You know, something that just coughs up a single page with some basic info, such as the regional options, time zone, current time, and the latency to the SQL Server. This checks that the infra guys did their job and that the AD accounts and firewall ports are in place. I wanted to write 1 page with just some dynamic l…

>No dependency injection. No JavaScript frameworks. >Visual Studio 2019 no longer ships with a web project template that does that. Every single project type coughs up megabytes of crap and a bunch of scaffolding. Yeah, the way depency injection and multiple JS frameworks are shoved down your throat in .NET Core is sooo annoying.

> Yeah, the way depency injection and multiple JS frameworks are shoved down your throat in .NET Core is sooo annoying

I've been using dotnet core for years and precisely zero times I have had any JS framework shoved down my throat.

Re: .NET Team Survey: Native AOT

#99
post #97

Earlier quoted context omitted.

> It's now riddled with MVP features that are 80% complete, bug-ridden, and undocumented other than couple of blog articles I work full time with ASP .NET Core 3.1 projects, and I don't recognise this at all. I don't think that it's correct.

Same here, this is just utter nonsense. I have to assume the person that wrote that comment hadn't actually been using dotnet Core at all. I note how they provide no examples of bugs from this "bug-ridden" and "undocumented" platform. I've been using dotnet since it was originally created many moons ago, and dotnet core is the best incarnation yet. Documentation is excellent - I don't think I've ever once came across…

> dotnet core is the best incarnation yet.

To be fair, we didn't use .NET Core extensively before .NET Core 2.1, because it was not quite ready yet. But since 2.1, we haven't looked back.

Re: .NET Team Survey: Native AOT

#100

Earlier quoted context omitted.

I suspect a lot of people (myself included) will just stop at 4.8.

Just this week I wanted to spin up a minimalist ASP.NET page for "tyre-kicking" of new infra builds. You know, something that just coughs up a single page with some basic info, such as the regional options, time zone, current time, and the latency to the SQL Server. This checks that the infra guys did their job and that the AD accounts and firewall ports are in place. I wanted to write 1 page with just some dynamic l…

Not sure how you miss the Empty project template: https://i2.wp.com/anthonygiretti.com/wp-content/uploads/2020...

With the new request handling pipeline you hardly need a template for a single page diagnostic.

https://anthonygiretti.com/2020/06/29/nano-services-with-asp...

Post reply on HN