

Just in case there is somebody who is using Clear.Dental in production, I want to let everyone know I am making a number of major changes in the next few months (see attached image)
These will be major changes that will help bring Clear.Dental to the mass market. Now that Clear.Dental is the only Open Source EHR/PMS, getting people to switch has never been more important.
Just in case there is somebody who is using Clear.Dental in production, I want to let everyone know I am making a number of major changes in the next few months (see attached image)
These will be major changes that will help bring Clear.Dental to the mass market. Now that Clear.Dental is the only Open Source EHR/PMS, getting people to switch has never been more important.
I wanted to marvel at the bot madness but
GitHub kept timing out while transferring 4MB
and browser kept choking on processing 14MB of resources
all spread out over 222 requests
for an issue thread with what about 25 text comments plus about the same number of logged repo actions?
Lord, but GitHub has so many problems.
#QT @ShadowJonathan via @rysiek
https://tech.lgbt/@ShadowJonathan/115050687403295425
I wanted to marvel at the bot madness but
GitHub kept timing out while transferring 4MB
and browser kept choking on processing 14MB of resources
all spread out over 222 requests
for an issue thread with what about 25 text comments plus about the same number of logged repo actions?
Lord, but GitHub has so many problems.
#QT @ShadowJonathan via @rysiek
https://tech.lgbt/@ShadowJonathan/115050687403295425
I think there is a Dunning–Kruger like effect whereby the complexity of rewriting an open source project from scratch is vastly underestimated the less you know about the scope of the work.
You could make 80% of #inkscape in a couple of months of javascripting. But this is 80% of Inkscape's surface. Not actual depth.
Rewrite it all in #Qt? #React? #JS? #Rust? These are ideas aren't bad. But they are vast projects that would cost millions of dollars.
Related to: https://mastodon.uno/@maxdid/114691504835360868
Qt’s New Bridging Technology - Looking Back to Move Forward https://www.qt.io/blog/about-the-new-qt-bridging-technology
«With the new bridging technology, Qt aims to provide not only a set of initial integrations for five pre-selected languages: C#, Kotlin/Java, Python, Rust, and Swift, but also to open and document a few private QML APIs to allow anyone to build additional language integrations in the future».
I think there is a Dunning–Kruger like effect whereby the complexity of rewriting an open source project from scratch is vastly underestimated the less you know about the scope of the work.
You could make 80% of #inkscape in a couple of months of javascripting. But this is 80% of Inkscape's surface. Not actual depth.
Rewrite it all in #Qt? #React? #JS? #Rust? These are ideas aren't bad. But they are vast projects that would cost millions of dollars.
Related to: https://mastodon.uno/@maxdid/114691504835360868
Qt’s New Bridging Technology - Looking Back to Move Forward https://www.qt.io/blog/about-the-new-qt-bridging-technology
«With the new bridging technology, Qt aims to provide not only a set of initial integrations for five pre-selected languages: C#, Kotlin/Java, Python, Rust, and Swift, but also to open and document a few private QML APIs to allow anyone to build additional language integrations in the future».
A space for Bonfire maintainers and contributors to communicate