On Tuesday, 1 June 2021 at 03:18:22 UTC, someone wrote:

But have you actually investigated it? It's being actively maintained.

https://github.com/d-widget-toolkit/dwt

On Tuesday, 1 June 2021 at 03:32:50 UTC, someone wrote:

Yeah, "fragmentation" is a problem. We do a lot of things 90%. We need more "100% projects" that are just plug n play rather than plug n pray

On Tuesday, 1 June 2021 at 05:27:41 UTC, Imperatorn wrote:

The solution is to reduce the scope of projects, but that requires design and planning. Hobby projects tend to be experiments that evolve over time.

On Tuesday, 1 June 2021 at 06:31:28 UTC, Ola Fosheim Grostad wrote:

Would like to pay for something that's not exists where there is already like 10 "good enough"(tm) alternatives? How much people actually use D and willing to pay for that?
That's the chicken-egg problem - no funding because no decent solutions, no decent solutions because such enormous effort requires compensation.

Another issue is that these hobby projects are not state of the art solutions, they stuck in early 90's (ok, maybe late 90's), where the rest of the world using different architectures and approaches that was evolved several times from then.
And yet people who asks for UI libraries goes like "nah, no fancy schmancy CSS, and no markup. gimme good ol' programmatical approach" or "bloat bloat bloat, no thanks"

On Tuesday, 1 June 2021 at 10:11:25 UTC, evilrat wrote:

Yes, I agree. I think Flutter forced Apple's hand, so they made SwiftUI? It is tempting to think that UI-specification is a mature field, but apparently not. It is still evolving.

I think the best approach is to create an UI for a specific application and then later turn it into a library. Then one at least have experience and can sort out weak spots before handing it to others.

Maybe if DPlug had more users something interesting would emerge? DPlug is the only framework I find interesting with D right now.

Right,I prefer 1100% over 390%.

On Tuesday, 1 June 2021 at 03:16:05 UTC, someone wrote:

I think it uses Metal, OpenGL ES, translation layer to OpenGL and Direct X, backend for Vulkan (but Vulkan hardware drivers apparently tend to be buggy). Also a build for webassembly.

It is the graphics engine for Chrome and Firefox, so it is probably the best bet if you want cross platform support.

See release notes for progression:

https://skia.org/docs/user/release/release_notes/

On Tuesday, 1 June 2021 at 05:26:47 UTC, Mike Parker wrote:

Yeah, DWT is solidly OK. I'd pick it over gtkd if you wanted to target Windows since it doesn't use gtk there.

On Tuesday, 1 June 2021 at 03:36:00 UTC, someone wrote:

Have you ever used github before?

That's how it works. You "fork" something, do a small change, then open a pull request back to the original. Then your "fork" gets abandoned until next time you want to do a PR.

This is perfectly normal on that site. Number of forks is actually correlated with number of contributors, not abandonment.

On Tuesday, 1 June 2021 at 05:26:47 UTC, Mike Parker wrote:

Being advised not to use it is not the same as saying won't use it; however I consider it a red flag, or to say it in other words, something that I have to pay even more attention to before start using it in order to not shoot me on the foot. I am researching the whole subject of GUI toolkits and right now I have no less than 10 toolkits to go so, even downloading, installing, configuring, reading some basic documentation, and making something stupid like a hello world app for each one will take some time, this is no surprise. Up to this point I didn't discard anything since I am aware I still have no deep insights/basis to. Give me some time please, but anything that comes to mind keep telling me, it helps a lot, thanks :) !