tompazourek

Some Windows servers use the Windows Server Core edition and you can manage it only via terminal if you choose to. In those cases, a command line text editor is useful. I'd say it's not super common from my experience. More often I see people using RDP or SMB file shares for file editing.

Isn't k8s ingress itself the reverse proxy?

I'd add:

* Hangfire

* Quartz.NET

* NHibernate

* AutoMapper

* StackExchange.Redis

* the Castle project

* xUnit

* NUnit

* Serilog

* SimpleInjector

These are all very popular long maintained open source libraries I've seen used in many projects.

NHibernate is quite popular alternative to EF and I've seen it used on many projects, especially big apps. Some smaller apps also choose Dapper (by StackExchange) and avoid EF.

Regarding ASP.NET, you're right. There are some alternatives, but not used very often from my experience.

In my opinion, you can go a bit more low level in C# and have control over allocations, data copying, threads, etc. Also, .NET is a bit more general purpose than Node. If the workload is more about computation (CPU/GPU intensive stuff) or has some unusual technical requirements (uncommon protocols, interop, etc.), you can really benefit from being lower level and more generic.

But all this is very project specific... it's hard to make these sort of claims about performance.

Maybe AirPods will be supported, they have some spatial audio as well.

People who practice playing musical instruments eventually learn something similar. You shouldn't really push hard, you need to be relaxed and then the speed will come. Plus it's also lot more enjoyable.

Top-left isn't as unnatural for humans in my opinion. It's how you read and write text... Also it's natural for web pages as the top left is fixed.

Thanks. I always thought that all this IDE kind of stuff came from Visual Basic. But I guess Delphi was an influence too.

Can you please elaborate?

I think it's a similar pattern, but at a different layer.

You can compose methods, compose classes/instances (DI), compose libraries/assemblies, compose processes, microservices, or entire apps and multi-app systems. There are similar patterns of composition, just each is at a different level of abstraction of the whole thing.

Sometimes it makes more sense to compose it inside an app, sometimes it makes more sense to design it differently and compose on another layer. Sometimes it can be both or it's blurry and not clear...

Now that's what I call a document database.

Thank you for sharing this.