aqtinstall VS AspNetCoreDiagnosticScenarios

I've used aqt[1] before but it doesn't look like it's seeing 5.15.11 yet, just 5.15.2.

[1]: https://github.com/miurahr/aqtinstall

Don't use the Qt installer. It sucks. It's only reason is to annoy people and collect your data. Use aqt: https://github.com/miurahr/aqtinstall

I mostly disagree. Like you said, Qt is the best native GUI toolkit available today. And that is a hard achievement. There are many tradeoffs (some you pointed out) but the open source community seems to find a way around those limitations. There are thousands of open source libraries you can plug-in into your Qt app to overcome many of its limitations (although some remain, like how can't we still not easily change caret/cursor color of QTextEdit??).

Unlike you, I like the direction where Qt is taking. I think QML and Qt Quick are great. I just implemented a feature in my note-taking app that turns Markdown text into Kanban board using QML and the experience has been great (https://github.com/nuttyartist/notes/pull/574). I'm planning to continue transition from QWidgets to QML/Qt Quick.

I do worry of the continuous friction with open source development and hate the online installers as well. I can recommend this useful tool https://github.com/miurahr/aqtinstall that allows you to easily download prebuilt Qt binaries. I hope they can revert their approach on that.

Install the qt binaries from the command line https://github.com/miurahr/aqtinstall

https://github.com/miurahr/aqtinstall will help you with that.

you can install it from vcpkg or conan (or https://github.com/miurahr/aqtinstall if you really want the official Qt binaries) and it'll be much less

Is there any particular reason why you want to build Qt yourself? This is usually quite painful and requires a lot of extra stuff (see https://wiki.qt.io/Building\_Qt\_6\_from\_Git) . If you just want to avoid the (horrible) official installer and a Qt account, you can use aqtinstaller to fetch everything you need: https://github.com/miurahr/aqtinstall

Just recently, I had to recompile a (singleplayer) save game editor. So basically a GUI that does some clever hex editing.

It was written in C++ using Qt.

Have you ever tried compiling a Qt program on Windows? It involves signing up for an official Qt developer account to even install qmake.

To the point I had to use an unofficial Qt installer CLI app (aqtinstall) [0] to even install the toolchain to build this little shitty app... which still relied on having several Qt .dll files in the same directory as the .exe to work.

Have you clicked on [0] yet? Well, then guess what programming language aqtinstall uses.

[0] https://github.com/miurahr/aqtinstall

This one is a pretty decent guide - https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/blob/master/AsyncGuidance.md

The C# (mostly applicat community has e.g. https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/blob/master/AsyncGuidance.md written by one of the Asp.Net architects. I found this in this lovely thread https://news.ycombinator.com/item?id=36785691 which expresses my views/confusion more clearly than I can express.

No it doesn't, hence why there are best practices guidelines written by the .NET architects, and there was a research project to add Go/Java co-routines as well.

https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/b...

https://twitter.com/davidfowl/status/1532880744732758018?lan...

https://github.com/dotnet/runtimelab/issues/2057

https://github.com/dotnet/runtimelab/issues/2398

They don't work just fine in C#, there is a reason why one of ASP.NET architects has written a guide of best practices.

https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/b...

Many that praise async/await in C#, kind of forget it took about 10 years to spread across all the layer of the language and runtime, since it was done via IL rewriting, it caused several issues with F# async tasks, due to the age of the ecosystem plenty of code isn't async/await friendly and needs to be wrapped into Task.Run() or similar.

There is a best practices guideline from one of the ASP.NET architects, https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/b...

During last year they researched adding Go/Java's approach to .NET, but now it is too late. See the ASP.NET Q&A session at BUILD 2023.

The best guidance I have found was from here: AsyncGuidance.md

To expand upon this thought, here is the AsyncGuidance doc[1] on why not to use .Result to get the return value of a completed Task in C#.

To make this simple they introduced async Main[2] a few years ago.

[1]: https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/b...

Async Guidance