cross-posted from: https://lemmy.world/post/49193875
DConf2026 mostly has proAI talks, with the biggest standout being Adam Wilson’s talk about integrating LLMs into developing the next version of the standard library.
This lead to a lot of debate within the community, with even some pro-genAI people calling it out, and there’s even an open letter calling for rethinking the use of genAI, and some increased interest in the OpenD fork. It is also found out that people did try to volunteer for the new standard library (including me), but were rejected with the excuse of “we already have things in the works”.
I’m also interested into some D alternatives that’s not Rust (🤮🤮🤮🤮🤮 - no I’m not a Lunduke fan, but a gamedev, also no “const by default” languages!), has metaprogramming capabilities, and no (mandatory) header files (🤮🤮🤮🤮🤮), in case I decide to leave. I have a game engine that could be ported, its resource management needs to decoupled for D’s garbage collection though.
It definitely is capable of it now, if you put some effort into guiding it, and you’re working in a popular domain/language. It couldn’t really do it a year ago though so you might just be a bit out of date.
I experiment with it quite a bit just because that’s what all the employers want right now, and I never get good results. It’s not good at making “decisions,” and you don’t really know what decisions that will need to be made until you start coding. Or, you can meticulously plan and review everything, which can take longer than just writing the code (we already have pretty good precise languages to specify behavior). To be clear, I’m talking about all the small decisions like, “I’ve already wrote similar code to this, maybe I should refactor it out to a function,” “maybe I should use a hashset here instead of an list,” “I should probably use stable_sort here instead of sort,” “maybe this endpoint should accept PUT instead of POST,” etc.