June 26, 2017
Am 26.06.2017 um 10:41 schrieb Wulfklaue:
> On Monday, 26 June 2017 at 08:29:54 UTC, Sönke Ludwig wrote:
>> Am 26.06.2017 um 09:19 schrieb Wulfklaue:
>> Can you post the error message? I didn't use the Linux sub system.
>
> From what i remember on my home system, the issue was it tried to store
> the file in Windows temporary directory.
>
> Just tried it on my my work PC ( with visual studio code portable ) and
> got a slightly different error:
>
>> C:\Users\xxx\AppData\Local\Temp\VSCodePortableTemp\.dub\build\vibe-d:utils-0.7.31:
>> The directory name is invalid.
>
> I assume the error is similar to the one i had in the weekend because
> its trying to use the temp folder again. Just different temp path
> because of the portable editor ;). Note: At home its a full VSC
> installation, not this portable version.

Okay, thanks, that explains it. I didn't realize that I'm using DUB master instead of the latest release, and this issue is already fixed there. A workaround is to use "dub --single webserver.d" instead (performs the build normally instead of building in the temp folder).
June 26, 2017
On Monday, 26 June 2017 at 08:47:46 UTC, Ecstatic Coder wrote:
> Thanks for having taken the time to write this very enlighting post.
>
> I think this is a very pragmatic analysis of the main roots of the problem, which clearly explains why D remains much less popular than Go, Python, Kotlin, etc despite the language itself is at least as modern and convenient (and even more IMHO).
>
> I don't think the situation will change any time soon, so I feel exactly in the same mood as you.
>
> Hence my suggession to simply make a few "cosmetic" changes to change D's perception on the web, to compensate for the lack of money and manpower.
>
> But they won't probably be applied.
>
> And I know that for the "do it yourself" I'm probably part of the problem...

I understand the frustration, brilliant language but not so well designed ecosystem around.
Please be aware, that even the setup of the D Foundation is still work in progress. So we are still waiting for the foundation to offer some kind of supporting memberships.

But as Andrei A. told us on DConf, the foundation already is paying some students (a small salary) for their work. So best thing we can do is to push the D Foundation (Andrei+Walter) to optimize the support structure.

The good thing behind these obvious missing parts is, that there is a strong focus on the language itself, so I am convinced, that D is here to stay, so that every effort in learning the language is a well made investment.

Regards mt. (still a bloody beginner, started with D Nov. 2015)
June 26, 2017
On Monday, 26 June 2017 at 09:26:01 UTC, Martin Tschierschke wrote:
> But as Andrei A. told us on DConf, the foundation already is paying some students (a small salary) for their work. So best thing we can do is to push the D Foundation (Andrei+Walter) to optimize the support structure.

A bit off-topic but what is going on with the students? I remember there are 3 students hired and one of them was at the D conference a while ago, talking about optimizing the D runtime. But has anybody read anything what is going on beyond this? Or even is there any progress?

Communications. Another point to add to the complained list *lol*.

At my work here, we have weekly status updates where the project leader writes down:

* x person is working on y.
* x task has been finished.
* y is proposed.

It saves on a lot of time because we do not need to repeat what we are working on to each boss / college.

Sometimes i think that Walter and Andrei are probably also tired of explaining the same thing over and over again. The issue being that a forum simply eats information and unless you read each and every thread, you will always miss (potentially) important or interesting information.
June 26, 2017
On Monday, 26 June 2017 at 08:54:23 UTC, Sönke Ludwig wrote:
> Okay, thanks, that explains it. I didn't realize that I'm using DUB master instead of the latest release, and this issue is already fixed there. A workaround is to use "dub --single webserver.d" instead (performs the build normally instead of building in the temp folder).

Indeed, that works a lot better :)
June 26, 2017
On Monday, 26 June 2017 at 09:45:46 UTC, Wulfklaue wrote:
> Communications. Another point to add to the complained list *lol*.
>
> At my work here, we have weekly status updates where the project leader writes down:
>
> * x person is working on y.
> * x task has been finished.
> * y is proposed.
>
> It saves on a lot of time because we do not need to repeat what we are working on to each boss / college.
>
> Sometimes i think that Walter and Andrei are probably also tired of explaining the same thing over and over again. The issue being that a forum simply eats information and unless you read each and every thread, you will always miss (potentially) important or interesting information.

Interesting that you bring that up. A couple of years ago we had a discussion about the need to improve communication. We said D needed a blog to better communicate what is going on. Now we have one, and by my count, the number of posts from Walter and Andrei are zero.

That's okay, because the language itself is not the problem. Almost all problems with the language can be fixed by others. Walter and Andrei don't have much to do with editor support, for instance, and I doubt that they are familiar with the IDE world even if they did want to get involved.

Anyone can start a group to work on something. If you want to put together a group to improve the IDE situation, come up with a plan (we need x, y, and z and here's how we'll do it), make an announcement on the forum, and run with it. No need to ask for permission, because there's nobody to ask for permission.
June 26, 2017
On Monday, 26 June 2017 at 10:13:13 UTC, bachmeier wrote:

