On Thursday, 11 September 2025 at 12:07:35 UTC, Serg Gini wrote:
On Wednesday, 10 September 2025 at 03:46:37 UTC, felixfxu wrote:
On Monday, 8 September 2025 at 20:10:52 UTC, Sergey wrote:
being focused on required important tasks = complicated
I don't quite understand the item above. What's dlang's
`"required important tasks"` now?
This one actually overlapping a lot with "volunteer based
development"
Some tasks need to be done, but they are boring and not-sexy.
Nobody want to deal with them.
So you can't ask volunteer to concentrate on tasks they don't
want to do.
Sometimes core devs are doing things they just like. And it is
ok from general point of view.
It is just not how "job" is working, right? You don't say to
your boss "nah.. I don't like this task - I'm not gonna do
this". But in volunteer based development - there is no "boss"
and there is no "job".
Another point that is going into this bucket is kinda lack of
understanding of what is "important". There is no plans (at
least clearly written and widely available).
Which is again partially based on underpower volunteer team
This is one of my bigger gripes about the way the DLF handles
things. What's the point of things like a borrow checker, fancy
DFAs for move semantics, or Phobos v3, if the language doesn't
even have a debugger for every platform that is able to properly
display its native types?
It's because nobody wants to spend their time peering over DWARF
info and then writing plugins for GDB, WinDBG and LLDB (or even
just one of them!). IMO, they should have a system where the
whole community gets to vote on one tooling/bug proposal every so
often, and then the DLF *has* to work on that alongside whatever
else they do.
