On 05/09/2018 7:00 PM, Joakim wrote:
The D foundation is planning to add a way for us to pay for changes we'd
like to see in D and its ecosystem, rather than having to code
everything we need ourselves or find and hire a D dev to do it:
"[W]e’re going to add a page to the web site where we can define
targets, allow donations through Open Collective or PayPal, and track
donation progress. Each target will allow us to lay out exactly what the
donations are being used for, so potential donors can see in advance
where their money is going. We’ll be using the State of D Survey as a
guide to begin with, but we’ll always be open to suggestions, and we’ll
adapt to what works over what doesn’t as we go along."
https://dlang.org/blog/2018/07/13/funding-code-d/
I'm opening this thread to figure out what the community would like to
pay for specifically, so we know what to focus on initially, whether as
part of that funding initiative or elsewhere. I am not doing this in any
official capacity, just a community member who would like to hear what
people want.
Please answer these two questions if you're using or would like to use
D, I have supplied my own answers as an example:
I have $50USD to spend upon shared library support to be designed (not
just patching bugs) and implemented.Sadly that is my limit. I wish it
was more given how much of a blocker it can be (and has shown to be).
$25 - Enable GC for the DMD frontend, so that dmd/gdc/ldc use less memory
The only thing I believe required for this is [0]. This depends upon a
decision from Walter and should be pretty straight forward to do. But
the frontend will not be in any way ready to be used as a library.
During DConf I did attempt to get the frontend ready to be actually
usable. After my first PR sitting for like 3 months and is now looking
like its dead, I won't be the one handling that anymore.
[0] https://issues.dlang.org/show_bug.cgi?id=18811
