text stringlengths 0 1.62k |
|---|
**Daniel Stenberg:** Oh, yeah. I actually just do that - stop, stay and consider all that; all those users, all those products, all those companies using it... Yeah, that feels really good. And as I said before, it's an ego boost, and of course, I contributed or even had a big part of that, and it's an awesome feeling.... |
**Adam Stacoviak:** You take a moment, enjoy it, and then you go back to work. At the end of your 17 year birthday post you were like "Have a beer with me, but only have one, because we've got work to do. There's bugs to take care of and tests to write." |
It's been an honor for me and Jerod to have you on this call. It definitely was great getting to know you and hear about all the things you're working on. For the listeners listening, we've got a couple shows coming up. We still have to schedule the Roots and Bedrock show, so if you're interested in WordPress and the B... |
**Jerod Santo:** We'll find out next week. |
**Adam Stacoviak:** Way off the path of curl, of course, but nonetheless, still a fun conversation. Daniel, is there anything else that you wanna cover before we taper off? |
**Daniel Stenberg:** I'm good. |
**Adam Stacoviak:** Anything else you wanna say to the audience? Where can they find you, where can they follow you... |
**Daniel Stenberg:** Well, everything I do and everything I play with is on my website, at daniel.haxx.se. And I am @bagder on Twitter. That's about it. |
**Adam Stacoviak:** Gotcha. We'll link that up in the show notes, so if you're listening to this, head to the show notes - changelog.com. That's right, changelog.com, not thechangelog.com. Jerod, we just changed from thechangelog.com to changelog.com. How cool is that? |
**Jerod Santo:** We've shed a few pounds. |
**Adam Stacoviak:** We did. Three characters... And we're https now too, so we're ready for the future. Totally secure. |
**Jerod Santo:** We're gonna get HTTP/2 rolled out... |
**Adam Stacoviak:** That's true. |
**Jerod Santo:** Maybe we can get Daniel offline to help us out with that. |
**Daniel Stenberg:** Any day soon, right? |
**Adam Stacoviak:** So for those wanting show notes to this show, it's changelog.com/153, because this is episode 153. Daniel, thank you so much for taking the time to talk to us. With that, everybody, let's say goodbye. |
**Daniel Stenberg:** Goodbye. |
**Adam Stacoviak:** Bye! |
**Jerod Santo:** See ya! |
• Introduction to the episode and guests |
• Sponsorships from Code Ship, Top Towel, and Code School |
• Explanation of the Ruby Heroes award and this year's winners |
• Interviews with each of the six Ruby Heroes: Nobuyoshi Nakata, Eileen Uchitelle, Sarah May, Zachary Scott, and two other guests (not mentioned by name) |
• Documentation and contributions in open source projects |
• Recognition of individuals who focus on behind-the-scenes work, such as patching and bug fixing |
• Jeremy Evans, creator of the Sequel library, and his experience with the Ruby Hero Award |
• Sam Saffron, creator of the Discourse platform, and his work on performance optimization and benchmarking tools |
• Mini profiler and other open-source tools for improving performance and productivity in Ruby development |
• The speaker praises Eileen for receiving an award and mentions her contribution to refactoring a difficult part of the Mini Profiler. |
• The speaker shares their own experience of working on a project that others had avoided, and how it can be demoralizing when someone else solves the problem just before you do. |
• The speaker suggests that having a public list of projects that need help can encourage others to contribute. |
• The speaker mentions a tool called Ccat and how it's not the first solution to a problem, but rather a rediscovery of an existing solution. |
• The speaker asks the group how many people know each other, either online or in person. |
• The speaker mentions that they've met Zach at conferences and that they both live in San Francisco. |
• The speaker talks about the Ruby Karaoke hashtag and how it brings people together to sing and have fun. |
• The speaker is involved in organizing a regional JavaScript conference and suggests having a karaoke session to break the ice and get people to know each other. |
• The group discusses the idea of having a karaoke session at the conference. |
• The group is asked to share their Ruby heroes, and several people mention Koichi and others. |
• Discussion of Ruby heroes, including Koichi, Greg Pollock, and Nobu |
• Ruby Hero award nominations for Koichi |
• Action Cable, a new feature in Rails 5 that adds native web socket support |
• Mruby, its potential for unique use cases, and development efforts |
• Performance improvements in Ruby 2.2, including GC changes and reduced memory usage |
• Discussion of symbol garbage collection and its implications for Ruby security |
• Area of Ruby that has the most "cobwebs" or needs the most love, with suggestions including Makefiles, the Ruby bug tracker, and tooling |
• Need for improvement in Ruby's tooling, specifically for Git and cross-platform support |
• Discussion of the challenges and difficulties in updating and improving Ruby's existing code and infrastructure |
• Difficulty with using GitHub due to concerns about dependence on a commercial service |
• Eric Wong, author of Git to SVN, is a Ruby maintainer and contributor who prefers Git but doesn't want to use GitHub |
• Discussion of finding a middle ground or alternative solution, such as self-hosted options like GitLab |
• Memory usage and optimization of Ruby web processes, including cutting down memory usage of Rails apps |
• Ruby and related libraries are bloated and consuming too much memory |
• The Mime Types library is particularly problematic, loading 20 megs of RAM |
• RubyGems introduces memory bloat into processes |
• A pull request has been submitted to reduce memory usage of the Mime Types library |
• Optimizing processes could lead to better Ruby adoption |
• The author is working to improve the Mime Types library and get it merged into RubyGems. |
• The mail gem has unnecessary dependencies and may be too verbose. |
• Conferences may be reaching a peak and need to evolve. |
• New formats and ideas are needed to make conferences more interesting. |
• Cross-pollination of technical boundaries could be beneficial, such as incorporating ideas from other languages and communities. |
• The speaker mentions their interest in attending more conferences, including cross-language conferences |
• The speaker likens Java to a lingua franca that binds different platforms together |
• The speaker mentions attending JS in the spring and notes that this may be an interesting idea for Ruby conferences |
• The speaker discusses the evolution of Ruby conferences, noting a change in the audience demographics |
• The speaker notes a significant increase in the number of attendees who are new to Rails or coming from large organizations |
• The speaker feels there is a mismatch between the audience and the speakers at conferences, with many speakers not being from the same "worlds" as the audience. |
• There has been a significant uptake in operations and performance-related talks, with Docker being a popular topic. |
• The speaker notes that there is a lack of talks on different languages and frameworks, such as Python or MVC frameworks. |
• The speaker also notes that conferences struggle to cater to both beginners and advanced attendees. |
• Making talks accessible and having a range of topics to suit different levels of expertise is seen as a challenge. |
• The speaker tries to explain complex topics in a way that is easy to understand, often by using examples from existing applications. |
• The speaker used an example of an active record talk to make the topic more relatable and understandable to the audience. |
• The speaker discusses the importance of using existing applications as examples to illustrate complex concepts. |
• The speaker mentions the topic of using Ruby on the browser via Opal, which is a library that transforms Ruby into JavaScript. |
• The speaker predicts that the Ruby community will be talking more about Opal and using Ruby on the browser in the future. |
• Discussing the benefits of using Opal, a Ruby compiler, to create JavaScript code that can run on both client and server sides |
• Mentioning the Vault framework, a real-time web framework built on top of Opal, and its integration with MongoDB |
• Jeremy's experience and involvement with Opal and Vault |
• Plans to integrate Opal into the web framework "Rota" to allow for writing Ruby code for both client and server sides |
• Jeremy's willingness to invest time and effort into long-term projects, such as Rota and SQL. |
• The future of the community and its growth |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.