The popular Material Theme extension for Visual Studio Code has been removed from the marketplace due to unresolved trademark issues with Google concerning the "Material Design" name. The developers were requested by Google to rename the theme and all related assets, but after attempting to comply, they encountered further complications. Unable to reach a satisfactory agreement, they've decided to unpublish the extension for the time being. Existing users with the theme already installed will retain it, but it will no longer receive updates or be available for new installs through the marketplace. The developers are still exploring options for the theme's future, including potentially republishing under a different name.
The Material Theme extension for Visual Studio Code, a popular theme providing a Material Design-inspired visual overhaul for the code editor, has been unexpectedly removed from the Visual Studio Code Marketplace. This removal appears to stem from a rejection by the Marketplace review team due to alleged trademark violations related to the use of the "Material Theme" name and associated iconography. The extension's developers, seemingly surprised by this action, are actively investigating the specific reasons for the rejection and working to resolve the issue with Microsoft. While the precise details of the trademark infringement claims remain unclear, the developers suspect it revolves around the usage of the term "Material" and a diamond-shaped icon, both potentially infringing upon Google's Material Design trademarks. Consequently, the Material Theme extension is currently unavailable for installation directly through the VS Code Marketplace, disrupting the workflow for numerous users who rely on the theme. The developers are exploring alternative solutions, including renaming the extension and altering its iconography to comply with marketplace guidelines, aiming to restore availability as quickly as possible. In the interim, users who already have the theme installed will retain its functionality, and the developers are providing instructions for manual installation from the project's GitHub repository for those who wish to install it on new VS Code instances or update to newer versions. The situation remains fluid, and the developers are committed to communicating updates regarding their progress in resolving the issue and returning the Material Theme extension to the VS Code Marketplace.
Summary of Comments ( 224 )
https://news.ycombinator.com/item?id=43178831
Hacker News users discuss the removal of the popular Material Theme extension from the VS Code marketplace, speculating on the reasons. Several suspect the developer's frustration with Microsoft's handling of extension updates and their increasingly strict review process. Some suggest the theme's complexity and reliance on numerous dependencies might have contributed to difficulties adhering to new guidelines. Others express disappointment at the removal, praising the theme's aesthetics and customizability, while a few propose alternative themes. The lack of official communication from the developer leaves much of the situation unclear, but the consensus seems to be that the increasingly stringent marketplace rules likely played a role. A few comments also mention potential copyright issues related to bundled icon fonts.
The Hacker News post titled "Material Theme has been pulled from VS Code's marketplace" sparked a discussion with several comments expressing concern and speculation about the removal of the popular theme.
Many commenters lamented the theme's disappearance, highlighting its popularity and expressing disappointment with its sudden removal. Some users voiced frustration with the lack of clear communication about the reason for the removal, leading to speculation about potential causes. Several users questioned whether the removal was due to licensing issues, potential malware, or a dispute with the theme's developer. The lack of official information fuelled the uncertainty and frustration.
Several commenters recommended alternative themes, with Night Owl, One Dark Pro, and Dracula mentioned as popular choices. This suggested that users were actively seeking replacements for Material Theme and the discussion became a platform for sharing alternative options.
A significant part of the discussion revolved around the importance of open-sourcing themes. Commenters advocated for forking the Material Theme and hosting it on open platforms to prevent similar situations in the future. This highlighted the community's desire for greater control and access to popular tools and resources. The incident seemed to have spurred a renewed interest in open-source alternatives and community-driven development.
Some commenters delved into the technical aspects of theme development, discussing the relative simplicity of creating and maintaining VS Code themes. This suggests that the community perceived the removal of Material Theme as a preventable issue, potentially caused by negligence or miscommunication rather than insurmountable technical challenges.
While the exact reason for Material Theme's removal remained unclear within the comments, the discussion revealed the theme's significant user base and sparked a broader conversation about the importance of open-sourcing, community involvement, and clear communication regarding the availability and maintenance of popular development tools. The frustration voiced by many commenters underscored the impact of such removals on developer workflows and the community's desire for more transparency and control over their tools.