D3 - Programming in 3D

[angel]

On Friday, 12 June 2020 at 13:12:35 UTC, Chris wrote:
> How would you go about D3?
>
>     1. Which features would you keep?
>     2. Which features would you definitely get rid of?
>     3. What type(s) of memory management would you chose?
>     4. How would you design Phobos?
>     5. What restrictions would you impose? (see below)
>     6. How would you handle backwards compatibility?
>     7. How would you design the tooling?
>     8. How would you make it “industry friendly”? (see below)

3. Reference counted memory management. It is predictable.
5. I would design layered restrictions, kinda @most_restricted, 
@very_restricted, @slightly_restricted, @c_style
6. I would handle backward compatibility responsibly, but without 
fanaticism - occasionally one must cut through the live tissue.
7. I don't know how to design tooling, but it definitely won't 
fly without tooling.
8. Interoperability and good tooling are your entrance tickets to 
the industry.
---
I actually don't think D needs D3.
Designing a perfect language right from the start is possible 
probably only in theory, but in the real life evolution works 
better - you add missing features, you drop what doesn't belong, 
otherwise you risk to end where you start.