Disney Open Source VS pathogen.vim

• Innovation and Creativity
  Open sourcing projects can lead to innovation through community contributions, enhancing and evolving tools and technologies with diverse insights.
• Community Engagement
  Engaging with a community of developers helps in building goodwill, fostering relationships, and encouraging collaboration across the industry.
• Cost Efficiency
  By leveraging the community's contributions, Disney may reduce development and maintenance costs for the projects they open-source.
• Talent Attraction
  Open-source initiatives can attract talented developers interested in contributing to visible and impactful projects, acting as a recruitment tool.
• Industry Influence
  By open-sourcing projects, Disney can set industry standards and influence the direction of certain technologies and practices.

Possible disadvantages

• Intellectual Property Risks
  Open sourcing code can lead to potential risks around intellectual property, as others might use or modify the code in ways that were not intended.
• Resource Allocation
  Maintaining open-source projects requires significant resources and commitment, which might divert attention from other internal priorities.
• Quality Control
  Ensuring the quality and security of open-source projects can be challenging due to the diverse contributions from external sources.
• Competitive Advantage
  There might be concerns about losing a competitive edge by exposing proprietary code to the public, which competitors could then use to their advantage.
• Community Management
  Managing a growing community around open-source projects can be complex, requiring effort in engagement, support, and governance.

• Ease of Use
  Pathogen.vim simplifies the management of Vim plugins by allowing users to easily install, update, and remove plugins without altering Vim's core files. It requires minimal configuration.
• Directory Structure
  It promotes a cleaner directory structure where each plugin resides in its own directory under .vim/bundle, making it easier to locate and manage individual plugins.
• Compatibility
  Being widely adopted and time-tested, pathogen.vim is compatible with a wide range of plugins. This ensures that users can confidently use popular Vim plugins alongside it.
• No Impact on Startup Time
  Pathogen.vim is lightweight, which means it doesn't significantly affect Vim's startup time, preserving Vim's reputation for speed and efficiency.

Possible disadvantages

• Limited Features
  Compared to modern plugin managers like vim-plug or Vundle, pathogen.vim offers limited features, lacking built-in update mechanisms for plugins or other advanced functionalities.
• Manual Management of Dependencies
  Pathogen.vim requires users to manually manage plugin dependencies and updates, which can become cumbersome when dealing with a large number of plugins.
• Exclusivity of Git for Installation
  Pathogen.vim relies heavily on Git for plugin installation, which might be a limitation for users who prefer or require alternative installation methods.

Tracking Disney Open Source since Mar 2021.

• Any Suggestions Apart from vscode for Terraform ?

  The person who mentored me the most when I was getting started with Terraform used VIM with pathogen but honestly this isn't a great idea unless you're really invested in a VIM workflow. Source: over 3 years ago

• Vim or Emacs?

  I am a bit confused. What has this anything to do with your original question? vim-pathogen is for Vim editor itself, not for PyCharm. I don't know much about MacOS, so not sure how to help. Did you try the installation steps at... Source: almost 4 years ago

• Usage of 'after/ftplugin' directory for filetype-specific configuration

  Back in the old(ish) days of Vim, usage of tpope/vim-pathogen to manipulate runtimepath was a popular way to install plugins. As it got update 9 days ago, it might be still used by some. Source: about 4 years ago

View more