This is a rerecording of a recent talk I gave at the New Jersey Programming Language Seminar on the D programming language. It's a brief tour of the D programming language, why I enjoy the language(i.e. my 'sales pitch'), and also why I think there's more to choosing a programming language than a single dimension (which we often do). In any case, I encourage folks to try as many programming languages and tools as you can, and see which ones you like and find which language may be your competitive advantage -- maybe it will be the D language!
Everyone around Walter Bright kept calling it D because it was a modern language with C-like syntax. Thus, D the next letter in the alphabet and eventually Walter gave in. :)
Thank you so much, we always use your resources and it's basically our main go-to if we don't understand anything from dlang.org (which happens majority of the time) I hope you can keep making videos and maybe start doing some programming problems so we can better understand where each syntax is used
I am truly thankful and will continue to binge watch your vids
It's worth noting many (A majority as I understand) AAA game studios end up writing their own STL. I'm willing to bet many industries where performance is the primary concern also write much of their core libraries from scratch.
D lets user opt-out of collector as needed which is quite nice. D has been used in AAA game development for what it's worth as well.
- It's both fast for prototyping and also scales well for large applications.
- Compiles very fast with DMD and supports many platforms with LDC and GDC.
- CTFE (compile-time function execution) is a big win.
- standard library has enough of the common things (json, sql, csv, curl, sockets, etc.) that I need for my domain. Other stuff I can usually find a package or C library to read in if needed.
- most of the defaults seem right to me in the language versus C++ (variable initialization, struct as value type by default, explicit casting, module system, thread-local data, etc.)
Ecosystem does need a boost but I think that's actively developing, so code-d plugin for VSCode is a good place for most to start (I prefer VIM). Ecosystem seems to be slowly and steadily growing otherwise.
I can post links to more video tutorials if useful (disclaimer: I made them :) ).
I wanted to share a video and recent article on getting started with time travel debugging using the freely available 'rr' tool on Linux (Full disclosure, I'm the author :) ).
Debugging is the number one skill (from my conversations) I hear from employers that they wish new software engineers had more experience with. Anyway, here is my small part to introduce one of many debugging technique to beginners.
Note, time travel debugging/reverse debugging has been around for quite some time! Check out what time travel tools your language has on the wiki if C++ isn't your default language :)
