Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

.NET Orleans

dotnet.github.io

Post reply on HN
Print view View original

231–240 of 287 posts

Re: .NET Orleans

#231

Post by drachenstern »

pjmlp wrote: post #172
manigandham wrote: post #171

Earlier quoted context omitted.

Why the long wait?

Because .NET Core isn't fully compatible with .NET Framework, and there are lots of stuff which people are willing to spend money porting them. In the consulting business "I rewrote X in Y" blog posts only happen when someone takes the time to budget the project, because there is someone doing the math of developer time x cost per hour . Then .NET Framework has been Windows specific for 20 years, there are lots of .N…

I really thought the question was serverside technologies, not desktop?

Re: .NET Orleans

#232

Post by drachenstern »

shanselman wrote: post #221
Thaxll wrote: post #87

Earlier quoted context omitted.

I'm pretty sure net core will remain for a long time in the enterprise world before making anything in the more open source / general public. It's 2020 I can't name a single server side known application built in net core.

Stackoverflow, Bing, UPS, Raygun.com

Oh Scott... it's not like anyone has heard of StackOverflow and they certainly don't discuss their architecture or performance metrics ...

https://stackexchange.com/performance

https://hub.packtpub.com/stack-exchange-migrates-to-net-enti...

And there's definitely nobody can see the current state of their underlying technologies to know about their transitions https://github.com/StackExchange

So ... this all just sounds weird for a startup with a weird name?

/s

Re: .NET Orleans

#233

Post by pjmlp »

drachenstern wrote: post #231
pjmlp wrote: post #172

Earlier quoted context omitted.

Because .NET Core isn't fully compatible with .NET Framework, and there are lots of stuff which people are willing to spend money porting them. In the consulting business "I rewrote X in Y" blog posts only happen when someone takes the time to budget the project, because there is someone doing the math of developer time x cost per hour . Then .NET Framework has been Windows specific for 20 years, there are lots of .N…

I really thought the question was serverside technologies, not desktop?

Answer applies to server as well.

Re: .NET Orleans

#234

Post by m-oswald »

Thaxll wrote: post #87
tmpz22 wrote: post #81

I spent some time learning dotnet core this year and with the slow-grind progress Microsoft has made it really does look like the technology stack might start to replace Java, Go, Rails, NodeJS, over the next decade. You can really feel Microsoft's experience in language development and enterprise software development coming together to provide better ecosystem ergonomics than other frameworks and toolchains. Specifi…

I'm pretty sure net core will remain for a long time in the enterprise world before making anything in the more open source / general public. It's 2020 I can't name a single server side known application built in net core.

GitHub Actions

Re: .NET Orleans

#235

Post by spaetzleesser »

cutler wrote: post #143
spaetzleesser wrote: post #133

Earlier quoted context omitted.

Same here. The Java ecosystem has almost everything you could ever imagine needing so it’s a safer bet. Maybe it’s not as shiny but it works. I don’t understand why MS doesn’t provide the ability to call Java code from .NET. It would open up a lot of libraries to the platform. Right now there are a lot of libraries that are first class in Java but have either no or only half baked .NET ports.

Which libraries? Could you give some examples?

Lucene, Bouncy Castle, a lot of niche research code is written in Java.

Re: .NET Orleans

#236

Post by manigandham »

nullsense wrote: post #193
manigandham wrote: post #136

Earlier quoted context omitted.

Here's the .NET 5 announcement which wraps up everything: https://devblogs.microsoft.com/dotnet/introducing-net-5/ .NET windows/desktop framework stopped at version 4.8 and .NET Core has spent 4 years incrementing to version 3, so .NET 5 is a merger of everything into a single framework again. Mono will still exist since it's used by Xamarin for mobile and Unity for games. AOT is mentioned in the article and comments…

>.NET 5 is a merger of everything into a single framework again Is it a merger or a replacement? I won't be able to just take my huge legacy .NET 4.7.2 app and just change the runtime to .NET 5 and hit the go button right? Seems for the app I work on at least the upgrade path is a full rewrite :/

