Jump to page: 1 25  
Page
Thread overview
D Language Foundation Monthly Meeting Summary
May 28, 2021
Mike Parker
May 28, 2021
Mike Parker
May 28, 2021
Imperatorn
May 29, 2021
zjh
May 29, 2021
zjh
May 29, 2021
zjh
Jun 03, 2021
JN
Jun 03, 2021
zjh
Jun 03, 2021
zjh
Jun 04, 2021
zjh
Jun 04, 2021
IGotD-
Jun 04, 2021
sighoya
Jun 04, 2021
zjh
Jun 04, 2021
Imperatorn
Jun 04, 2021
drug
Jun 04, 2021
Imperatorn
Jun 04, 2021
IGotD-
Jun 04, 2021
sighoya
Jun 04, 2021
IGotD-
Jun 05, 2021
Paulo Pinto
Jun 10, 2021
sighoya
Jun 10, 2021
IGotD-
Jun 10, 2021
Paulo Pinto
Jun 07, 2021
Norm
Jun 08, 2021
Paulo Pinto
Jun 05, 2021
Imperatorn
Jun 05, 2021
Imperatorn
Jun 07, 2021
sai
Jun 07, 2021
IGotD-
Jun 04, 2021
bachmeier
Jun 03, 2021
IGotD-
Jun 02, 2021
Dukc
Jun 02, 2021
Mike Parker
Jun 04, 2021
Kagamin
May 28, 2021

We've just completed our monthly meeting for the month of May 2021. One decision we made is to start providing summaries of the topics discussed. Hence this forum post.

The participants: Walter, Atila, Andrei, Razvan, Max, and me.

Goals & Tasks

The primary topic on our agenda for this meeting was a goal-oriented task list. In place of the old vision documents, we want to start maintaining a list of our current major long-term goals and some more minor short-term goals, broken down into specific tasks. This serves both as the current vision and as a task list for community members looking to make an impact with their contributions. For example, Bugzilla issues that fall under a goal will be labeled as such, so contributors can more effectively focus their attention. The list will also be used to guide some of the work our new strike teams will be doing.

We've got a preliminary list of high-level goals that we will flesh out with specific tasks over the next couple of weeks. For example, major long-term goals are memory safety (e.g., specific bugs, fully enabling DIP 1000 support) and Phobos v2. There were other goals discussed, such as implementing named arguments, improving compile-time introspection, improving Phobos @safety, and more. I don't know yet what the initial version of the final list will look like, but I hope to publish it in the next two or three weeks.

Error Messages

We discussed how to improve error messages. Walter exhorts everyone to please raise a Bugzilla issue for specific error messages you encounter that you think need improvement. Walter also said he is open to accepting the implementation of a command-line switch that enables URLs in error messages to provide more information.

Next Meeting

Our next monthly meeting will take place on June 25th. We haven't yet set the agenda, but a portion of it will be devoted to following up on some of the topics discussed in today's meeting.

May 28, 2021

On Friday, 28 May 2021 at 14:56:08 UTC, Mike Parker wrote:

>

We've just completed our monthly meeting for the month of May 2021. One decision we made is to start providing summaries of the topics discussed. Hence this forum post.

The participants: Walter, Atila, Andrei, Razvan, Max, and me.

And Ali!

May 28, 2021

On Friday, 28 May 2021 at 14:56:08 UTC, Mike Parker wrote:

>

We've just completed our monthly meeting for the month of May 2021. One decision we made is to start providing summaries of the topics discussed. Hence this forum post.

[...]

Splendid! Communication is king

May 29, 2021

On Friday, 28 May 2021 at 14:56:08 UTC, Mike Parker wrote:

>

We've ...
Good,maybe we can raise our sounding slogan "Better C++" again!

May 29, 2021

On Saturday, 29 May 2021 at 00:26:54 UTC, zjh wrote:

>

Good,maybe we can raise our sounding slogan "Better C++" again!

There are too many talents in C++
We must attract them.
Only them can make d great!Because they are library writer. They can make d great.

May 29, 2021

On Saturday, 29 May 2021 at 00:30:38 UTC, zjh wrote:

> >

Good,maybe we can raise our sounding slogan "Better C++" again!

If I'm a marketer of rust, I'll say rust is abnormal C++.would you like a try?
If I were a marketing person of D, I would say d is a Better c++.will you try?
We can make use of the C++ fame to make us famous.
C++ is always our good friend.

June 02, 2021

On Friday, 28 May 2021 at 14:56:08 UTC, Mike Parker wrote:

>

For example, major long-term goals are memory safety (e.g., specific bugs, fully enabling DIP 1000 support) and Phobos v2.

Phobos v2 is an official plan? That was news for me! Any chance to get a glimpse of what's planned for it?

June 02, 2021

On Wednesday, 2 June 2021 at 11:10:36 UTC, Dukc wrote:

>

Phobos v2 is an official plan? That was news for me! Any chance to get a glimpse of what's planned for it?

The overall goal is that it doesn't replace the current Phobos, but sits alongside it. Changed/improved/new functionality goes in the std.v2 namespace (or whatever it looks like in the end) and you can import that alongside existing std packages.

Andrei has talked about it a little here in the forums, and Steve did some preliminary work a while back. Beyond that, I have no details about plans. We'll have more after the workgroup gets going.

June 03, 2021

On Saturday, 29 May 2021 at 00:30:38 UTC, zjh wrote:

>

On Saturday, 29 May 2021 at 00:26:54 UTC, zjh wrote:

>

Good,maybe we can raise our sounding slogan "Better C++" again!

There are too many talents in C++
We must attract them.
Only them can make d great!Because they are library writer. They can make d great.

I disagree. Attracting C++ folks doesn't seem to work. You may try to lure them with promises of nicer templates and no header files, but after a while they will complain about the garbage collector and go back to their new C++ draft standard.

If you advertise yourself as Better C++, you are instantly setting yourself up for comparison and are turning away everyone who dislikes C++ in the first place.

Rust doesn't advertise itself as "Safe C++", Go doesn't advertise itself as "Native Java", Zig doesn't advertise itself as "Better C".

June 03, 2021

On Thursday, 3 June 2021 at 22:40:50 UTC, JN wrote:

>

On Saturday, 29 May 2021 at 00:30:38 UTC, zjh wrote:

>

On Saturday, 29 May 2021 at 00:26:54 UTC, zjh wrote:
OK, how do you position "d"?
What kind of programmers do you want to attract? beginner?pythoner?scripter?
How to attract them and why and what feature attact them?
What slogan of "d", Can d occupy a bigger market?
Does d still occupy the field of system programming

The GC of D is a burden.in the speaking of AA.
D does not owns the advantages of GC , but all the disadvantages of GC .Why not discard it?

« First   ‹ Prev
1 2 3 4 5