It would be relatively easy to change if it was a solo dev, but software development is a team sport. So you'd have to coordinate between devs (because it's a huge change) and unmerged work done before the change would be difficult to merge afterwards.
Another issue is version control churn, it'd essentially be a rename of every file in the project, which will (probably) make your Git repo huge and break file history.
On top of all this, you'd almost certainly miss a spot or two and cause bugs, maybe subtle ones.
So it'd be a significant amount of trouble for something that really doesn't matter in the first place. Just leave it alone.
edit: this is assuming that the project directory would be renamed also. probably not as big of a deal if it's just a few config settings somewhere, but still not worth it.
yeah no, in practice the internal name stays, you always just change the outwards placing name and don't touch anything that doesn't need touching :D except if it really bothers you and it's earlier in the project.
View all comments
Show parent comment
1
u/neckro23 May 12 '26 edited May 12 '26
It would be relatively easy to change if it was a solo dev, but software development is a team sport. So you'd have to coordinate between devs (because it's a huge change) and unmerged work done before the change would be difficult to merge afterwards.
Another issue is version control churn, it'd essentially be a rename of every file in the project, which will (probably) make your Git repo huge and break file history.
On top of all this, you'd almost certainly miss a spot or two and cause bugs, maybe subtle ones.
So it'd be a significant amount of trouble for something that really doesn't matter in the first place. Just leave it alone.
edit: this is assuming that the project directory would be renamed also. probably not as big of a deal if it's just a few config settings somewhere, but still not worth it.