It's technically a merger. It's the next version of .NET Core after v3.0 but jumping ahead to v5.0 and dropping the "Core" designation, and then merging in parts of Mono, AOT toolchain, and even more of the (upgrade) bits of the classic framework.

You might be able to get pretty far with just a framework switch. The RC is already out so try it. You'll probably have to update the csproj/sln files at a minimum and fix some known API differences but it's unlikely you need an entire rewrite.

Re: .NET Orleans

#237

Post by dmitryminkovsky »

cutler wrote: post #138
dmitryminkovsky wrote: post #91

Earlier quoted context omitted.

I really enjoy how TS is the same on server and client. The C# runtime is way richer, but I like the TS type system more. Not sure I’d want to use different platforms on backend/front end even if C# did server rendering like React.

Not sure what you mean by different platforms. Did you mean languages as React and Node are separate entities? Personally, if I had to hire a developer the minimum requirement would be competence in JS/React and a statically-compiled server-side language. JS-only developers are to be avoided.

Different platforms meaning JavaScript vs C# vs Java and their respective runtimes. Yes server and client JS are not the same runtime but they are easy enough to smooth over that they are practically “the same”

Yes a JS only developer is probably lacks certain experience but I am well versed in Java and have had solid exposure to C#, like they them both a lot, but today would prefer to use TS on backend and front end for any small project. The fact that I can share types and validation code (Joi) on both server and client is really powerful in my opinion. There’s only so much you have time to focus on when you’re working on a small project. Context switching two platforms is a big impediment in such cases.

Re: .NET Orleans

#238

Post by manigandham »

FridgeSeal wrote: post #186
manigandham wrote: post #142

Earlier quoted context omitted.

Lack of higher-level language features requiring code duplication/generation, a lean standard library usually necessitating 3rd-party packages, and an utterly terrible module system and fragile tooling setup. Go is still far better than JS, but both are behind in modules, packaging and overall structure as compared to .NET. gofmt is nice though, more languages should have that.

For all it's other woes, I've had like 80% fewer issues with Go's tooling than .Net's. - Getting packages installed: trivial - Getting clean builds: trivial - Build and run works near perfectly In comparison .net seems designed to be used _only_ via Visual Studio: - Why does it re-download the packages each time I ask it to build? - Why does VS freak out sometimes when there's a terminal window left over from a previ…

.NET Core is CLI first: https://docs.microsoft.com/en-us/dotnet/core/tools/

We use it all the time, no VS required. You don't have to edit any XML files today, and can use a simple editor like Visual Studio Code or notepad if you want.

Do you have some big old solution that you're working with?

Re: .NET Orleans

#239

Post by manigandham »

FridgeSeal wrote: post #191
aliswe wrote: post #181

Earlier quoted context omitted.

I suspect you haven't yet seen tge power of LINQ, it's not the chaining that is its point - it's the lazy evaluation. It's not at all limited to DB operations.

Every use of LINQ I've seen in .Net codebases has been to perform (more slowly) transformations or aggregations that should have done in the database.

Sounds like you've worked with poor code/developers. LINQ with EF translates into DB queries including aggreations and transformations. That's the whole point of compiling the query, unless someone either didn't understand the query they were writing or explicitly chose client-side evaluation.

Re: .NET Orleans

#240

Post by cutler »

nullsense wrote: post #192
cutler wrote: post #138

Earlier quoted context omitted.

Not sure what you mean by different platforms. Did you mean languages as React and Node are separate entities? Personally, if I had to hire a developer the minimum requirement would be competence in JS/React and a statically-compiled server-side language. JS-only developers are to be avoided.

Out of curiosity what if I'm good, say above average, with C# backend, but never used React commercially, though have used Vue on personal projects for the last several years, but consider my JS a bit of a weak spot?

If was thinking more about full-stack development so professionally you'd need some commercial exposure with JS.
Post reply on HN