Worst ideas/features in programming languages?

russhy russhy at gmail.com
Sat Oct 16 05:37:40 UTC 2021

On Friday, 15 October 2021 at 21:55:55 UTC, SealabJaster wrote:
> On Friday, 15 October 2021 at 16:44:57 UTC, deadalnix wrote:
>> Then end result in practice is that almost everything uses the 
>> GC, and that @safe and @nogc are almost useless.
> Is there anything we can do to start addressing this, and the 
> other woes people have brought up?
> The answer is likely no, so I foresee these same things popping 
> up over and over and over again with no resolution since we 
> seem to have dug ourselves into a corner.

In the end, i think it doesn't really matter to be honest, as 
long as we make sure that additions to the STD doesn't make 
assumption about the memory allocation strategy, we'll be fine

The library authors will be free to use what ever is best for 
their libraries/program

STD will be here to assist them, rather than enforce them into 

One thing to mention is that entertainment is, more and more, and 
faster than ever, being consumed online, in dematerialized ways, 
that includes games and anything VR/AR/XR

There will be a massive need of software being built, games being 
created for various kind devices and for multiple experiences

WASM will be important, game engines/framework built for it will 
be needed

And those kind of libraries will avoid GC'd langauges to maximize 

Web stuff is a problem already solved, trying to chase it is a 
dead end

Our best bet i believe, is believe is to target those devs, for 
their engine needs, they need something that helps them be in 
control over the memory allocations

Let them use C#, Javascript, Lua etc as scripting language if 
they wish, but let them consume our libraries, they'll depend on 
D forever, they'll appreciate D, and maybe they'll also use D for 
their gameplay code instead of having to glue one

Making the STD empower that is i believe important

I think the best short term move that will help in the very long 
term is to finally finish ``STD.EXPERIMENTAL.ALLOCATORS`` and put 
it in ``STD.MEM``

It's a little bit bloated, it'll need a little lifting

What its author has to say?

More information about the Digitalmars-d mailing list