Artwork

Contenu fourni par SmartLogic LLC. Tout le contenu du podcast, y compris les épisodes, les graphiques et les descriptions de podcast, est téléchargé et fourni directement par SmartLogic LLC ou son partenaire de plateforme de podcast. Si vous pensez que quelqu'un utilise votre œuvre protégée sans votre autorisation, vous pouvez suivre le processus décrit ici https://fr.player.fm/legal.
Player FM - Application Podcast
Mettez-vous hors ligne avec l'application Player FM !

Static Code Analysis in Elixir vs. Ruby with René Föhring & Marc-André Lafortune

46:02
 
Partager
 

Manage episode 389412709 series 2493466
Contenu fourni par SmartLogic LLC. Tout le contenu du podcast, y compris les épisodes, les graphiques et les descriptions de podcast, est téléchargé et fourni directement par SmartLogic LLC ou son partenaire de plateforme de podcast. Si vous pensez que quelqu'un utilise votre œuvre protégée sans votre autorisation, vous pouvez suivre le processus décrit ici https://fr.player.fm/legal.

In this episode of Elixir Wizards, hosts Owen and Dan are joined by René Föhring, creator of Credo for Elixir, and Marc-André LaFortune, head maintainer of the RuboCop AST library for Ruby. They compare static code analysis in Ruby versus Elixir.

The conversation explores the intricacies and challenges inherent in static code analysis across object-oriented and functional programming paradigms, highlighting the unique characteristics of both Ruby and Elixir. Key topics of discussion include the ways these tools can enhance coding styles and empower developers, the delicate balance between providing guidance and enforcing rules, and the evolving future of code analysis in these languages.

Topics discussed in this episode:

  • The differences and applications between static and dynamic analysis
  • How Credo aims to offer flexible and educational guidance for Elixir developers
  • The complexities of method identification in Ruby and its impact on static analysis
  • Challenges posed by macros and dynamic code modification during compilation in Elixir
  • Reducing false positives in code analysis tools to minimize developer frustration
  • Promoting uniform coding practices through analysis tools
  • The significance of using analysis tools with clear, specific objectives
  • How coding standards can refine and improve coding styles over time
  • Building analysis tools and checks through an understanding of Abstract Syntax Trees (ASTs)
  • Potential advancements in the analysis of Phoenix templates and HTML in Elixir
  • Contrasting approaches to managing code and comments in Elixir and Ruby ASTs
  • The fine line between providing helpful guidance and imposing stylistic preferences
  • Heuristics in static analysis highlight inconsistencies without mandating style
  • The potential for more straightforward pattern matching in ASTs with future updates
  • The importance of a gradual implementation of tool updates to maintain backward compatibility
  • Creating tools that support and empower developers, rather than hinder them
  • How static analysis contributes to cleaner, more maintainable codebases
  • Potential future developments in the field of static code analysis
  • Practical applications of using linters like Credo and RuboCop in software development

Links mentioned in this episode:

Credo https://github.com/rrrene/credo
https://hexdocs.pm/credo/overview.html
Dogma: A code style linter for Elixir https://github.com/lpil/dogma
https://github.com/rubocop/rubocop
RuboCop's AST extensions and NodePattern functionality https://github.com/rubocop/rubocop-ast
https://github.com/whitequark/parser
https://hex.pm/packages?search=credo&sort=recent_downloads
https://github.com/doorgan/sourceror
https://github.com/rrrene/credo/blob/master/lib/credo/check/readability/large_numbers.ex

Special Guests: Marc-André Lafortune and René Föhring.

  continue reading

182 episodes

Artwork
iconPartager
 
Manage episode 389412709 series 2493466
Contenu fourni par SmartLogic LLC. Tout le contenu du podcast, y compris les épisodes, les graphiques et les descriptions de podcast, est téléchargé et fourni directement par SmartLogic LLC ou son partenaire de plateforme de podcast. Si vous pensez que quelqu'un utilise votre œuvre protégée sans votre autorisation, vous pouvez suivre le processus décrit ici https://fr.player.fm/legal.

In this episode of Elixir Wizards, hosts Owen and Dan are joined by René Föhring, creator of Credo for Elixir, and Marc-André LaFortune, head maintainer of the RuboCop AST library for Ruby. They compare static code analysis in Ruby versus Elixir.

The conversation explores the intricacies and challenges inherent in static code analysis across object-oriented and functional programming paradigms, highlighting the unique characteristics of both Ruby and Elixir. Key topics of discussion include the ways these tools can enhance coding styles and empower developers, the delicate balance between providing guidance and enforcing rules, and the evolving future of code analysis in these languages.

Topics discussed in this episode:

  • The differences and applications between static and dynamic analysis
  • How Credo aims to offer flexible and educational guidance for Elixir developers
  • The complexities of method identification in Ruby and its impact on static analysis
  • Challenges posed by macros and dynamic code modification during compilation in Elixir
  • Reducing false positives in code analysis tools to minimize developer frustration
  • Promoting uniform coding practices through analysis tools
  • The significance of using analysis tools with clear, specific objectives
  • How coding standards can refine and improve coding styles over time
  • Building analysis tools and checks through an understanding of Abstract Syntax Trees (ASTs)
  • Potential advancements in the analysis of Phoenix templates and HTML in Elixir
  • Contrasting approaches to managing code and comments in Elixir and Ruby ASTs
  • The fine line between providing helpful guidance and imposing stylistic preferences
  • Heuristics in static analysis highlight inconsistencies without mandating style
  • The potential for more straightforward pattern matching in ASTs with future updates
  • The importance of a gradual implementation of tool updates to maintain backward compatibility
  • Creating tools that support and empower developers, rather than hinder them
  • How static analysis contributes to cleaner, more maintainable codebases
  • Potential future developments in the field of static code analysis
  • Practical applications of using linters like Credo and RuboCop in software development

Links mentioned in this episode:

Credo https://github.com/rrrene/credo
https://hexdocs.pm/credo/overview.html
Dogma: A code style linter for Elixir https://github.com/lpil/dogma
https://github.com/rubocop/rubocop
RuboCop's AST extensions and NodePattern functionality https://github.com/rubocop/rubocop-ast
https://github.com/whitequark/parser
https://hex.pm/packages?search=credo&sort=recent_downloads
https://github.com/doorgan/sourceror
https://github.com/rrrene/credo/blob/master/lib/credo/check/readability/large_numbers.ex

Special Guests: Marc-André Lafortune and René Föhring.

  continue reading

182 episodes

Semua episode

×
 
Loading …

Bienvenue sur Lecteur FM!

Lecteur FM recherche sur Internet des podcasts de haute qualité que vous pourrez apprécier dès maintenant. C'est la meilleure application de podcast et fonctionne sur Android, iPhone et le Web. Inscrivez-vous pour synchroniser les abonnements sur tous les appareils.

 

Guide de référence rapide