Hacker News Reader

Comment by esistgut | Hacker News Reader

Can anyone compare this to other backend frameworks like Django and Rails? Are non-Windows operating systems well supported as development platforms? I did some quick searches and the standard Visual Studio popped out a lot inside documentation, doesn't seem like a good sign. How would you compare it to Elixir and Phoenix?

View on HN

It works perfectly fine on non Windows environments from our experience. I am running myself several production apps in Linux containers in Kubernetes in the Google Cloud and it works like a charm. Also from a dev point of view I know many devs who work from a Mac with Visual Studio Code and they love it.

Just to add, you don't need to use Visual Studio anything, you could work in VIM/Emacs on Linux and never leave the terminal, and do full stack .net core development if you wanted to.

I find you can use vim/emacs when working with interpreted environments like python. when using java or .NET the stack gets much bigger and advanced intellisense becomes a bigger advantage.

Personal experience: if youre beginning a foray into strongly-typed large stacks like java/.net be prepared to trade in your minimal vim/emacs as an IDE for something heavier duty such as visualstudio/intellij.

If your're like me and burned vim mnemonics into your brain its not terrible, there are plugins which make the editor sort of behave vim-style (but little to no plugin support and vimscript is out the window)

Vim literally uses the same autocompletion library that VSCode uses. Omnisharp.

Im sorry to say it but vim/omnisharp is nowhere close to usable in a professional setting (based on my attempts about 8 months back). Its like eclim. Compared to an out-of-box installation of visual studio (even without resharper) I'm spending way more time fighting with my tools than I can afford. I fear this vim-omnisharp effort on a fundamental level will never be worthwhile except for the most trivial of .NET projects.

EDIT: vs-code is a FOSS project, For .NET I think this is a much better direction.

Its different from Django. Asp.net core focuses on being modular, whereas django focuses on providing conventions to aide in development. I develop with both on mac using VS code.

I still prefer django over it because the community provides so much additonal value. But MS seems motivated to get core tonthat1 level.

It’s been a while since I used Django or rails, but asp.net has the same feature set. Asp.net is more modular than I remember the other frameworks being but that has probably changed in the last few years.

With .net core development is supported on macOS and Linux as well as windows with visual studio code. I develop on macOS myself.

If you’re not familiar with asp.net it’ll be a bit confusing. There are now two versions - asp.net which is windows only and asp.net core which is cross platform. Also there has been a lot of flux in .net core so older tutorials are often wrong.

Don't forget Visual Studio for Mac (improved MonoDevelop improved Xamarin Studio)

Compared to Visual Studio + ReSharper, Visual Studio for Mac is quite a step back (putting it mildly). I've high hopes for Rider (cross-platform JetBrains IDE for .NET that was just released), though I haven't tried it yet.

I've been using Rider and it's been pretty good. This shouldn't be a surprise. Remember that JetBrains started with ReSharper. This is basically their home turf.

That said, third party IDEs can always be expected to be slightly behind the first party stuff. But in this case I think it's worth it and might actually be a good litmus test for adopting the next releases.

The main problem for me a while ago were memory leaks in mod_mono. Everything was running mostly fine for the first week or so, then mod_mono was starting to eat more and more memory. A weekly restart would solve the problem, but I hope this is resolved now. I'm afraid under a higher workload this would bring the server to its knees.

Asp.net core by default runs on .net core rather than mono. So should not be an issue.

A lot of documentation is a bad sign to you?

Also, non-Windows OS are supported as a first-class citizens.

> A lot of documentation is a bad sign to you?

A lot of documentation that specifically talked about Visual Studio and not any other (more platform agnostic) tooling is probably what made them say it was a bad sign.

I've been working with dotnet core the past couple months. It takes a lot of Googling to find useful answers still. The documentation is not particularly comprehensive and it is true that the docs are frequently images of "How to use visual studio to do this" which is never useful for vscode users. I'm actually starting to understand why StackOverflow is such a commonly used resource because of it (in python land I almost never need to defer to stack overflow).

That said, still enjoying the ecosystem, but docs-wise it's kind of a mess. I was thinking I'd start compiling a few cheat sheets for things like EF... This page for example is just totally busted:

https://code.msdn.microsoft.com/101-LINQ-Samples-3fb9811b

And that's linked directly from:

https://docs.microsoft.com/en-us/ef/core/querying/basic

Reply on news.ycombinator.com