What changes to D would you like to pay for?

Dejan Lekic dejan.lekic at gmail.com
Fri Sep 7 09:41:08 UTC 2018


On Wednesday, 5 September 2018 at 07:00:49 UTC, 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:

I would donate again to DFoundation towards the administration 
and proper handling of the development process. Let me clarify - 
I expect D Foundation to oversee the D development process in the 
same fashion the JCP (Java Community Process) works. - That is an 
example of how professionals handle these things.

The D Foundation should, in my humble opinion, start the design 
(and perhaps the development) of commonly used APIs that may or 
may not be part of Phobos (APIs yes, the implementation should be 
separate library).

The following APIs come first to my mind:
- Crypto API
- Networking API (supporting all major protocols, and giving nice 
set of interfaces to implement own - look at protocol handlers in 
Java, or similar)
- Graphics (2D and 3D)
- GUI API (a rock-solid, scene based like JavaFX)
- Database API
- TUI (console UI)
- Security API (Role-base Access, etc)
- VFS API (Look at Apache Commons VFS)

Again Phobos should only contain interfaces - refecence 
implementation should be in the libphobos-<api> (example: 
libphobos-crypto.so)

The design and the development (or coordinating the development) 
of these APIs should be the D Foundation responsibility. Also 
future improvements should be part of the the improvement process 
that is also governed by the D Foundation (look at Python PEPs)...

I talked about this on IRC many times with other D programmers. 
Rich set of APIs is why languages like Java, Python, JavaScript, 
Go, etc gained so much popularity.

The more I see the D Foundation do these things, the more I will 
be willing to donate.


More information about the Digitalmars-d mailing list