Why is D unpopular? (page 46)

On Friday, 6 May 2022 at 13:40:19 UTC, Adam D Ruppe wrote: > On Friday, 6 May 2022 at 13:25:00 UTC, Ola Fosheim Grøstad wrote: >> All these languages have good eco systems (or system libraries) for their application areas. To get a reasonable comparison you need to focus on one application area and look at what you would need to build a full featured application. > > D is ideal for all applications. Not in practice. > I know there's some belief out there that you can only possibly be good at one thing, but it isn't even true for insects, much less for divine delights like D. Not sure why you are looking down on insects, they're more important in an ecosystem than humans.

On Friday, 6 May 2022 at 14:30:27 UTC, mee6 wrote: > Not sure why you are looking down on insects, they're more important in an ecosystem than humans. which insect is causing an excinction event? Humans #1

On Friday, 6 May 2022 at 14:30:27 UTC, mee6 wrote: > Not in practice. Yes in practice. >> I know there's some belief out there that you can only possibly be good at one thing, but it isn't even true for insects, much less for divine delights like D. > > Not sure why you are looking down on insects, they're more important in an ecosystem than humans. I'm not looking down on insects. Quite the opposite - I'm defending their flexibility against common misconceptions over their hyper specialization.

May 06, 2022

Re: Why is D unpopular?

Posted by Ola Fosheim Grøstad
in reply to Guillaume Piolat

Permalink

Ola Fosheim Grøstad

Posted in reply to Guillaume Piolat

Permalink

On Friday, 6 May 2022 at 14:02:40 UTC, Guillaume Piolat wrote:

(first let's agree that I will not answer to your next message, so that our time is capped :))

Sure :)

That doesn't mean if you have a webservice to write, that Go is the "best tool for the job". D could be very well be the "best tool for the job".

D does not have cloud service support as I am aware of. Eco system matters. Running an on-demand Go service will be much cheaper and responsive (I am talking CPU time).

the products people use. (You will have noticed that Faust it can be implemented at CTFE in D even, so you can save writing a compiler and a backend, and get a D-man tattoo instead).

Making modifications real time and seeing the spectrum change as you type is fun and intuitive, you also get access to the standard library and can conduct experiments within seconds: https://faustlibraries.grame.fr/

It is great that D does everything you want for your use context, but it is not comparable in terms of features for that domain in general.

On Friday, 6 May 2022 at 16:15:23 UTC, Ola Fosheim Grøstad wrote: > The point was that you need to retain dedicated users over time in order to build an eco system. http://dpldocs.info/this-week-in-d/Blog.Posted_2022_05_02.html

On Friday, 6 May 2022 at 17:30:46 UTC, Adam D Ruppe wrote:

On Friday, 6 May 2022 at 16:15:23 UTC, Ola Fosheim Grøstad wrote:

The point was that you need to retain dedicated users over time in order to build an eco system.

http://dpldocs.info/this-week-in-d/Blog.Posted_2022_05_02.html

Well written article, but supporting @safe and @nogc is optional, so isn't that a self-imposed burden by authors? I'm inclined to believe that authors giving up on libraries have other causes, but I could be wrong.

Anyway, it is very difficult to grow the eco-system until you have retention, until then "gravity" won't happen. And without gravity you won't have enough maintainers of a library to sell stability…

It is great to see that Max has joined SDC, by browsing through the repo it looks like a lot of effort has gone into it! That is the kind of "gravity" that you need. If you have two highly active developers, you might get three and so on… Increasing belief in the long term viability of the project.

Forums