Kogasa

Didn’t ask

You don’t need to use the same one. Just don’t expose it publicly in libraries.

It’s a lot better with some notable exceptions. First, .NET Core is multiplatform by design, so it is by default quite portable. The .NET Core CLI is extremely powerful and means a CLI workflow is totally feasible (and also simplifies CI pipelines). The new “multiplatform” application framework, MAUI, runs on Windows, Mac, iOS, and Android, but not Linux/GTK/QT etc. You can maybe attribute this to the design philosophy of abstracting native controls, of which “Linux” itself has none, but either way it’s useless on Linux. Third party frameworks like Avalonia do work very well on Linux.

Despite .NET being relatively friendly with Open Source, Java will probably remain the first choice for FOSS devs for a while, if only due to history and traction. You could write a C# Lemmy alternative, but it wouldn’t necessarily be faster or simpler or better in any particular way than a Java version. I’d certainly rather contribute in Java than start from scratch in C#.

C# isn’t really the go-to for high scale distributed systems. But it’s extremely easy for a small team of developers to set up a really solid service really quickly. I don’t have experience with Go so I can’t really compare, but I find ASP.NET Core very pleasant to work with, and I also appreciate the suitability of C# and .NET libraries for both backend and frontend work.

Nullable reference types are (a completely mandatory) bandaid fix in my opinion as a .net dev. You will encounter lots of edge cases where the compiler is unable to determine the nullability of an object, e.g. when using dependency injection to populate a field, or when using other unusual control flows like MediatR. You can suppress the warnings manually at the slight risk of lying to the analyzer. Objects supplied by external library code may or may not be annotated, and they may or may not be annotated correctly. The lack of compile-time null checking is occasionally an issue. But that said, NRT makes nullability a significantly smaller issue in C# than it used to be

You can also easily write your own option monad or use a tiny library that does.

At some level, the goal of customer service is to prevent customers from bothering your employees. A sufficiently confusing first level of customer service is just as good as one that actually attempts to help you because it convinces you to give up

That would make it impure

Docker is lighter and easier to manage than a VM. I run a collection of services as docker compose services inside a NixOS host VM. It’s easy to start, stop, monitor, update etc. even from a different computer (via ssh or docker contexts). It’s great.

deleted by creator

It’s just as easy to run in a Docker container and I would recommend this anyway.

The compositor will have to implement a CLI. Sway has an IPC socket and CLI just like i3 and I can use this to hide windows.

What platforms would you like your app to run on? Then, which UI framework supporting those platforms would you like to use? Then, look at the framework’s documentation to find a sample starter project that you can run as an app, and modify it from there

What’s wrong with mssql besides licensing? It’s fast

If you have a lot of semantic breakpoints (like the end of a concept) that don’t line up with syntactic breakpoints (like the end of a method or expression body) your code probably needs to be refactored. If you don’t, then automatic code formatting is probably all you need.

I understand… In a programming environment 99.999% of tabs aren’t after any other text.

Err, why would there ever be something besides a tab before a tab? Are we doing ASCII art?

I do not know what that means

If only we were still having the conversation.