D Profiles Idea

[aberba]

On Saturday, 20 July 2024 at 23:29:57 UTC, Mensikov wrote:
> I have an idea. Due to the abundance of D capabilities, I 
> propose to introduce the concept of D profiles to the 
> community. In D, you can write firmware for a microcontroller, 
> an OS, a web server, scripts, a vst plugin, and a compiler. All 
> these niches have different requirements from the programming 
> language. We already have a betterC mode, but what if we 
> introduce a more understandable gradation? Well-defined 
> subsets, let's say. We call these subsets profiles. With these 
> profiles you can better search for the required packages in 
> dub. Let's say I have a system profile, and it will be possible 
> to filter all packages by this request. A system profile may 
> have requirements not only for the absence of GC, but also for 
> the API in general, for example, to be closer to a low level. 
> Or I have a script profile, I can use both system and script 
> profiles. This will also allow language developers to see the 
> weaknesses of specific profiles and introduce features for 
> them. You can build std like a pyramid, with a system profile 
> at the bottom, and a managment profile based on it, for example.
>
> [...]

You're better off looking at D as a complete language and use it 
as is rather than a language that'll suddenly switch to some cool 
model. Versions of D isn't going to be significantly different. 
It just doesn't make sense. I don't see why current D can't do 
any of the above.

You can write every type of code in current D or use a custom 
runtime as mentioned above.