Pacco VS Flurl.Http

I've this project in mind to try it later which looks interesting and covering different topics https://github.com/devmentors/Pacco

With a friend of mine, we've implemented quite some time ago https://github.com/devmentors/Pacco and https://github.com/devmentors/Trill - extremely simple Twitter-like app with additional UI in Blazor https://github.com/devmentors/Trill.Web (similar structure to Pacco, all the infrastructure is running via Docker, and the services can be run locally, via Docker, PM2 or Tye

For Microservices examples, you can check your these guys: https://github.com/devmentors/Pacco

I feel like their packages could reduce the development time of a dotnet microservice by a lot. Here's one of their project showcasing what it can do: https://github.com/devmentors/Pacco

Flurl and others

Is Flurl.HTTP the same as https://flurl.dev/ I assume? (It doesn't mention a specific http package)

As far as your code goes, take a look at flurl (https://flurl.dev/). It is oh so much cleaner and more readable than the httpclient stuff.

I would also add flurl to that list https://flurl.dev/. It's an amazing library and can be super helpful for quick one off API calls.

Linqpad for me, it's my go to scratch pad when testing out either new tech or edge cases and POCs than firing up a new console project. Especially when wanting to try out new nuget packages and see how they work. Even for messing with external apis I use it with Flurl, especially for apis that don't have any proper documentation.

If you working with api use flurl You can also read source code on github.

Flurl: