May 25, 2022

On Wednesday, 25 May 2022 at 14:14:28 UTC, Dukc wrote:

>

Aren't you worried that by using DPlug they discover D and use it to steal the market share that would have gone to Auburn Sounds if they had stayed with C++?

Companies that already exist will keep their codebase and not use D.

So it's only new entrants, it's more likely to take market share from C++ey shops.
Moreover, audio companies disappear because of internal disagreements, very rarely market conditions.

May 25, 2022

On Wednesday, 25 May 2022 at 13:57:30 UTC, Guillaume Piolat wrote:

>

So there is a "debt vs asset" position to account for, it is that the current community must be able to create net-positive

Maybe your company could take the role of a publisher? So if I create a novel effect it would go into one of your stacks with a certain percentage?

Then I don’t have to deal with marketing, windows etc and you would get a cut? Or is that unrealistic?

>

Now you must explain to users how to compete with you...

Yes... it would be better to cooperate and share marketing costs, some kind of umbrella brand? Or is it better to be small perhaps. I know nothing about this...

>

If Vibrant had sold more than 200 copies :) perhaps it could have a framework too. But it was a bitter commercial failure and couldn't justify the maintenance, so everything about it is retired.

I haven’t heard of Vibrant, but I guess it is typical in publishing to have a few products that makes up for all the others.

Seems to me that pooling would reduce the risk, but I guess cooperation online is a challenge...

If I knew how to make money off audio then I would give it a try by making weird effects for sure!!😁

>

Cost of making the by-product available in open-source is there, but you have unintended positive consequences too (more ecosystem, input, community, things happening).

Understand, seems like attracting knowledgable hobby-users early on is important so that support is not done by devs...

May 25, 2022

On Wednesday, 25 May 2022 at 17:27:58 UTC, Ola Fosheim Grøstad wrote:

>

Maybe your company could take the role of a publisher? So if I create a novel effect it would go into one of your stacks with a certain percentage?
Then I don’t have to deal with marketing, windows etc and you would get a cut? Or is that unrealistic?

Some actors of the industry have done that and it is very lucrative for them. A big subscription separated through allies. But then you have to grow a lot to make acquisition. It's a more important power imbalance than just relying on other's code though.
At the end of the day, noone will really do your marketing for you.

>

Yes... it would be better to cooperate and share marketing costs, some kind of umbrella brand? Or is it better to be small perhaps.

It's too early to tell.
What I'd like to push meanwhile is more sharing of (unmaintained) private UI code.

May 25, 2022
On 5/25/2022 4:55 AM, Dukc wrote:
> Unfortunately, you have a bug in your search query. You should also include bugs that have no resolution.

Why didn't you post the better link you used?
May 25, 2022

On Wednesday, 25 May 2022 at 20:13:46 UTC, Guillaume Piolat wrote:

>

At the end of the day, noone will really do your marketing for you.

Maybe with the ui scripting you could boil down one effect to a couple of files and have many effects by different authors in the same plugin. Then sell collections: 8xvocoders, 80s-reverbs, 20 analog guitar effects.

Anyway, the idea could be to view dplug as a gateway to a service. I guess the review would have to be by audio sample... to make it managable...

Anyway, something cooperative could make dplug interesting to more people.

May 25, 2022
On 5/24/2022 5:34 PM, Timon Gehr wrote:
> That encourages pseudo-fixes that focus on special cases.

Since I'm the one fixing the bugs, why would I be motivated to write pseudo-fixes?

But if I do, then file a new bugzilla with an example that actually illustrates the problem. It's not like we're going to run out of bugzilla numbers.

I also dislike reopening closed bugzillas by adding more problems to it. Just open a new one.

> I do submit bug reports to bugzilla.

Good!

> Well, sometimes the person who finds the bug is not great at making examples, then others provide better ones on the same bug report.

If it's a mess, close it and open a new one that is better.

> All of the bug reports were already in bugzilla

Good, but how would I know without links posted?

> I can get more proactive in filing enhancement requests again.

Good!
May 25, 2022
On 5/24/2022 5:18 PM, Timon Gehr wrote:
> On 25.05.22 01:47, Walter Bright wrote:
>>
>> I do enjoy and appreciate your contributions, too, even if it seems like I'm always arguing with you :-/
> 
> I guess this is as good an opportunity as any to also say that I highly appreciate the huge amount of work that you have invested into D. There's a lot that already works great.

Thanks, I like hearing that!
May 26, 2022

On Wednesday, 25 May 2022 at 21:54:02 UTC, Walter Bright wrote:

>

On 5/25/2022 4:55 AM, Dukc wrote:

>

Unfortunately, you have a bug in your search query. You should also include bugs that have no resolution.

Why didn't you post the better link you used?

Bugzilla is convoluted, what ever happened to switching to github? You wouldn't have this problem with github.

May 26, 2022

On Thursday, 26 May 2022 at 12:24:34 UTC, mee6 wrote:

>

Bugzilla is convoluted, what ever happened to switching to github? You wouldn't have this problem with github.

It’s happening. Robert Schadek is expected to be ready with the migration script next month. He’s doing a related talk at DConf.

https://dconf.org/2022/

May 26, 2022

On Thursday, 26 May 2022 at 13:04:43 UTC, Mike Parker wrote:

>

On Thursday, 26 May 2022 at 12:24:34 UTC, mee6 wrote:

>

Bugzilla is convoluted, what ever happened to switching to github? You wouldn't have this problem with github.

It’s happening. Robert Schadek is expected to be ready with the migration script next month. He’s doing a related talk at DConf.

https://dconf.org/2022/

So... what happened to Vlad's bugzilla harmony proposal? It's decided that we're moving to GitHub issues?