Youtube comments of Developer Voices (@DeveloperVoices).

  1. For me too. ❤️
    28
  2. Thanks! It takes me a ridiculously large amount of time to figure out what I'm going to say each week. I'm glad it's worth it. 😅
    13
  3. For the good of everyone (except the nodes that are dead). 😁
    12
  4. I can understand that. The way I see it, the whole of computing is fair game, so there will always be episodes on databases. Not every episode will appeal to everyone, but at 50 episodes a year I think that'll balance out. 🙂
    12
  5. Thanks! I wish I could have posted it when you needed it, because that would mean I'd discovered Neovim sooner too. 😁
    12
  6. Wow, what can I say except thank you! That's very kind of you to say. I'm glad if my joy and curiosity for coding is finding like minds. 😊
    11
  7. Thanks. I find guests in all the ways - my contacts, people I meet at conferences, recommendations from listeners, and more. There's no fixed pattern, except, "Are they doing something interesting?" 🙂
    11
  8. Yes. Kinda. Check back in two weeks for the exact answer. 😀
    10
  9. Yeah, I was perhaps a bit cavalier there. 🤦‍♂️ Of course OCaml programmers want to monitor and handle runtime problems, just as Erlang programmers want to get their code right before they ship. I was just trying to find a way to highlight the main point - Erlang's got a very unique and interesting approach to runtime problems. 🙂
    10
  10. Thanks! That seems to be the general vibe I'm getting. ❤️ I''ll be much happier if I can let the conversation decide the length, so if that's what people want it's a great relief. 😅
    10
  11. I've heard of it, and knew it was for GPU programming, but nothing beyond that. I've never dived into it. 🙂 (Actually, I think I did make a failed attempt to install in on my laptop once, which makes me think of the Zig episode we did on reliable cross-platform builds. 😁)
    9
  12. I can offer a couple of recommendations. I learnt from SICP, which is coming up to its 40th anniversary, but I think it still holds up as a great intro. And Luca Pette was recommending Crafting Interpreters in the recent TypeStream episode. SICP covers compilers as well as interpreters, but it's assuming a Lisp-like language so teaches almost nothing about parsing. I'll let you decide whether those are pros or cons. 😁 https://en.wikipedia.org/wiki/Structure_and_Interpretation_of_Computer_Programs https://craftinginterpreters.com/
    9
  13. I think you could be right, but it’s still a lot easier than getting all your users to adopt that new browser. 😅
    8
  14. Thanks - I'm glad you're enjoying them! We have about 10 future episodes already recorded, so I can 100% guarantee the next few months. 😄
    8
  15. Thanks! 😊
    8
  16. The phrase "living legend" definitely applies. 👑😁
    7
  17. Yeah, it’s a great way to work, if you have time on your side. A real antidote to the sprint-treadmill.
    7
  18. It was an absolute pleasure. 🙂
    7
  19. I do my best. Glad you're enjoying them. 😁
    7
  20. There's an official VSCode plugin: https://docs.modular.com/mojo/faq#is-there-ide-integration And I've been using Neovim. The mojo support was was straightforward to set up, as it's already part of in 'neovim/nvim-lspconfig'. Well, straightforward if you're already using Neovim for other coding. :-)
    7
  21. Yes, definitely want to do Vale. (Though I suspect the series will never be complete. 😅)
    7
  22. Well that escalated quickly. 😅 There certainly are privacy concerns, but also a lot of valid use cases. And everything they’re doing was already possible - the APIs have been there in the specs for years. I don’t think it’s time to dive straight into Godwin’s Law. 🥹
    6
  23. That's in the same area, but I think it's a different approach. A DSL generally makes it easy to write example-based tests. It's a great technique and a real time saver. But property testing is more general, saying something like: 1. An example username is any string. 2. An example email is `<any string>@<any string>.com`. 3. Come up with 10,000 random username/email pairs and call the register function. The number of registered users should always increase by one.
    6
  24. Agreed, there will always be a place for both. I actually faced that this week. I've got some serialization code that writes data to and from JSON. I've got some property tests that ensure that `x == decode(encode(x))` and it's way more thorough than I would ever be. But I also have a couple of hard-coded cases just so I know the JSON looks exactly the way I want it to look. :-) FWIW though, I think you could also write some property tests for cryptographic functions. For example, a good hashing function shouldn't generate similar-looking hashes for similar-looking input. So you might say, "Generate a document. Hash it. Now change one character in the document and check that at least 5 characters have changed in the hash. Now do that 10,000 times." Something like that would be a valuable check. :-)
    6
  25. Yeah, that's a weird one all right. 😅
    6
  26. Yeah. When you spend a lot of time typing, it really brightens up the keyboard. 😁
    6
  27. Odd - it works for me in other languages, so it should just be a question of whether your LSP server supports it...
    6
  28. Ah, thanks for letting me know. ❤️ Fixed!
    6
  29. Yeah, I've some sympathy with that argument. We do have a propellerhead tendency in our industry, jumping at fads and silver bullets in a heartbeat. Remember when Pair Programming and TDD were going to usher in a new golden age that made everything that came before look like the wild west? Where's all that hype now? But at the same time, we're also surprisingly intransigent. It's nearly 60 years since Tony Hoare committed his Billion Dollar Mistake and we're still inventing languages with null pointer exceptions. We've had networking for even longer and yet writing code that runs on multiple computers is still significantly harder than a single machine. Perl is in the build stack of nearly everything and COBOL is probably still at the heart of your bank, despite the fact that nearly no-one would make those choices today. We're both moving too fast and too slow. Which, on reflection, fits with our industry's age. Industrial computing is older than multiple careers, but still shorter than a single lifetime. So we're continually seeing people pushing for 'the new way' while at the same time being young enough to remember when you could run an entire accounting department on 64kb. Our memory is both too short and too long. Maybe one day we'll have it all figured out, but we're definitely not there yet. I keep searching for new ideas, experimenting, and adopting the most promising ones. Cautiously. 🙂
    6
  30. Glad you like them! I have a new process for gathering them as I edit, so they should be appearing much more regularly from now on. 😅
    6
  31. I'm glad someone picked up on that. 😉
    6
  32. Thanks, will do! (And it's Kris, for the record. 🙂)
    6
  33. I'm not sure what you mean. "What's the future of Elm?" was pretty much the first question I asked Evan, and his answer formed the bulk of the subsequent discussion. Of course, I would have loved it if the answer was, "The next version's out this week! And we'll have v1.0 by March!" But that's not the case, and I think Evan very eloquently explains why that's not the case.
    6
  34. I'd love to do that. It'll depend on finding the time, but yes, noted!
    5
  35. D'you know, I soooo nearly said, "If you actually write Prolog please get in touch." 😅 I'd love to hear what it's being used for...
    5
  36. Glad you're enjoying them! 😊 Bill and I actually spoke a few weeks back. You can expect that episode sometime in January. 🙂
    5
  37. Yes, he's definitely on my list. 🤞
    5
  38. Haha, yeah. These days Rust is nearly ‘mainstream’, right? 😅
    5
  39. Hehe, fair question. Either next week (10th Jan) or the week after. 🙂
    5
  40. 😂
    5
  41. I think what you've missed is how many people doing data engineering are stuck with unclean data in crappy data sources. I was asking if Flink would be any help in that ugly but all-too-common reality.
    5
  42. Ooh yes, good idea. The closest we have so far is the Mojo episode with Chris Lattner. It's definitely worth going down into MLIR itself. 🙂
    5
  43. For certain kinds of programs, that's exactly the right strategy. If something runs for a short amount of time, consumes a modest amount of memory, then exits, it's probably a smart approach. Some programs run faster if they just take all the memory they need and then throw it all back at the end. Compilers are a common example.
    5
  44. Ah, I'd not heard of Odin. I shall add that to my research list. Thanks!
    5
  45. It's 2023, I have a 3D printer, and it's probably more reliable than my 2D one. Welcome to the future. 😅
    5
  46. Yeah, hosting a podcast like that would hold zero interest for me. I'm here to learn too! :-)
    5
  47. My pleasure!
    4
  48. IKR? 😁
    4
  49. I was thinking about the declarative vs. imperative programming style, and the unification of sets of facts based purely on programmer-specified relationships.
    4
  50. Likewise! Thanks again for joining me Tyler. 🤜🤛
    4
  51. I think the real aim is to be in the same solution-space as C, without actually touching C. FTR, I don't dislike C. But I don't love it either. There's definitely room for improvement.
    4
  52. Poseidon would be a fantastic name for a language, if only because you could call it, "The King of the Cs." 😁
    4
  53. I believe it's much more tightly integrated than that - KRaft is very much a part of Kafka, and it runs in the same logical process as the broker. You can choose to run Kafka as "just" a broker, or as "just" a metadata-controller, or both at once. Either way, it's just configuration - you're not spinning up a separate service in the way you would Zookeeper. That said, yes, there are operational advantages to having some instances dedicated to brokering and other instances dedicated to quoruming: "The key disadvantage [of running in combined mode] is that the controller will be less isolated from the rest of the system. For example, it is not possible to roll or scale the controllers separately from the brokers in combined mode. Combined mode is not recommended in critical deployment environments." - https://kafka.apache.org/documentation/#kraft_config I read that as more an operational issue than a problem with combined mode per-se. 🙂
    4
  54. Erm...do you have a reference for that? 🤔
    4
  55. Awesome! Yeah, I've been having some fun with Gleam too - Louis' done a great job. :-)
    4
  56. Yes, I definitely want to get Louis back soon. And with a bit of luck & planning, I'll also have someone else from the lovely Gleam community on soon. 🥳
    4
  57. I’m pretty sure all modern programming languages are just three assembly language instructions in a trench coat. 😁
    4
  58. Yes! Good idea. I'll add that to my list of guests to research. Any suggestions for who would make a good interviewee?
    4
  59. Sam has been on my list for over a year now. He's promised to join me as soon as his home studio stabilises. 😁 As for Zig, Loris Cro's said he'll send me a signal flare as soon as Andrew emerges from the Development Mines. 🤞
    4
  60. Thanks, but...I think it's correct. "Running the gauntlet," originally referred to a military punishment where someone would be made to run between two lines of soldiers who would beat them as they went. Over time it expanded to mean crossing any path that's beset with problems on all sides. That's the sense in which I meant it. 🤜😱🤛 "Run the gamut," would work too, but wouldn't have the same implied difficulty. 🙂
    4
  61. Glad you enjoyed it!
    4
  62. Thanks! I'll add him to my list. 👍
    4
  63. Yeah, me too. 🚀
    4
  64. Ha yeah, I can understand that. It's possible, but sometimes in Elm it seems easier to print to a webpage. 😅
    4
  65. Oh that's interesting. You dislike the panning? Noted. 👍
    4
  66.  @CryptoDrewStreams I look forward to hearing about it. 😁
    4
  67. Yeah, it's never going away. Heck, we can't even get rid of COBOL in production. But I think there's huge value in being able to say, "This is a better option for new projects, and for legacy systems that really need to be rewritten." C will always be with us, but we don't necessarily have to keep increasing the amount of C in the world. 🙂
    4
  68. They can probably answer that better than I can - take a look here: https://ziglearn.org/chapter-5/ 🙂
    4
  69. You'll never guess who I interviewed yesterday. Stay tuned. 😉
    4
  70. Most property testing libraries will allow both. They run with a random seed, but if they fail they report the failure and the seed that was used. Then you can repeat the run with the same seed as-needed.
    4
  71. It's https://github.com/tomasr/molokai 👍
    4
  72. Aye aye sir. 😁
    4
  73. Yeah, there's a lot of appeal (and certainly a lot of brain food) in having a language that lets you manipulate its own code. Buuuuut...I wouldn't hold C up as a great example of that. It's string-based macro system kinda sucks. IMO, Lisp had the right idea here - let people manipulate the language *in the language*, with AST-transforms. It works so much better than string-munging. You might find Zig interesting. It's a C-style language with a macro system that works at the language level, rather than the source-string level. YMMV of course. 🙂
    4
  74. Sadly I can imagine we’ll still be writing COBOL in 100 years. 😅
    4
  75. Glad to be back. 😀
    3
  76. Thank you! I'm really glad you joined me. 👍
    3
  77. Yeah. I don't want to speak for Tyler, but I get the impression he learnt a lot there but is glad he's moved on the from that company's business model.
    3
  78. Not really. There's no cryptographic chain, and there's no decentralised consensus. The clients do attempt to predict the future state, but it's just a temporary guess. The final say rests with a centralised server. There is a similarity between deployment of the engine logic and the deployment of a smart contract, though. We discuss that in the latter part of the podcast. 🙂
    3
  79. Thanks! Glad you enjoyed it - I’ve been trying to line that one up for aaaages. 😅
    3
  80. That's a great idea! Yes, I'll drop the team a line immediately. Thanks! 👍
    3
  81. No disrespect was intended. Sadly there were a few places where we talked over each other—almost inevitable on a transatlantic conversation—and for clarity's sake I muted Nathan or myself. I try to be impartial on that,and just pick whichever side kept the conversation flowing best in that moment. 🙂
    3
  82. Wow, thank you. That's really kind of you to say. ❤️😊
    3
  83. Thanks! Glad you enjoy it. 😊
    3
  84. Thanks! One of my favourite things about this industry is that there’s always more interesting stuff to learn. I love being a part of that. 😊
    3
  85. Thanks! There are plenty more coming too. :-)
    3
  86. Oooh, nice. I'll drop a line to Sophia and see if she's interested. Thanks!
    3
  87. And more to come... 😅
    3
  88. Yeah, that's a thorny one. We also go out as an audio-only podcast on Spotify, Apple, etc., so we have to treat it like radio...
    3
  89. Well, it's easy to verify who created Odin, if you want to double-check. 🙂
    3
  90. Thank you. Corrected. 🤦‍♂️
    3
  91. Yes, the release notes say go for it. 🙂 It was deemed production ready for new clusters back in late 2022. Migrating existing clusters from Zookeeper was declared production ready with the release of 3.6, which happened on 10 Oct 2023: https://kafka.apache.org/blog#apache_kafka_360_release_announcement
    3
  92. Yes, definitely. I've sent him an email... 👍
    3
  93. Ha, yeah, and that's me trying to keep it together. 😉
    3
  94. Ha, yeah you're not the first to notice that. It's probably not the name I would have chosen, but 10 years on it's definitely too late to change. 😅
    3
  95. Terminal. I'm using Kitty: https://sw.kovidgoyal.net/kitty/
    3
  96. That'll be Telescope. Somewhere in the telescope codebase there'll be a for loop working its magic. 🙂 Glad you enjoyed it! Stay tuned for more. 😉
    3
  97. IKR? 😂
    3
  98. Ha, glad you like it. Sometimes I do little things like that and wonder if anyone gets it or if I'm just amusing myself. 😅
    3
  99. Ooh interesting. Not that I've heard of. That would probably make a great hack project for someone... 🙂 https://ellie-app.com/
    3
  100. Thanks for being a great guest! Ratatui's really a fun library to use - I hope this brings it some more enthusiasts. 🥳
    3
  101. You're welcome! 😊
    3
  102. The only one I'm aware of is XTDB. There's an interview about that here: https://youtu.be/3sRKQg9-In8 (As Ben suggests, you can build bitemporality into a regular database just by adding two timestamp columns and constructing the queries correctly. But XTDB is the only one I know of that actually tackles the parts of the SQL spec that make it easy.)
    3
  103. OMG, I'd not heard of AutoLISP. That's awesome. 😮 I'll have to research it and add it to the shownotes. Thanks!
    3
  104. I don't think so. But sometimes the most fun things in software start out as yak-shaves, right? 😅
    3
  105. Wow, Cobol's still harvesting fresh souls in 2023 huh? Good luck! 😅
    3
  106. 😂 I’m quite confident that in 100 years we’ll still be maintaining COBOL. 😅
    3
  107. 😁
    3
  108. Wow, thank you! I’m touched. 😊
    2
  109. Why black? That was just the colour I had on at that week. It's always changing. Why paint them at all? Because I like it. 🙂
    2
  110. Thanks. Stay tuned, there’s plenty more in the pipeline. 😀
    2
  111. Heck, I should have caught that. Thanks very much - I've updated the subtitles with your fixes. 🙏
    2
  112. I could see it. It feels like we finally have all/most of the tools at our disposal now. Both in terms of cheap disk and the software infrastructure to make the most of it.
    2
  113. Thanks! That's really great to hear. 😊
    2
  114. Haha, together we can expand!
    2
  115. Glad you enjoyed it!
    2
  116. Thanks Michael. I'm glad it's appreciated, and I'm pleased you're here. 🙂
    2
  117. Glad you enjoyed it!
    2
  118. 😂
    2
  119. Yeah, sorry about that. It's in there, but I mixed it too quietly this week. 🤦‍♂️
    2
  120. And thanks for the suggestion! 🙂
    2
  121. You didn't have to wait long - it's up now. :-D
    2
  122. Yes, I believe he was. There's a link in the shownotes. :-)
    2
  123. Geez, that's a design constraint I've never even considered... 😱
    2
  124. Glad you found it. 🙂
    2
  125. Our pleasure!
    2
  126. Whoever wins, we win. 😁
    2
  127. Thanks for the feedback! 👍
    2
  128. Ooh, nice idea. I'll add it to the list! 👍
    2
  129. Short answer: Scalable data processing platform between different data sources. Longer answer: https://youtu.be/RkSMEMswq3M
    2
  130. Thanks, will do! ❤️
    2
  131. Thanks!
    2
  132. You can call me a monster but I refuse to stop. 😁
    2
  133. Thank you. SPJ's an absolute legend. If I can stand next to him and look even half-decent, I'm winning. 😁
    2
  134. Thank you!
    2
  135. Oh that's very interesting - I didn't realise you could run Rust code inside the BEAM. 💡🙂
    2
  136. Dang, I’ll have to get my rhetorical devices to pay off more quickly next time. 😅
    2
  137. That's a really tough question. I don't think Louis' in any hurry to put the 1.0 badge on it, but I also know it's already in use in production. I guess it also raises the question, what does 1.0 mean? Production ready? Supported? Guaranteed not to make any major changes? Stack overflow already has answers to most of your questions? My impression is that what's already there is high quality enough to start relying on, but there's a lot of design work and fleshing out still to do. For anything more definite, I think you should probably head to the Gleam Discord and strike up the conversation. :-) https://discord.gg/Fm8Pwmy
    2
  138. Oops, sorry. Hopefully that's better in recent episodes - I was still finding my feet for this one. 😊
    2
  139. Yeah, it was a pretty sweet prize. And like Jon said, it's not the monetary value so much as the recognition on the day. 🙂
    2
  140. I so nearly dropped that pun into the intro, but I figured it wouldn't i18n well. 😁
    2
  141. I totally agree. ❤️
    2
  142. Dang! Thanks for letting me know. Not sure what happened there - it should be exactly the same as the video version, but clearly not. I've just shipped a fix. Thanks again!
    2
  143. You're welcome! 🙂
    2
  144. Haha, not specifically aiming for wizard but I’m happy to get there by accident. 😁
    2
  145. Awesome! Ben was so great in that episode - great to hear you enjoyed it too. 😁
    2
  146. I'd love to! She's totally in my personal Hall of Fame. I did try to get her on a few months back, but couldn't get a hold of her. Maybe it's time to gently try again. 🤞
    2
  147. Thanks for the feedback! And thanks, I did my very best to pronounce it correctly. I'm better with programming languages than human ones, but I try. 😅
    2
  148. Thanks. And I will. ❤️
    2
  149. Glad you like them! Keep an eye on this playlist - I'll be adding more there as they come: https://www.youtube.com/playlist?list=PLuiPju9KQBnatff3GerbYpqPijpDRJp9p 🙂
    2
  150. Ha, me too. 😅
    2
  151. Funnily enough, I only found out about hop last night. So in the video it was easymotion, but I think it's going to be hop going forward. :-)
    2
  152. 😝
    2
  153. <googles> Ooh, Smalltalk huh? Cool. Yes, I'll reach out to him. :-)
    2
  154. Ooh, good idea. Added to my list. 👍
    2
  155. Yes, absolutely! You can find links to all the major platforms from here: https://pod.link/developer-voices
    2
  156. Harsh! 😂
    2
  157. Maybe I need to look into this further, but on the surface of it…I wouldn’t equate supporting a charity that helps the children in a country with supporting the government of that country. If we did, wouldn’t that apply to UNICEF and UNHCR too? 🤔
    2
  158. Glad you're enjoying it! I don't have one specific source. It comes from a combination of reading around, meeting people at conferences and recommendations from friends, listeners and other guests. 🙂
    2
  159. Bill and I recorded a discussion earlier in the month. Expect it out mid-January. 😊
    2
  160. Thanks! I have plenty more coming. 😁
    2
  161. It looks like that's not going to happen: https://github.com/ziglang/zig/issues/161
    2
  162. Hmm...local playback speed settings? The original's definitely at normal speed. 🙂
    2
  163. Programmers have been using the term footgun for decades. It’s not exclusive to people intelligent enough to speak more than one language. 🙂
    2
  164. Oh, that's (accidentally) very funny! Thanks for pointing it out - I've corrected the subtitles to 'defer'. 😅
    2
  165. I don't think any language can really claim to be the fastest. But I'd certainly expect Zig to be among the fastest.
    2
  166. Thank you so much!
    2
  167. I don't, sadly, but having looked around Hypothesis is definitely where I'd start. It looks good. 👍
    2
  168. Thanks!
    2
  169. Yeah, the tricky thing for me to judge with a vide like this is what do I put in, what do I leave out? I couldn't see a way to include custom serialization code without adding in a lot of extra explanation about PureScript's language features. And that would have muddied the main point. FWIW, here's an example of the custom serialization code. The testing side would remain the same as in the video: https://github.com/krisajenkins/FallFolks/blob/main/src/Common/Types.purs#L165-L172
    2
  170. Martin Kleppmann, the author of Designing Data-Intensive Applications. 🙂
    2
  171. Thanks! I'm glad to hear it. ☺️
    2
  172. Awesome, thank you!
    2
  173. Agreed on all points. Off camera, Evan said there will come a time when he's ready to announce concrete things, and when that comes he'll be back here for round 2. I'm looking forward to it. :-) And Richard? Well him I can deliver immediately: https://youtu.be/DzhIprQan68
    2
  174. True! I could happily have spent another hour on that discussion. 😅
    2
  175. Thank you. 😊
    2
  176. Hehe, I made sure he taught me beforehand. 😁
    2
  177. Thanks! 😊
    1
  178. Oooh, that's interesting - can you expand on that a little? Because apart from the episode on Community Management, I'd say all our guests have been software engineers. 😊 What are we missing? What kinds of guests would you like to see? 🙂
    1
  179. My pleasure!
    1
  180. Thanks! Yes, I'm currently trying to set that one up. 👍
    1
  181. Nice suggestion. Thanks, I'll get in touch. 👍
    1
  182. I don't write as much Lisp as I used to, but it remains one of my favourite languages. ❤️ You might like this episode we did on Lisp a while back: https://youtu.be/fytGL8vzGeQ
    1
  183. ​ @criticalcitizens  Ouch! I hope that was all money you could afford. 😨
    1
  184. Game of War I think. :-)
    1
  185. Ooh, maybe we should do an episode on SurrealDB. 🤔👍
    1
  186. Thanks! 🤗
    1
  187. Haha. Definitely the former, but I think the colour makes it more noticable. 😁
    1
  188. You’re welcome!
    1
  189. 😂
    1
  190.  @joelalexander928  It's amazing how many things boil down to a finite state machine. It's one of those universal patterns in programming we keep rediscovering. 🙂 Glad you're enjoying it!
    1
  191. You're welcome. I hope you have as good an experience with it as I have. :-)
    1
  192. You could definitely argue that docker takes care of the installation side of usability. But there's a lot more to usability than just installation/configuration. For example, one of DuckDB's usability features I really like is simply being able to say, "SELECT country, count(*) FROM 'users.json' GROUP BY country". Running queries directly on JSON files, without needing to create a table or define a schema, is a fantastic usability feature. 🙂
    1
  193. Thanks! ❤️
    1
  194. Thanks! So glad you're enjoying it. 😊
    1
  195. Thanks for listening!
    1
  196. Thanks! 😊
    1
  197. Thanks so much! I hope your prediction comes true. 😁
    1
  198. Ah, I think I’d missed your point the first time around. You’re saying that the advantage of config file is you’ve got many reader implementations to choose from? That I’d have to agree with. You’re tied to one way of expressing the answer, but free to choose how that’s interpretted. 👍
    1
  199. True, but I currently have myself surrendered to the person who spec’d YAML, and I’m not certain I’m happier. 🤷🏻‍♂️
    1
  200. Haha, I have the same problem. 😅
    1
  201. That really makes me wonder which country you're in. I'm going to guess it's not the US or UK. My experience with banks in those countries is that, sadly, it's an uphill battle to achieve any meaningful change. :-(
    1
  202. I think it's more that they bought Github and didn't care what extras it came with. 😁
    1
  203. Thanks!
    1
  204. Thanks you. 😊
    1
  205. Ooh, interesting. Added to my list, thanks!
    1
  206. Thanks David! Plenty more on the way. 😁
    1
  207. Haha, yeah sorry. Old habit from the days when I'd only read the word 'linux' in books. I find it hard to shake. 🤦‍♂️
    1
  208. Surely Satan is more like Loki than Odin? 🤔
    1
  209. I don’t want to speak for Bill, but I suspect he’d very broadly agree, and argue that that’s a good thing. As for me, I’m Switzerland. All ideas and perspectives considered. 😁
    1
  210. You might be interested in Hare. Drew DeVault's writing that as a C replacement, and he's writing an OS too, to answer exactly your point. https://youtu.be/42y2Q9io3Xs
    1
  211. Yeah, I fretted over that one. I think both are considered valid, and I figured if I pronounced it 'matrixes' then everyone—including non-native speakers—would know what I was referring to. Next time I think I'll just try to say it in a way that avoids the plural altogether. 😅
    1
  212. Nah, some people want to build on what's come before, and that's exactly the way it should be.
    1
  213. Thanks!
    1
  214. Thank you! 🥳
    1
  215. Glad you enjoyed it!
    1
  216. Aw, thanks. :-)
    1
  217. He really is. ❤️
    1
  218. Thanks George! That one was a particular pleasure to record - Simon's an absolute legend. 🤩
    1
  219. Thanks! On both fronts! 😁
    1
  220. And it’s so good to be back. 😁
    1
  221. And it’s so good to be back. 😁
    1
  222. Totally. :-D
    1
  223. Can we agree on...unusual? 😁
    1
  224. 😂
    1
  225. 😅
    1
  226. Thanks! I'm really glad you liked it. I'm looking forward to releasing many more. :-)
    1
  227. Do you mean like something Racket-esque? I don't think Gleam intends to be a language where users can dynamically extend the language itself. It's a very interesting point in the design space though. Maybe we should do an episode on Racket... 🤔
    1
  228. I can neither confirm nor deny. I’m Switzerland. 😅
    1
  229. I'd try the recently-released Exercism track: https://exercism.org/tracks/gleam IIRC, it was written by Louis, so you'll be in good hands. :-)
    1
  230. Thanks!
    1
  231. Love it, thanks! 😁
    1
  232. My pleasure! It was an unexpected treat - I'm really glad we talked. 😀
    1
  233. Thanks! Will do. 😁
    1
  234. Haha. Loving DuckDB at the moment. 😁
    1
  235. Thanks! Hopefully in time, we will. 🤞
    1
  236. Thanks!
    1
  237. I know! 😭 I missed out a 't', and only realised after it was published. Youtube doesn't let you edit videos, so I will have to live with my shame. 😔
    1
  238. Thanks! I hope so. 😀
    1
  239. Thanks, glad you think so!
    1
  240. I think that 'just' is hiding a heck of a lot of work. I mean, Python's over 30 years old and—all being well—it'll finally remove the GIL* sometime this year. Retro-fitting the kind of optimisations that Chris is talking about is possible, sure, but it might not be realistic. 🤔 * https://realpython.com/python-gil/
    1
  241. No.
    1
  242. Over here, we're all trying to guess which actor you could mean. 😁
    1
  243. Glad it was helpful. Good luck with the interview!
    1
  244. Thanks! Glad to hear it. 🙂
    1
  245. Thanks! ☺️
    1
  246. Thank you!
    1
  247. I really like both of them. Emacs (with evil-mode) was my main editor for years, and I think either is a great choice. I find Emacs Lisp to be more fun to write than Lua, because the interactive development experience is absolutely world class. Lua's still good, it's just that elisp is astonishingly good. But some of Emacs' UI experience is need of a refresh, which gives Neovim a day-to-day edge. The Neovim team have done a great job of pulling the terminal into the 21st century. :-)
    1
  248. Sounds like you need to install `lua-language-server`. On OSX that's `brew install lua-language-server`, but YMMV. :-)
    1
  249. If I could get a degree in Witchcraft, I’d be all over that. Until then, I’ll have to content myself with DnD. 😅
    1
  250. Ah, great question. So I started off with this developer's guide: https://github.com/nvim-telescope/telescope.nvim/blob/master/developers.md ...and then the rest I picked up from reading source code.
    1
  251. Thanks!
    1
  252. Oops, thanks for spotting. Fixed! Yeah, they're auto-transcribed, and then I proof read them as best I can in the time I have. 😊
    1
  253. I'd give Hugh's book a try. It's a free download away: https://go.lightbend.com/designing-reactive-systems-role-of-actor-model
    1
  254. Ooh, thanks - will do!
    1
  255. I think he just misspoke. I'm sure Hugh knows Erlang's older than that.
    1
  256. Yes indeed. I'm aiming to record one next week. :-)
    1
  257. Eeeh, I'd totally agree there are some very old projects that are still going strong. But could you really say bash has been reinvigorated somehow? I think if I showed the copy of bash on my Mac to someone from the 90s, they'd see almost exactly the same tool. Whereas if you're trying to write a plugin for Neovim, it's a completely different experience running from the same original Vim codebase.
    1
  258. Small world huh? See you at the next one. 🥳
    1
  259. Yeah. Agile was supposed to get us closer to that kind of feedback loop....I'm not sure how often it happens in practice...
    1
  260. Yeah, me too. I'm currently speaking to the Zed team to get someone on the show. Look out for a dedicated episode...some time in May? 🙂
    1
  261. Thanks!
    1
  262. Ooh, this news just in. Vik Fearing has done some work adding support into Postgres. Anything from Vik is worth checking out: https://twitter.com/pg_xocolatl/status/1680932577115361280
    1
  263. Excellent! Glad it helped!
    1
  264. Probably my best answer to that question is to point you to this previous episode: https://youtu.be/crM2Smhbvmk 🙂
    1
  265. Ooh, yeah that's a good one. I'll add it to my research list. 👍
    1
  266. One of the greatest! Did you hear there's another installment coming soon. Portal Prelude I think it's called. :-)
    1
  267. Yes, there's a lot of overlap.
    1
  268. Well…I always thought so. But I’m open to correction. 😁
    1
  269. Thanks David - I appreciate your support! :-D
    1
  270. 😂
    1
  271. Thanks! I'm glad you're enjoying it!
    1
  272. One thing I love about the podcast format is, I try to aim for roughly a certain length, but if things are too interesting to stop then we're always free to keep going. 🙂
    1
  273. I think that's generally true for adding stuff. Adding new features is relatively easy. The hard part is taking away. Personally I'd remove C's macro system entirely, but that's never going to happen. And that's just one example. 🤷‍♂️
    1
  274. Yup, D is on my research list. :-)
    1
  275. Thank you!
    1
  276. Thanks. 😂
    1
  277. Oh interesting. That led me to a search which leads to this: https://tinyurl.com/5ye2zr9c I might debate the word 'trivial', but it's nice to see it's totally possible. :-)
    1
  278. I think it all depends. Different programmers are comfortable with different levels of abstraction. It's a spectrum, and that's okay. Personally I find Go too restrictive in what abstractions it can express, and I like a langauge like Haskell. But I can easily find Haskell code that's too abstract for my comfort zone: https://hackage.haskell.org/package/recursion-schemes-5.2.2.5/docs/Data-Functor-Foldable.html#v:chrono We need languages that cater for everyone. And languages that stretch everyone too. :-)
    1
  279. If you were a lawyer, trying to use English to accurately describe a contract worth millions, I think you'd see the problems with English. (But you still wouldn't have any prospect of replacing it. 😅)
    1
  280. Thanks!
    1
  281. 😂
    1
  282. 😁
    1
  283.  @shaurz  Sure have! That's over here: https://youtu.be/aKYdj0f1iQI
    1
  284. Oh, I had no idea you were local. I'll look out for you on future runs. :-D
    1
  285. Thanks! Maybe we can all catch up in person sometime? 🙂
    1
  286. Thanks! (I confess, I have been wrestling with the balance of the intro/outro music. I'll keep working on it. :-D )
    1
  287. 😁
    1
  288. From the sounds of it, that would be a very achievable project. 🙂
    1
  289. Nice! I'd love to hear a sample. 🎧
    1
  290. Thanks for the support! ❤️
    1
  291. Thanks!
    1
  292. Thanks!
    1