On Tuesday, 11 April 2017 at 14:36:18 UTC, Ali Çehreli wrote:
> On 04/11/2017 02:35 AM, Joseph Rushton Wakeling wrote:
>> will we see you at DConf? :-)
>
> Yes. I'm looking forward to it. :)

Great!  And, likewise :-)

On Tuesday, 11 April 2017 at 06:08:16 UTC, Ali Çehreli wrote:
> I will be presenting D as a time-saving tool at C++Now:
>
>   http://cppnow.org/
>
> I have to say it took me a very long time to come up with the title and the abstract. How could I sell D to C++ experts? Luckily, I asked Manu and among a long list of ideas he said "it's about saving time" and "time is money". How can you argue with that? ;)
>
> Do you agree or disagree that D brings competitive advantage? Please let me know.
>
> Are you attending the conference?
>
> Ali

Coming from C++, I think you can talk about compilation times first and the easiness of making a new program with dub (even with dependencies).

Because imho library integration and waiting for the compiler are the biggest pain points with C++, actually I'm not sure memory safety will make trench workers switch. Newer C++ almost erased leaks and memory errors if you follow it.

On 04/11/2017 02:22 AM, qznc wrote:
> On Tuesday, 11 April 2017 at 06:08:16 UTC, Ali Çehreli wrote:
>> I will be presenting D as a time-saving tool at C++Now:
>>
>>   http://cppnow.org/
>
> Looks like C++Now has two keynotes. One keynote on D and one keynote on
> Rust. Maybe they should change their name. ;)
>

I *think* the third one will be related to Haskell but don't quote me on that. I applaud the organizers for inviting other languages. Their keynote theme for this year is "What can C++ learn from other languages?"

Ali

On Tuesday, 11 April 2017 at 09:30:28 UTC, Jacob Carlborg wrote:
> On 2017-04-11 08:50, FreeSlave wrote:
>
>> D can't compete with C++ until it gets proper dynamic library support on
>> all platforms. As far as I understand there're still problems on Windows.
>
> And no official support on macOS.

And no output for ARM64. :/

Arek

On Tuesday, 11 April 2017 at 09:30:28 UTC, Jacob Carlborg wrote:
> And no official support on macOS.

LDC officially supports shared libraries on macOS. -David

On Saturday, 22 April 2017 at 10:12:04 UTC, Arek wrote:
> And no output for ARM64. :/

LDC has beta-quality support for AArch64. --David

On 4/11/2017 8:10 AM, Guillaume Piolat wrote:
> Newer C++ almost erased leaks and memory errors if you follow it.

C and C++ don't have memory leaks if you are careful. The trouble is, there's no checking.

On Sunday, 23 April 2017 at 10:16:14 UTC, Walter Bright wrote:
> On 4/11/2017 8:10 AM, Guillaume Piolat wrote:
>> Newer C++ almost erased leaks and memory errors if you follow it.
>
> C and C++ don't have memory leaks if you are careful. The trouble is, there's no checking.

The rules of leak-free, exception-safe C++11 aren't so hard.
- single-owneship for everything, invent fake owner if needed
- std::unique_ptr for owning pointer, raw pointers for borrowed
  (unique_ptr neatly avoids to write a RAII wrapper for everything)

When teams internalize these rules, no more leaks, no more double-free, etc.
Hence Rust that sanctified this style.

On Sunday, 23 April 2017 at 12:04:08 UTC, Guillaume Piolat wrote:
> Hence Rust that sanctified this style.

And why it's not that interesting to the modern C++ programmer.

On 2017-04-22 13:35, David Nadlinger wrote:

> LDC officially supports shared libraries on macOS. -David

That's great.

-- 
/Jacob Carlborg