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

131–140 of 287 posts

Re: .NET Orleans

#131

Post by x0n »

ricksharp wrote: post #124
x0n wrote: post #106

Earlier quoted context omitted.

I think maybe you stepped out of .net at the wrong time. Pattern matching, records, discriminated unions (c# 10) etc are here and on they way. Lots of functional features being integrated into C# with every update.

I’ve been using C# since 2003, but I’m still 5 times faster in typescript & react. Besides that the typescript type system is insane. It’s cool to hear about discriminated unions though.

The more haste, the less speed! Yeah, I get ya. Love me some typescript.

Re: .NET Orleans

#132

Post by Rapzid »

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.

I'm incredibly interested in this. A daydream of mine is to create OSS infrastructure/SRE systems in .Net. F# if it makes sense. <3 F#.

Re: .NET Orleans

#133

Post by spaetzleesser »

yyyuutt wrote: post #112
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 spent 10 years doing C# on a big system and love it. However it never got the momentum Java did so I've switched. I prefer C# over Java, I hate a lot of Spring attribute/factory/builder craziness, but Java has so much more wider support I would always choose it first now.

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.

Re: .NET Orleans

#134

Post by mattferderer »

manigandham wrote: post #121
mattferderer wrote: post #113

Earlier quoted context omitted.

Sadly Node Services has gone the way of the Dodo bird. I'm not aware of any replacement. https://github.com/dotnet/aspnetcore/issues/12890

Yea I'm in that thread. It's no longer maintained by Microsoft but the code still exists and runs just fine, and there's not much to maintain other than keeping up with the Node releases and API changes. The closest community project is https://github.com/JeringTech/Javascript.NodeJS and should be a drop-in replacement for `INodeServices` If you just want V8/JS scripting then there's https://github.com/microsoft/Clea…

Have you used it by chance with .NET Core 3 or .NET 5? I was considering using it for some tooling during the build process without using Node.

Re: .NET Orleans

#135

Post by KurtMueller »

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…

Is it as good as rails? When I run a rails new command, I can setup my postgres connection, nodejs and webpack libraries, rails core library in one command. Rails has database migrations with conventions i like - the timestamp and a file name that represents the action to be performed against the database (e.g. AddNameToBlogs) which that can also be rolled back.

I also really like the Rails restful router which is strongly tied to its controllers.

I could go on. I really like that Rails gives me strong, opinionated conventions but also allows me to configure things to be liking if needed.

I want to love .net core - I really like F#. Any other rails dev out there make the transition to .net core?

Re: .NET Orleans

#136

Post by manigandham »

atombender wrote: post #127
manigandham wrote: post #122

Earlier quoted context omitted.

Officially it's been pushed back. The priority has been the unification of all the different runtimes and platforms first, which is coming with the big .NET 5 release.

Is there a document describing this plan? Will this replace .NET Core, CoreRT, etc.? As someone who isn't a .NET developer, the sheer proliferation of runtimes and platforms is super confusing, and I can never remember what's what between, .NET, .NET Native, .NET Framework, .NET Core, Mono, CoreRT, etc. If this is getting cleaned up, that's great news.

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, and there's also this big thread in the CoreRT repo if you want to see more discussions: https://github.com/dotnet/corert/issues/7200

Re: .NET Orleans

#137

Post by cutler »

manigandham wrote: post #94
tmpz22 wrote: post #86

Earlier quoted context omitted.

The coup de grace is functioning and sane server side rendering of ReactJS apps by c# applications. If Microsoft can make that easy and simple it will lead to a huge churn as many software companies replace less efficient nodeJS applications for that use case. Typescript will always have its placed client-side but there will be huge user benefits if we can have more and better server side rendering.

You can already do that by running Node with SSR (or any npm/js code) in .NET using Node Services [1] or use ReactJS.NET that packages everything for you [2]. But Microsoft won't officially do any more since they have Blazor which lets you run C#/.NET in the browser with both client-side WASM and server-side SignalR/websocket running modes. It's much more advanced and functional than React already. [3] 1. https://cha…

Blazor is currenlty hobbled by having to haul its runtime across the wire and is thus not in a position to compete with React or Vue.

Re: .NET Orleans

#138

Post by cutler »

dmitryminkovsky wrote: post #91
tmpz22 wrote: post #86

Earlier quoted context omitted.

The coup de grace is functioning and sane server side rendering of ReactJS apps by c# applications. If Microsoft can make that easy and simple it will lead to a huge churn as many software companies replace less efficient nodeJS applications for that use case. Typescript will always have its placed client-side but there will be huge user benefits if we can have more and better server side rendering.

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.

Re: .NET Orleans

#139

Post by fgonzag »

SergeyBykov wrote: post #69
fgonzag wrote: post #58

Earlier quoted context omitted.

Since you're an expert on both, do you mind discussing which of the two you like better? And the reasons behind it?

After more than a decade of working on Orleans and only three weeks on Temporal it's foolish of me to talk about what I "like better" :-). I'm working on a couple of conference talks to compare the two approaches. In short, Orleans is biased towards quick low latency operations. Longer running workflow style operations are totally doable, but require extra application logic and thinking. Temporal's main abstraction i…

Awesome! Thanks for the quick comparison

Re: .NET Orleans

#140

Post by cutler »

TheRealDunkirk wrote: post #117
manigandham wrote: post #104

Earlier quoted context omitted.

Very fast, statically typed, clean language design with features like LINQ for data operations and fantastic async support, cross-platform, comprehensive standard library, advanced ORMs like EntityFramework and NHibernate, easy deployment including docker/self-contained/single-file, build anything from web/mobile/desktop apps, best-in-class IDE and tooling, Blazor UI component framework running .NET in the browser, s…

> LINQ for data operations > advanced ORMs like EntityFramework and NHibernate I've used all of these. Rails' ActiveRecord blows all of them clean out of the water.

ActiveRecord surpasses all other ORMs in memory usage and slow execution, that's for sure.
Post reply on HN