Hearted Youtube comments on Developer Voices (@DeveloperVoices) channel.

  1. This was awesome - the interactive aspect and ability to pause/ resume in many lisp implementations is relatively little discussed - and very powerful in scientific computing / engineering. Longevity/ low maintenance is also an underestimated factor. I would have loved some screenshots / quick video demo. Anyway I loved that scientific computing got a peek, and hope to see more.
    4
  2. Best programming language of all time. (collide like a super nova)
    4
  3. I finally worked out what a term was that I must have misheard (and so must the subtitles translator) - sheeted code. For those that don't understand the wonderful accent, Juan is meaning JIT/JITted code, not sheeted code. And Smalltalk IoT is Smalltalk-80, of course. "Shamp" is jump. I hope these help. Aside from that misunderstanding, this is an excellent low-level interview about the guts of Smalltalk.
    4
  4. Great podcast. Always enjoy hearing about tigerbeetle, and even after consuming heaps of tiger beetle content - I always learn something new. Seems this new consensus algorithm needs to be adopted into all control plane / manager services. Thanks for the content!
    4
  5. Sam is such a fascinating guest! One of your best episodes yet, Kris!
    4
  6. Very interesting, thank you!
    4
  7. great discussion, really relevant for not just zig but the process of building and shipping native projects in general
    4
  8. Im very interested in Mojo. It still seems to be too young for me but as Rust developer I look forward to moving to Mojo at some point.
    4
  9. Wow great channel what a gem in a haystack! Liked and subscribed! I'm currently starting learning Rust and deepening my knowledge in C coz both can help speedup my Python code. I'm interested to know if Zig does something similar? C does it via Cython, Rust via PyO3.
    4
  10. if its ziggin i`m zagging a like 🤣
    4
  11. Hey I know that guy! 🥳.
    4
  12. What an epic intro! Great guest too
    4
  13. Babe wake up, new Evan Czaplicki interview just dropped!
    4
  14. Very well explained and great pacing!
    4
  15. Every time I listen to this guy I have to google a bunch of stuff lol.
    4
  16. This is the conversation about mojo I’ve been waiting for thank you {K|Ch, ris}
    4
  17. The two hardest problems in computer science are (1) naming (2) caching and (3) off-by-one errors.
    4
  18. “Erlang is weird. And I’m saying that as a Lisp/Haskell guy” Yiiiikkkeess. When a Lisp dev thinks a language is weird…
    4
  19. Been going down the Duck, erm, rabbit hole the last few weeks and it’s already made me decide to switch our Spark jobs to Duck. Quack quack!
    4
  20. You are such a competent interviewer, thank you so much for all your podcasts !
    4
  21. I honestly don't think Erlang looks bad at all...
    4
  22. Enjoyed every bit of the talk! Hope this channel grows and keeps you motivated to put out content :)
    4
  23. this will be Chris Lattners Masterpiece, i am beyond excited, thanks for this amazing interview
    4
  24. Fantastic podcast! Joran can talk for days on end about his baby, it must be quite inspiring to be on his engineering team. Developer voices ought to be an order of magnitude more popular, this was great
    4
  25. Fantastic interview. Agnes is in rarefied air up there, dealing with CFD and then transitioning to FHE. Thanks for hosting her and asking such excellent questions!
    4
  26. Amazing! ❤
    4
  27. Thank you for these great interviews. I'm always surprised how HARD things are. I work with financial data and JS likes floats, accounting likes fixed point or ints to the cent. And a lot of times I'm sending CSV files with text that will be converted to whatever type is used by the receiving database. Data Pipelines are HARD. Sure, Debits and Credits work with INTs, but what if I want to multiply by a monthly interest rate to 5 significant digits. A lot of times I'm not looking for "correct" calculations, but consitant ones. I love the precept of "LOVE YOU DATA." And always have to beware things that work perfectly fine for 90% of cases. That 10% gets you in trouble.
    4
  28. I like the haircut
    4
  29. Creating these languages is impressive
    4
  30. ​ @DeveloperVoices  Now it needs to start being taught in university!
    4
  31. We have reached peak geekdom with the SQL license plate. Great stuff as always!
    4
  32. I've been "planning" a digital audio project for years (yes years, it's a hobby project I can faff around for as long as I like) and haven't been able to find the right language (I want high-level - but not too high and I want interop with assembly-language)... and Zig is my current candidate. The original code I worked on years ago was C++ and I don't want to go back there, I've considered Rust but it IS like C++'s type-safe younger brother like Loris says and we don't like that. But now I've heard that Andrew Kelley was actually working in the same area when he started on Zig, I think even more that it might be the answer I've been looking for.
    4
  33. Always able to find people doing facsinating things with tech, was really interesting. A type of dev work I didn't even realise was a thing, but makes obvious sense why when you hear it does.
    3
  34. I really enjoyed this episode, it was interesting to hear the perspective of someone who not only has ADHD but understands how it affects themselves, how it differs from others with the same diagnosis and the strengths and challenges it provides in navigating the development world. To address the closing question of the podcast, I'm more than happy for the net to be widened as you put it in regards to future podcast topics :)
    3
  35. Your interviewing skills are astonishingly good. Wonderful channel!
    3
  36. While watching this I ended up building zig on my system. Can't wait to try it out!
    3
  37. 2:33 - holy shit that was smooth!
    3
  38. Great questions! Maybe a little intro about the speaker and who he is? just throwing some positive feedback out there 🙏
    3
  39. Gleam is looking quite polished with v1.0
    3
  40. Not a doctor, but the way Kris is able to let his guests talk for so long without interrupting them, makes me believe that indeed, he probably does not have ADHD :) Thanks a lot for the video
    3
  41. Great episode. I learned about some really interesting sounding projects that I hadn't heard of before (ReasonML and ReScript). I really like the idea of bringing Erlang and OCaml together. Really interested to see where this project goes!
    3
  42. I gave Zed a try several months ago and was impressed by the performance. It has become my go to editor for anything else, where I don't need special debugger features or tool chain support. My wish would be, make it the go to editor for Rust! Rust really needs a good editor with toolchain support and remote debugging. Here all the big players have issues or are very complex to handle. I know that because I use it all the time. But for the record, great work! Zed is outstanding and I love it!
    3
  43. great interview!
    3
  44. Love Prof Schafmeister's way. Would be very intestering to have a coding live session using both cando & clasp!
    3
  45. thank you for another good talk krish. I kind of don't like the Roc language after trying it for a while because it tries to emulate the elm and it fails spectacularly, it literally fails at everything it tries. I also don't like what the community did to Evan and elm in general. other than its not the worst the language I've come across.
    3
  46. Super interesting and fun episode. Thank you both!
    3
  47. This guy is good vibes
    3
  48. That hair is the definition of majestic
    3
  49. Property Testing sounds like a really great idea. As someone who is already using data-driven tests in production, if I could extend the code which is producing these cases with auto-generated tests, it would be an easy transition. I do think there will always be a place for example-based tests. Imagine trying to property test the implementation of a cryptographic hash function. Unless you had another implementation to compare it against (and even if you did, how would test that one?), you should not be able to associate the input and the output except by doing the work to compute the hash. Thus you cannot cover all cases using Property Testing. But, if you can generate the bulk of you're test cases using it, then mop up the rest with a few examples, it would be a big win.
    3
  50. TJ's content is the reason I abandoned vim and went neovim and converted my config to lua. Before that I never used lua, I knew it was embedded in many games and was supposed to be fast. I thought it was bad idea for neovim to split off from vim in this way and split the plugin eco system, because ppl will want their plugins to work for both vim and neovim right? (I was very wrong apparently). Then after seeing him explaining things using lua, it started to make sense and it just seemed so much more pleasant than vimscript. Now a few years later I've written a multiple thousands of lines of lua code, split over my config and a plugin or 2 (which only I and 2 colleagues use), to aid my workflow in neovim, and can't imagine ever have done all that in vimscript. Also the lua plugin ecosystem is very active, with multiple new plugins coming out every week. And the community is very active and imo very welcoming (not everyone agrees all the time tho).
    3