text stringlengths 0 1.17k |
|---|
**Jerod Santo:** He opened the issue about using GitHub's release notes... |
**Adam Stacoviak:** That's right, yeah. |
**Jerod Santo:** And he uses it for Lineman... We'll have him on next week. |
**Adam Stacoviak:** Yes, so we'll probably extend this conversation a little bit there, just because... So that's it for this week. Let's everybody say goodbye. |
**Jerod Santo:** See ya! |
**Olivier Lacan:** Goodbye! |
• Justin Saros' work on Lumen.js |
• Lumen.js as an alternative to monolithic Rails application development |
• Justification for the statement "JavaScript won't be a framework" |
• Lumen.js as a solution to alleviate problems with monolithic Rails app dev |
• Breaking down Rails responsibilities into build, application framework, and sensible defaults/conventions |
• Comparison between Ruby on Rails and Node.js for application development |
• Accidental creativity in open-source communities |
• Importance of sensible defaults and convention-driven design |
• Comparison of Ruby and Node.js ecosystems |
• Lineman as a tool for build tools, not a framework |
• Single responsibility principle in tool design |
• Integrating with front-end frameworks (e.g. Ember, Angular) |
• Avoiding code generation and promoting flexibility |
• Consultant perspective on choosing technologies for clients |
• Balancing traditional and rich JavaScript front-end development approaches |
• Client's system and needs are prioritized when working with them |
• Greenfield apps are built with consideration for user experience, budget, and business goals |
• Rich client applications may be necessary for certain applications, but can be more expensive to build and maintain |
• Simple, traditional web applications can serve companies well initially, but may become inefficient and unmaintainable over time |
• Agile development methodologies, such as one-week sprints, can lead to the "simple trap" where complexity is added in a monolithic, unstructured way |
• Breaking up a monolithic, complex application can be difficult and require significant rework |
• Discussion of the distribution of new projects, with 2/3 being "fat client" and 1/3 being "all back end" |
• Comparison of traditional Rails and JavaScript "fat client" projects, with a 50/50 split between the two |
• Explanation of the goal of Lineman, a JavaScript framework, to make "fat client" JavaScript web applications as easy to build as traditional server-side HTML web applications |
• Features and benefits of using Lineman, including rapid prototyping, consistency, and meta-plugins |
• Discussion of how to integrate Lineman with existing Rails applications, including proxying back to the Rails application and using a shared repository |
• Strategies for managing separate repositories for Lineman and Rails applications |
• The benefits of using PagerDuty for incident management and resolution |
• Comparison between Lineman and Yeoman as front-end project tools |
• Criticisms of Yeoman's approach to project setup and community-driven generators |
• Features of Lineman, including its table for comparing Lineman and Yeoman |
• Overview of Lineman's test runner, Testum, and its capabilities |
• Discussion of Lineman's testing story and its advantages over Yeoman. |
• Lyman's author mentions that Lyman's dependency management is limited, and it relies on a default configuration that "just works" |
• The author uses Lyman's helper directory to store their own test helpers, and suggests this may be beneficial to others |
• The author criticizes Yeoman's approach to dependency management, specifically Bauer, which is seen as a "fancy downloader" rather than a true dependency management tool |
• The author argues that Yeoman's approach encourages users to use Bauer as a dependency management tool, which can lead to issues with version conflicts and transitive dependencies |
• The author suggests that a better approach would be to write leaner, meaner applications that don't rely on a large number of JavaScript plugins |
• The author proposes that users should commit their vendor dependencies to ensure control over the application's dependencies |
• The author notes that Yeoman's approach to dependency management is "diametrically opposed" to their own, and that it's a matter of perspective and experience. |
• The importance of focusing on building an application quickly, rather than getting bogged down in engineering problems. |
• Critique of using Browserify, Require, and Bauer, as they introduce unnecessary complexity. |
• Discussion of Lineman.js, which is primarily written in CoffeeScript, but generates JavaScript output. |
• The author's preference for CoffeeScript, citing its benefits and maintainability. |
• Criticism of users who refuse to use Lineman.js due to its CoffeeScript basis, labeling it as a "straw man argument" and "entitlement". |
• Discussion of contributor feedback, with the author expressing frustration with users who open issues without offering to contribute or open a pull request. |
• The author's observation that the Ruby community is smaller and more homogeneous, whereas the JavaScript community is diverse and global. |
• Difficulty in managing and trusting open source dependencies |
• The "bozo button" concept for dealing with problematic open source contributors |
• The intersection of technical and social aspects of open source |
• Corporate backing of open source and its implications |
• The "social coding contract" and Justin's upcoming talk on the topic |
• The risks of relying on unmaintained or poorly maintained open source dependencies |
• The need for users to take greater responsibility in understanding their dependencies and their maintainers |
• The consequences of relying on a web of open source dependencies that may be insecure or unreliable |
• Open-source companies have a responsibility to give back to the community despite getting free value from open-source software |
• Maintaining open-source projects can lead to burnout due to the emotional toll of supporting users and dealing with issues |
• There is a need for a cultural shift in how users and maintainers interact, with users having a deeper understanding of open-source and contributing back |
• Demystifying open-source code can help users contribute and reduce burnout for maintainers |
• Both users and maintainers need to meet in the middle, with users having a deeper understanding of open-source and contributing back, and maintainers being more accessible and supportive. |
• The process of debugging and understanding code is becoming more accessible and encouraged for beginners |
• The increasing social nature of pull requests on platforms like GitHub is changing how people approach code and debugging |
• There is a need for better tools to help developers transition from using APIs and documentation to digging into code themselves |
• The languages Go and Rust may be easier to develop tools for due to their nature |
• The process of taking over an open-source project, specifically RSpec, can be complex and time-consuming |
• The importance of having a clear plan for maintenance and control in open-source projects to avoid control issues and encourage collaboration |
• Concerns about maintaining RSpec Given without sufficient resources or guidance |
• Comparison of RSpec Given to Jasmine Given |
• Inspiration from Jim Weirich's approach to open-source and community building |
• Tribute to Jim Weirich's impact on the Ruby community |
• Upcoming projects and availability for questions through Twitter or GitHub |
[0.00 --> 14.78] welcome back everyone this is the changelog and i'm your host adam stekowiak this is episode |
[14.78 --> 21.62] number 128 jared and i talked to justin saros about his work on lyman js building javascript |
[21.62 --> 27.64] apps and much more today's show is sponsored by code ship pager duty and harry's we'll tell you |
[27.64 --> 33.38] a bit more about pager duty and harry's later in the show but our friends at code ship they're rock |
[33.38 --> 38.72] solid hosted continuous deployment service that just works you can easily get set up with continuous |
[38.72 --> 43.92] integration for your app in just a few steps and automatically deploy when all your tests pass |
[43.92 --> 49.62] code ship has great support for lots of languages test frameworks as well as notification services |
[49.62 --> 55.06] they easily integrate with github or bitbucket and can deploy to cloud services like roku |
[55.06 --> 62.56] aws nojitsu google app engine and even your own servers setup is easy takes just three minutes |
[62.56 --> 68.68] get started today with their free plan and make sure you use our code the changelog podcast again |
[68.68 --> 75.10] that's the changelog podcast when you use that you're gonna get a 20 discount for three months |
[75.10 --> 82.60] on any plan you choose head to coach ship.io and tell them the changelog sent you and now on to the show |
[82.60 --> 89.74] welcome back everyone we got a fun show lineup today today is friday august 1st we're actually |
[89.74 --> 94.96] broadcasting this show in particular live on five by five we don't always broadcast live but today is |
[94.96 --> 99.96] it's just one of those days we got to broadcast live so um i'm adam stikowiak i'm joined by |
[99.96 --> 107.72] jared santo our managing editor so jared say hello hello hello and we also have our our guest today on |
[107.72 --> 113.14] the show justin serrells justin how are you i'm doing fantastically well thank you fantastically |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.