On Sunday, 15 May 2022 at 01:51:23 UTC, Walter Bright wrote:
> On 5/14/2022 6:44 PM, forkit wrote:
>> There is no actual market for ImportC, in the 'real' world.
>
>
> People are already using it.

Sure. This might make sense, if the team involved in the project are all very well versed in both languages (and whatever other languages may also be used in the project). And, if they can confidently obtain and use the tools and people they need to make the project succeed, and maintain it over time.

But some of the biggest software security concerns (that still exist to this day), are a result of C.

Modern programming languages should be encouraging a move away from C (and providing the means to do so), and not encouraging a move towards C.

My real concern though (and in relation to the topic of this thread), is that ImportC will actually make D even less popular.

Who has the time to be (continually) well-versed in both D and C?

On Sunday, 15 May 2022 at 02:30:52 UTC, forkit wrote:

> Who has the time to be (continually) well-versed in both D and C?

That's kind of the point. With ImportC, you don't *have* to be well-versed in C if you need to use a C library.

On Sunday, 15 May 2022 at 02:38:12 UTC, Mike Parker wrote:
> On Sunday, 15 May 2022 at 02:30:52 UTC, forkit wrote:
>
>> Who has the time to be (continually) well-versed in both D and C?
>
> That's kind of the point. With ImportC, you don't *have* to be well-versed in C if you need to use a C library.

Integrating a library whose code you're not well versed in, seems like a recipe for disaster.

I'm now thinking of the 2 x fighter planes (C and D) flying together in one of Walter's videos.

Are the planes (let alone the pilots) going to make it back to base, or not?

On Sunday, 15 May 2022 at 03:02:24 UTC, forkit wrote:
> On Sunday, 15 May 2022 at 02:38:12 UTC, Mike Parker wrote:
>> On Sunday, 15 May 2022 at 02:30:52 UTC, forkit wrote:
>>
>>> Who has the time to be (continually) well-versed in both D and C?
>>
>> That's kind of the point. With ImportC, you don't *have* to be well-versed in C if you need to use a C library.
>
> Integrating a library whose code you're not well versed in, seems like a recipe for disaster.
>
> I'm now thinking of the 2 x fighter planes (C and D) flying together in one of Walter's videos.
>
> Are the planes (let alone the pilots) going to make it back to base, or not?

It may be a recipe for disaster sometimes but most of the time it's how programmers actually make software...

If you want to make a game you don't need to know how to implement a graphics driver.

On Sunday, 15 May 2022 at 03:02:24 UTC, forkit wrote:
> 

Also, the time for emulating the C++ experience of interfacing to C, has long gone.

The advantage C++ had (soooooo..long...ago....for doing this), was that C programmers would be more likely to move towards using C++. That is what made C++ popular after all.

But that was a long......time.........ago....

C programmers have had enough time to move to a newer language.

If they still program in C, I don't see them moving to D anytime soon.

Nor do I see D programmers moving (back) to C.

So I fail to see the benefit in having D and C flying around together...

On Sunday, 15 May 2022 at 03:07:31 UTC, max haughton wrote:
> ...
> If you want to make a game you don't need to know how to implement a graphics driver.

sure. but someone will likely take advantage of that C code used in that graphics driver on your device.. and they'll take control of your device (cause nobody on the dev team understood what that C code was actually doing - since they were all D programmers).

On Sunday, 15 May 2022 at 03:02:24 UTC, forkit wrote:

>
> Integrating a library whose code you're not well versed in, seems like a recipe for disaster.
>

Then how do you ever use any libraries?