www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.announce - D at 20: Hits and Misses, and what I learned along the way Oct 19

reply Walter Bright <newshound2 digitalmars.com> writes:
I'll be speaking at the Northwest C++ Users's Group on Oct 19.

https://nwcpp.org/

Work began on the D programming language 20 years ago. A huge part of language 
design is looking at the past for what worked and what didn’t, and divining 
future trajectories so the language can be where the ball lands. D has its
share 
of strikes and home runs. I’ll be talking about a few of each, and lessons 
learned the hard way. I’ll pontificate a bit about where programming
languages 
and D are headed.
Sep 22 2019
next sibling parent reply Peter Jacobs <peterj mech.uq.edu.au> writes:
On Sunday, 22 September 2019 at 19:40:48 UTC, Walter Bright wrote:
 I'll be speaking at the Northwest C++ Users's Group on Oct 19.

 https://nwcpp.org/
That page says "Oct 16th, 2019 at 7:00 PM".
Sep 23 2019
parent Walter Bright <newshound2 digitalmars.com> writes:
On 9/23/2019 12:38 AM, Peter Jacobs wrote:
 On Sunday, 22 September 2019 at 19:40:48 UTC, Walter Bright wrote:
 I'll be speaking at the Northwest C++ Users's Group on Oct 19.

 https://nwcpp.org/
That page says "Oct 16th, 2019 at 7:00 PM".
Oops, you're right!
Sep 23 2019
prev sibling next sibling parent reply "H. S. Teoh" <hsteoh quickfur.ath.cx> writes:
On Sun, Sep 22, 2019 at 12:40:48PM -0700, Walter Bright via
Digitalmars-d-announce wrote:
 I'll be speaking at the Northwest C++ Users's Group on Oct 19.
 
 https://nwcpp.org/
 
 Work began on the D programming language 20 years ago. A huge part of
 language design is looking at the past for what worked and what
 didn’t, and divining future trajectories so the language can be where
 the ball lands. D has its share of strikes and home runs. I’ll be
 talking about a few of each, and lessons learned the hard way. I’ll
 pontificate a bit about where programming languages and D are headed.
Will this talk be posted somewhere like Youtube afterwards? I'd love to hear it, but can't attend in-session for practical reasons. T -- Being able to learn is a great learning; being able to unlearn is a greater learning.
Sep 23 2019
next sibling parent reply Walter Bright <newshound2 digitalmars.com> writes:
On 9/23/2019 10:49 AM, H. S. Teoh wrote:
 Will this talk be posted somewhere like Youtube afterwards?
Yes, though sometimes it doesn't due to various failure modes of the camera and operator :-)
Sep 23 2019
parent reply "H. S. Teoh" <hsteoh quickfur.ath.cx> writes:
On Mon, Sep 23, 2019 at 02:55:00PM -0700, Walter Bright via
Digitalmars-d-announce wrote:
 On 9/23/2019 10:49 AM, H. S. Teoh wrote:
 Will this talk be posted somewhere like Youtube afterwards?
Yes, though sometimes it doesn't due to various failure modes of the camera and operator :-)
There should be redundant, decoupled camera/operator crew to solve this problem. ;-) T -- Chance favours the prepared mind. -- Louis Pasteur
Sep 23 2019
parent reply Walter Bright <newshound2 digitalmars.com> writes:
On 9/23/2019 3:01 PM, H. S. Teoh wrote:
 On Mon, Sep 23, 2019 at 02:55:00PM -0700, Walter Bright via
Digitalmars-d-announce wrote:
 On 9/23/2019 10:49 AM, H. S. Teoh wrote:
 Will this talk be posted somewhere like Youtube afterwards?
Yes, though sometimes it doesn't due to various failure modes of the camera and operator :-)
There should be redundant, decoupled camera/operator crew to solve this problem. ;-)
I know. The same thing happened at DConf 2018, where the first morning's sessions were all lost.
Sep 24 2019
next sibling parent Joseph Rushton Wakeling <joseph.wakeling webdrake.net> writes:
On Tuesday, 24 September 2019 at 23:27:44 UTC, Walter Bright 
wrote:
 On 9/23/2019 3:01 PM, H. S. Teoh wrote:
 On Mon, Sep 23, 2019 at 02:55:00PM -0700, Walter Bright via 
 There should be redundant, decoupled camera/operator crew to 
 solve this
 problem. ;-)