> Now we have one, and by my count, the number of posts from Walter and Andrei are zero.

Actually, they have one each: Walter's "Snowflake Strings" [1] and Andrei's "Introspection, Introspection Everywhere" [2]

There are more in the pipeline, so we'll hear from them again a little ways down the road.

https://dlang.org/blog/2017/02/22/snowflake-strings/
https://dlang.org/blog/2017/05/22/introspection-introspection-everywhere/


June 26, 2017
On Monday, 26 June 2017 at 10:13:13 UTC, bachmeier wrote:
> Anyone can start a group to work on something. If you want to put together a group to improve the IDE situation, come up with a plan (we need x, y, and z and here's how we'll do it), make an announcement on the forum, and run with it. No need to ask for permission, because there's nobody to ask for permission.

I think you hit the nail on that head with that one. There is nobody to ask permission but the other side of the shoe is also, there is nobody to push for it.

We can talk about it for ages but very few people have the time to pick up projects beyond our own. It helps when you are writing a project and you need a feature/library that D does not have. And in the end you public that feature/library. And the feature/library get maintained as long as that project is relevant to your needs.

This is something that is noticeable in D especially, a lot of projects are a result from people needing something, they write it. But the moment they do not need it anymore? There is in a lot of cases nobody to take over the project for various reasons.

D feels at times too much incomplete. And the above mentioned point is one of them.

There is no real leadership to push for features. It seems to me, that Walter and Andrei live in there happy little world, writing new features into D that they want / find interesting. Nothing wrong with that. But they are somewhat the official leaders of D...

Maybe its better if D gets a community leader / director / communication expert or whatever the titles, who's job is not pure development ( some knowledge is always a plus ) but to focus the resources ( by acquiring talent, money, publicity, ... ) in actually enhancing D its eco system.

All the talk before technically comes down to this. Its not about simply electing yourself to write a library/feature that D is missing and that is. That does not work because it temporary solves one issue but not the global. Anyway, off lunch, back to the salt mines.
June 26, 2017
On Monday, 26 June 2017 at 11:10:42 UTC, Wulfklaue wrote:
> On Monday, 26 June 2017 at 10:13:13 UTC, bachmeier wrote:
>> Anyone can start a group to work on something. If you want to put together a group to improve the IDE situation, come up with a plan (we need x, y, and z and here's how we'll do it), make an announcement on the forum, and run with it. No need to ask for permission, because there's nobody to ask for permission.
>
> I think you hit the nail on that head with that one. There is nobody to ask permission but the other side of the shoe is also, there is nobody to push for it.
>
> We can talk about it for ages but very few people have the time to pick up projects beyond our own. It helps when you are writing a project and you need a feature/library that D does not have. And in the end you public that feature/library. And the feature/library get maintained as long as that project is relevant to your needs.
>
> This is something that is noticeable in D especially, a lot of projects are a result from people needing something, they write it. But the moment they do not need it anymore? There is in a lot of cases nobody to take over the project for various reasons.
>
> D feels at times too much incomplete. And the above mentioned point is one of them.
>
> There is no real leadership to push for features. It seems to me, that Walter and Andrei live in there happy little world, writing new features into D that they want / find interesting. Nothing wrong with that. But they are somewhat the official leaders of D...
>
> Maybe its better if D gets a community leader / director / communication expert or whatever the titles, who's job is not pure development ( some knowledge is always a plus ) but to focus the resources ( by acquiring talent, money, publicity, ... ) in actually enhancing D its eco system.
>
> All the talk before technically comes down to this. Its not about simply electing yourself to write a library/feature that D is missing and that is. That does not work because it temporary solves one issue but not the global. Anyway, off lunch, back to the salt mines.

+1
June 26, 2017
On Monday, 26 June 2017 at 11:09:47 UTC, Mike Parker wrote:
> On Monday, 26 June 2017 at 10:13:13 UTC, bachmeier wrote:
>
>> Now we have one, and by my count, the number of posts from Walter and Andrei are zero.
>
> Actually, they have one each: Walter's "Snowflake Strings" [1] and Andrei's "Introspection, Introspection Everywhere" [2]
>
> There are more in the pipeline, so we'll hear from them again a little ways down the road.
>
> https://dlang.org/blog/2017/02/22/snowflake-strings/
> https://dlang.org/blog/2017/05/22/introspection-introspection-everywhere/

Sorry, I was a bit sloppy. I meant posts from the perspective of leaders saying "this is the plan going forward". These are more of what I would consider technical posts rather than big picture plans for the future posts.
June 26, 2017
On Monday, 26 June 2017 at 11:10:42 UTC, Wulfklaue wrote:

> There is no real leadership to push for features. It seems to me, that Walter and Andrei live in there happy little world, writing new features into D that they want / find interesting. Nothing wrong with that. But they are somewhat the official leaders of D...

At the same time, this is the case for many languages. The leadership worries about the language and leaves IDE support and such to the community. It's not different from what I've seen over the years for Clojure, Python, Haskell, OCaml, Scala, Ruby, R, and probably others.