It appears that Go's superiority has attracted some controversy (in tranny circles)
>>106504586Even rust has more/better bindings for popular UI frameworks and toolkits.Why doesn't golang have bindings for Qt?
>>106504674>Why doesn't golang have bindings for Qt?Because Qt is written in C++ which makes it incompatible with any other compiled language. And also it uses some extra addons that are not C++ standard with their qmake/cmake programs, such aspublic slot: ...
public slot: ...
>>106504715bitch I'll fuk u up
>>106504715No execuses. Python, C#, Rust, whatever all have bindings for Qt.
>>106504814Those are all general purpose programming languages, while Go is a language and toolkit for making web backends.
Also, why do we need a second go thread with the exact same meme regurgitated by the OP?
>>106504586Did Go even get serious capture in the industry outside of Google, Tokyo, and the kubernetes/devops ecosystem?
>>106504586Tuple return values are wasteful. Tagged unions are superior. However, Zig's error handling is way better than both Go or Rust.
>>106504586Exceptions are superior.
>>106504946Nope. Pretty much the only thing keeping Go relevant still is docker and kubernetes
>>106504814C# and Rust do NOT have bindings for Qt
>>106504946SO survey of professional devs has Go ahead of Rust but about half as widespread as c# and Java
>>106504586Go definitely has some useful features, I’m using it for one of it’s biggest MIS-features, however.1. Inability to link, dynamic or otherwise, making binaries massive, duplicative, and immodular (in the literal sense). This is great on old systems that have old crypto.I was again annoyed by the go working use-case that all project code is in one small package main file that you compile and run.One .go file.The pre-module workaround is hilarious (install) and the module system is even worse.Do I have to copy every package into that one file and get rid of the package.references and choose unique names.
>>106505001Not good enough?https://github.com/qmlnet/qmlnet
>>106504586>Go's superiorityAbsolutely superior... at sucking
>>106505060QML is not Qt. Just look at the code, it is completely different from writing regular Qt
In Rust you can just define a new type and writeBoxResult<f64>or do the same for a non-boxed more specific error type.
BoxResult<f64>
>>106504715>>106504674there is qt without the moc you could write bindings for that no one wants to because qt fucking sucks. https://woboq.com/blog/verdigris-qt-without-moc.html
>>106504586Rust’s multi return looks a lot like C++’s. Shit.Also, it looks like rust largely copied C++ syntax on everything, then just fucked with the only good syntax that C++ had going for it.
>>106504586TRY FUCKING CATCH, faggot
>>106504586Go == Neutered C for lazy, unskilled people.
>>106505234>neuteredin what way
>>106505277it doesn't let you have out of bounds or memory errors so its bad
>>106504586Gojeets really are fishing for complements for reinventing checked exceptions except 1000% more verbose and 1000% more niggerlicious and ugly
>>106504674Nobody showed up when https://github.com/therecipe/qt stopped being updated
Real programmers code in assembly.
>>106505277Garbage collection slowing shit down.
>>106505434unless you are writing AAA game or drivers, no it is not slowing shit down
>>106505457What's an AAA game? Not gonna do another round of cloudflare captchas just for that.
>>106505485Road to vostok for example
>>106505531Kek, no idea either, but my bad. I can't search nothing right now, that's why I asked. Not being lazy.
>>106504996where is C++'s mascot, Keith?
>>106505554
>>106505982
>>106506056Alright, thanks. Realistic war simulator I guess.
>>106504586 > Absolute retard think it is somehow superior.Typical.
>>106504966>Zig's error handling is way better than both Go or RustI'm interested. Tell me more about it.
>>106504586Fuck off, jeet
