Thread overview
[OT] "Safe Systems Software and the Future of Computing" talk by Joe Duffy
Sep 02, 2017
Paulo Pinto
Sep 03, 2017
Walter Bright
Sep 03, 2017
Mike Parker
September 02, 2017
Hi everyone,

Videos of Rust Conf 2017 are now available, and Joe Duffy did the closing keynote telling his experience developing Midori.

Specially relevant are the parts where he explains the internal resistance from classical C devs at Microsoft, adopting a more safe systems programming.

https://www.youtube.com/watch?v=EVm938gMWl0

Some of his ideas also apply to improving D's adoption among system devs.

--
Paulo
September 02, 2017
On Saturday, 2 September 2017 at 20:03:17 UTC, Paulo Pinto wrote:
> Hi everyone,
>
> Videos of Rust Conf 2017 are now available, and Joe Duffy did the closing keynote telling his experience developing Midori.
>
> Specially relevant are the parts where he explains the internal resistance from classical C devs at Microsoft, adopting a more safe systems programming.
>
> https://www.youtube.com/watch?v=EVm938gMWl0
>
> Some of his ideas also apply to improving D's adoption among system devs.
>
> --
> Paulo

Thanks for sharing this, looks quite interesting so far.
September 03, 2017
On 9/2/2017 1:03 PM, Paulo Pinto wrote:
> Some of his ideas also apply to improving D's adoption among system devs.

Some interesting observations he made:

1. rigor is not wanted when prototyping

D recognizes this in that you can ignore @safe programming and pretty much all of the annotations when writing quick & dirty prototypes.

2. syntax matters

This has always been a focus with D, in that the syntax is meant to be easy and familiar.

3. Incrementalism matters

This is the focus of -betterC, where D can be incrementally adopted by existing programs, rather than all-or-nothing.
September 03, 2017
On Sunday, 3 September 2017 at 15:46:36 UTC, Walter Bright wrote:
> On 9/2/2017 1:03 PM, Paulo Pinto wrote:
>> Some of his ideas also apply to improving D's adoption among system devs.
>
> Some interesting observations he made:
>
> 1. rigor is not wanted when prototyping
>
> D recognizes this in that you can ignore @safe programming and pretty much all of the annotations when writing quick & dirty prototypes.
>
> 2. syntax matters
>
> This has always been a focus with D, in that the syntax is meant to be easy and familiar.
>
> 3. Incrementalism matters
>
> This is the focus of -betterC, where D can be incrementally adopted by existing programs, rather than all-or-nothing.

Sounds like blog post material.