I know. The same thing happened at DConf 2018, where the first morning's sessions were all lost.
Going by the lessons of DConf 2015, I reckon we should always have at least one person using their laptop to stream to YouTube ;-)
Sep 25 2019
prev sibling parent Ron Tarrant <rontarrant gmail.com> writes:
On Tuesday, 24 September 2019 at 23:27:44 UTC, Walter Bright 
wrote:

 I know. The same thing happened at DConf 2018, where the first 
 morning's sessions were all lost.
Does this fall under the category of "things I learned the hard way?" :)
Oct 18 2019
prev sibling parent reply Dennis <dkorpel gmail.com> writes:
On Monday, 23 September 2019 at 17:49:12 UTC, H. S. Teoh wrote:
 Will this talk be posted somewhere like Youtube afterwards?
It's up now! https://www.youtube.com/watch?v=p22MM1wc7xQ
Oct 17 2019
next sibling parent reply "H. S. Teoh" <hsteoh quickfur.ath.cx> writes:
On Thu, Oct 17, 2019 at 07:24:20PM +0000, Dennis via Digitalmars-d-announce
wrote:
 On Monday, 23 September 2019 at 17:49:12 UTC, H. S. Teoh wrote:
 Will this talk be posted somewhere like Youtube afterwards?
It's up now! https://www.youtube.com/watch?v=p22MM1wc7xQ
Huh. Walter says binary literal were removed from D, so how come the following still compiles on git master?? pragma(msg, 0b1000_1000); T -- It is widely believed that reinventing the wheel is a waste of time; but I disagree: without wheel reinventers, we would be still be stuck with wooden horse-cart wheels.
Oct 17 2019
parent reply Dennis <dkorpel gmail.com> writes:
On Thursday, 17 October 2019 at 20:39:41 UTC, H. S. Teoh wrote:
 Huh.  Walter says binary literal were removed from D, so how 
 come the following still compiles on git master??

 	pragma(msg, 0b1000_1000);
I was surprised by him mentioning that as well. I'm glad it stayed too, since I actually use them. When encoding in utf8 a code point of two code units for example, I think this looks really clean: ``` buf[0] = 0b1100_0000 | (chr >> 6) & 0b01_1111; buf[1] = 0b1000_0000 | (chr >> 0) & 0b11_1111; ```
Oct 17 2019
parent Adam D. Ruppe <destructionator gmail.com> writes:
On Thursday, 17 October 2019 at 20:56:54 UTC, Dennis wrote:
 I was surprised by him mentioning that as well. I'm glad it 
 stayed too, since I actually use them.
Indeed, me too. And they are definitely still there and I'd be quite sad if they disappeared.
Oct 17 2019
prev sibling parent reply Walter Bright <newshound2 digitalmars.com> writes:
On 10/17/2019 12:24 PM, Dennis wrote:
 On Monday, 23 September 2019 at 17:49:12 UTC, H. S. Teoh wrote:
 Will this talk be posted somewhere like Youtube afterwards?
It's up now! https://www.youtube.com/watch?v=p22MM1wc7xQ
Slides: https://digitalmars.com/articles/hits.pdf
Oct 17 2019
parent Ethan <gooberman gmail.com> writes:
On Friday, 18 October 2019 at 01:37:01 UTC, Walter Bright wrote:
 Slides: https://digitalmars.com/articles/hits.pdf
Tangent time. In regards to floating point:
 Unable to convince people that more precision is worthwhile
I'm actually waiting for quad floats to have hardware support. Registers are already wide enough, just nothing internally or in terms of instruction set for them yet. But yeah. The reality is that the hardware I operate on uses 32-bit floats almost exclusively on the CPU (the sole exception I can think of is the main simulation timer, you don't want that as a 32-bit float). GPUs and shaders use 16-bit half floats extensively these days. But 64-bit is a rarity because operations take 40% more execution time on average with my own tests and we can forsake the accuracy for execution time. This might change in a 4K TV world. Haven't really done too much with them yet (despite Quantum Break supporting 4K, but I didn't really notice anything glitchy that I could associate with floating point imprecision). Still. 64- and 128-bit floats are quite useful for offline calculations. Make your data as accurate as possible, then let the runtime code use the fastest execution path it can.
Oct 20 2019
prev sibling parent Walter Bright <newshound2 digitalmars.com> writes:
Reddit: 
https://www.reddit.com/r/programming/comments/djgsdy/d_at_20_hits_and_misses/
Oct 17 2019