Bicep is just a set of macros for the JSON templating. I get why it was invented, I tried to use it about a dozen times, have always fallen back to either Terraform or raw Azure templates (which I actually prefer since they’re so, so easy to handle programmatically and work essentially like serialized API call data).
25% of the first 4GB of memory,
20% of the next 4GB of memory (up to 8GB),
10% of the next 8GB of memory (up to 16GB),
6% of the next 112GB of memory (up to 128GB),
2% of any memory above 128GB
"AKS reserves an additional 2GB for system process in Windows nodes that are not part of the calculated memory."
It is quite slow on android IMHO. At least for me, in comparison with Chrome.
I also use ublock origin in android which should make loading page faster I guess but unless the page is absolutely awful, chrome remains faster even with ads on.
More important than being open source was the fact that it was Windows only for the first 15-ish years of its existence.
Mono never got traction within the startup culture. In part, because it operated in a legal grey area for many years regarding MS patents for web (or web adjacent) technologies like ASP.NET and ADO.NET.
Microsoft made some extremely generous patent grants to Mono and several major Linux Distributions relatively early in Mono's history. Microsoft didn't seem to want to repeat the mistakes that led to their divorce with Java and the early foundations of .NET with their relationship with Mono. In my experience of it, most of the "legal grey area" concerns around Mono for a lot of its history was either truly outdated/ignorant advice or intentional FUD from antagonists (many of which just hated anything Microsoft indirectly touches no matter what).
I think it depends on who you are. In 2007, a lot of people distrusted Microsoft and with good reason. They'd spent a lot of time extinguishing competitors. .NET Core was initially released in 2016, but Microsoft wasn't saying that .NET Core was their plan for the future. It seemed like an experiment they'd likely kill off or that it might just be a small subset of .NET.
I think saying that Microsoft started open sourcing .NET in 2007 feels a bit disingenuous. Plus, wasn't it source-available under the Microsoft Reference License? Regardless, .NET was still tied to Windows unless you wanted to use Mono (which was slow and had an uncertain future).
If you were someone who developed on Mac or Linux and deployed to Linux, you couldn't choose .NET in 2007 or 2014. Even in 2016, are you going to choose a brand-new ASP.NET Core? Microsoft announced .NET Core 1.0 at the Red Hat Summit in 2016 which isn't exactly an endorsement that the company thought it was the future of .NET. It seemed like Microsoft was trying to open up just enough to hook a company on .NET Core and then tell them "well actually, you should really upgrade to the real .NET Framework on Windows" when they ran into problems. That's not what happened, but Microsoft certainly hadn't committed to .NET Core in 2016. Their messaging was "well, Red Hat will offer support for this thing we made."
If I didn't have a Windows PC in 2015, I couldn't do .NET development (Mono aside). If I wanted to deploy to Linux in 2015, I couldn't do .NET development (Mono aside). The open source part matters to lots of people because .NET simply wasn't a choice for those who didn't want to be beholden to Windows and licensing until recently. People definitely ignored .NET because it simply wasn't an option for them.
My feeling was that Microsoft open sourced the .net framework to help Mono catchup a bit.
As for access to windows, to be honest I think that's pretty easy to have. Run on general purpose hardware, it's not that expensive.
I think that having access to a Mac is relatively harder than having access to a Windows machine.
When .net core came out I was under the impression that the product was the future of .net but maybe I was living in a bubble.
Anyway, I understand your point but I still think that the disinterest towards .net is tied to a generalized adversion to Microsoft (probably deserved) but not really related to the tech itself nor it's availability on Linux or Mac.
I find that owning the email address domain it is safe enough with any decent provider. If you get locked out just change the provider and dns configuration.
Even if you are storing passwords in Google account you should be able to reset all of them since you have access to the email.
That's a bit gratuitous