# Deprecating Marvin

DevFeed: [Deprecating Marvin](<https://devfeed.tech/articles/deprecating-marvin-37262.md>)

Original publisher: [Read original article](<https://muffinman.io/blog/deprecating-marvin/>)

Author: Stanko

Published: 2020-09-16T00:00:00Z

Content type: opinion

Language: en

Sources: [Stanko Tadić](<https://devfeed.tech/sources/stanko-tadic.md>)

Topics: [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>), [React](<https://devfeed.tech/topics/react.md>), [repo](<https://devfeed.tech/topics/repo.md>), [maintenance](<https://devfeed.tech/topics/maintenance.md>)

Tags: [boilerplate](<https://devfeed.tech/tags/boilerplate.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [react](<https://devfeed.tech/tags/react.md>), [repo](<https://devfeed.tech/tags/repo.md>), [software](<https://devfeed.tech/tags/software.md>)

## AI overview

The author announces the deprecation of Marvin, a React project boilerplate created for personal needs that later became an internal project and was used by thousands of people. The repository will remain available, but further improvements and maintenance will stop because the evolving React ecosystem made maintaining a single boilerplate unproductive.

## Source excerpt

It is funny, I would never say I would be sad to deprecate a software project. Especially a project boilerplate. But I just merged the deprecation notice, and I do feel down a little. I created Marvin about four years ago for my own needs. Since then it grew, became internal project at Work&CoFun fact, our website is made on top of Marvin. and was used by thousands of people. Why? # When Marvin was created React landscape was looking a lot different than today. The ecosystem continues to relentlessly evolve and maintaining a single boilerplate to capture all these possibilities has become unproductive. The repo will stay available, but we are stopping further improvements and maintenance. Thank you! # A big thank you to everyone who used and supported Marvin!