D Editions

Atila Neves atila.neves at gmail.com
Fri Jun 7 00:53:51 UTC 2024


On Thursday, 6 June 2024 at 04:21:23 UTC, Federico wrote:
> On Thursday, 30 May 2024 at 18:31:48 UTC, Atila Neves wrote:
>> https://github.com/atilaneves/DIPs/blob/editions/editions.md
>>
>> Destroy!
>
>
> I hope you will tolerate this unsolicited intrusion of mine,

There's a "Destroy!" right there, so I can't see how the 
"intrusion" would have been unsolicited. ;)

> Let me explain: the primary requirement for a programming 
> language is not its flexibility, power, ease of learning, etc. 
> No, the primary requirement is its stability and the certainty 
> that code written for a release will be compiled by all 
> compilers and libraries that support it.

I agree that should be a goal.

> And this is what makes D unusable (and indeed practically 
> unused).

What makes you think that? Especially since in a world where 
those things are true I wouldn't have my current job(s).

As soon as it is born, a fork of its system library...
> as soon as it starts to receive support from major IDEs, a fork 
> of the language. Now I see your willingness to make it 
> "dynamically scalable"... my friends, this way, you're going 
> nowhere.
>
> Let's talk about the initiative related to this thread: it 
> doesn't work.
> It's not acceptable that using the same language, I would write 
> code that wouldn't be compiled by the machine of the programmer 
> at the desk next to mine. This would be possible if I were 
> programming in C and he in D, but if we both work in Dv2, the 
> language standard must be the same for everyone.

I agree. What in the proposal makes you think that it wouldn't 
work?

> Of course, there can be a Dv3, Dv4... Dv2001, but someone has 
> to standardize each version and, once done, there must be a 
> freeze that prevents changes (except for debugging).

Those would be editions.

> From experience, I would find it very difficult to convince a 
> company to use code written in D.

I would also find it difficult to convince most companies to use 
Haskell or Clojure, but I'm not sure how that's relevant.




More information about the dip.ideas mailing list