912 karma · joined November 1, 2011
Searching through the repo [0,1] it seems like you still need to write a certain amount of C++ especially if you're using QtWidgets instead of QML. So in my eyes this seems like a way to incorporate Rust code into a Qt project rather than build a Qt interface for use in Rust, as the end program is essentially a C++ program with some Rust bits.
From what I understand if you have a fair amount of existing Rust code to reuse in a Qt GUI application this is probably the best way to get them to talk together but it's a still a bit far from "Qt GUI for your Rust programs". I get that the distinction between the two is a bit blurry but in any case you still need to write a considerable amount of C++ especially if you opt for the QtWidgets way.
Of course it is entirely possible that I've completely missed the point so in that case please correct me.
[0] https://github.com/KDE/rust-qt-binding-generator/tree/master...
[1] https://github.com/KDE/rust-qt-binding-generator/tree/master...
In the meantime I have residential IPv6 since 2011. I really believe corporate networks are one of the main causes of delay in massive IPv6 adoption. And given the inertia I'm not really expecting them to change soon.
However Open Access is not panacea. Most of the times it just moves the cost from the subscriber to the author. The open access costs are equally extortionate for several journals in the ballpark of £2000 for a single article. As a result publicly funded grants must also include a quite significant budget for publishing costs further inflating the already bloated administrative overhead of research programmes. So you either pay the journals to open up your article or pay for a subscription. It does increase visibility and accessibility of research but, still, we are not quite there yet.
Although I partially agree; it's not only the price that affects the consumption of tobacco. It's could also be that there is nothing cool about smoking nowadays.
But unless they move Thunderbird to WebExtensions (which would be a total productivity disaster) it can always be modded.
Although an UI update is always welcome there are more important issues to address in Thunderbird, like better calendar synchronisation and an overhaul to its search capabilities.
And it's not only wired. I've come across a lot of internal sites and intranets that are poorly tested on anything but Chrome. I know, it's not exactly the same thing as the old IE/ActiveX but it still grinds my gears when it happens.
[0] https://arstechnica.com/tech-policy/2016/12/california-man-s...
[0] https://www.cups.org/AppleContributorAgreement_2011-03-10.pd...