I don't think I read that one. I created a separate link-post for that one. Thanks.
When I joined some years ago, it automatically created a private, invite-only room named "Echo Chamber" with me being the single member. If it didn't happen to you automatically, you can create one yourself.
!books@programming.dev
Thanks for the explanation. If it works, don't fix it :)
I used Google Sites a long time ago and I'm a bit surprised it still exists (with Google killing products all the time). How is it with revision history, etc. Is it easy to download the contents in a reasonable format? One advantage of GitHub/GitLab is that you have all your archive in source control all the time.
Have you tried Github packages yet?
No. Thank you for the suggestion. We use Azure Devops, but I would expect it to have good integration with GitHub. But creating a public project in Azure Devops may make more sense (so that all packages are in one place).
[...] but what prevents you to use nuget.org?
The only thing is possible name collisions. I didn't start looking into this, but it is a possibility. Otherwise I think we will end up doing this.
No problem. In another comment I saw that you said you "[n]ever wrapped [your] head around dot net". If that's the case, I would suggest you looking into it (or something similar) before going into the more advanced (functional programming, C/C++/Rust) route. You can try to implement a backend in C# to one of your projects and see how .NET works (BTW you need to be looking at .NET Core, not the older .NET Framework stuff. Anything after .NET 5 is fine). Or you can try implementing a Lemmy/kbin clone. İn my experience, completing a project is critical to learning. Of course everybody learn in a different way, and you know you better than anyone else.
One last note: learning different languages is not really that important unless the language changes the way you think. Again, good luck :)
What microservices offers is loosely coupled services with very limited responsibilities and can be replaced easily and without any impact on a running service.
We only get this if we do microservices correctly. That's more or less the whole point of my comment. In many cases, teams rush into splitting their monolith into smaller chunks and call it a day. Without proper monitoring, orchestration/choreography, service boundaries, tooling, etc. microservices will drag a team into territories where they will lose control.
Unless you somehow believe that the same people writing both a monolith and microservices would opt to write spaghetti code [...]
No, I don't believe that. However, I also don't believe people who write spaghetti code will start writing better code just because now they are writing smaller components. If the team has good coding hygiene, they will produce good code whether it's monolith or microservices. But you have a point. If we are talking about components that are 200LoC, it's more difficult to produce spaghetti (or easier to recover from it). I'm not sure that's the norm, though.
As a final note: I'm not saying microservices are bad, or monolith is better than microservices. I'm just trying to introduce some nuance. I have been part of a microservices transformation and I think it was successful. But we met with many challenges along the way that were not immediately obvious from the beginning. To quote one of the pioneers of microservices architecture:
Don’t think of adopting microservices as flipping a switch; think about it as turning a dial. As you turn that dial, and have more services, you’ll hopefully have more opportunity to get the good stuff out of microservices. But as you turn up that dial, you’ll hit different pain points as you go. (Sam Newman, Monolith To Microservices)
If your move is a "check" move, you need to add "+" to it: Qe7+
I don't have any experience, but have been looking into this space as well. Currently we have MAUI, Uno Platform and Avalonia UI. It looks like Microsoft is putting all their weight behind MAUI and for that reason only, I would expect it to win in the long run.
I have the same problem on mobile Firefox on Android. I'm using the default frontend as well. This was not happening a week ago (or maybe 10 days). Started recently.