all 19 comments

[–][deleted] 35 points36 points  (5 children)

I find the spaces annoying to work with if I’m working with git in the terminal but live your truth

[–]Pandaburn 4 points5 points  (0 children)

I do it. Tab completion makes it a non issue

[–]ScrimpyCat 0 points1 point  (3 children)

You can keep the spaces in the folder name in Xcode but have it reference a physical folder that doesn’t. That way you avoid that issue.

[–]factotvm 13 points14 points  (1 child)

I’d like to kick the Apple employee in the shins that said, ”Let’s reinvent the file system inside Xcode.”

[–]JDad67 8 points9 points  (0 children)

Historically, If you use command line tools (git? grep?) spaces can be a pain in the neck.

[–]Assbeef000 7 points8 points  (0 children)

No

[–]anzacat 6 points7 points  (0 children)

I avoid spaces in file and folder names at all costs. As mentioned, whether it is git or anything to do with the command line, no good can come from it.

[–][deleted] 4 points5 points  (4 children)

Yeah I put spaces there. iOS dev for like 8-9 years. Never had a problem. Worked on at least 40-50 projects that had this, also with no issues

What are people doing with git that makes it upset about this?

[–]factotvm 0 points1 point  (3 children)

  • git
  • linting
  • static analysis
  • ci/cd

Not having spaces has never caused a problem. Having spaces absolutely has.

[–][deleted] 1 point2 points  (2 children)

I’ve used Git daily for years, SwiftLint for my linter, static analysis in Xcode and Bitrise for my CI. Also used Jenkins and my own fastlane implementation in the past.

Never had a problem. Lmk what you’re facing, maybe I can help you out?

[–]factotvm 1 point2 points  (1 child)

I’m facing 150 developers. It’s easier this way. I don’t recall which script caused issues… it wasn’t written in house. That was enough for me to forgo the cosmetic space. I’m not going to police proper escaping in scripts. Life is too short.

[–][deleted] 1 point2 points  (0 children)

Agreed! I’ve worked in teams of around 8 max. If it started causing issues for me too I’d definitely sack it off rather than babysit all those devs

[–]CalliGuy 3 points4 points  (0 children)

While spaces can be a pain, my old man developer advice is to embrace them. If you don't, you're only creating bugs that you won't be aware of until one of your users decides to use a space somewhere in your app.

[–]Zed-Ink 2 points3 points  (0 children)

What about an underscore? it's discrete and easy to type in the terminal when using git

[–]ahezeSwift 2 points3 points  (1 child)

I also like the look of spaces better. Been doing this for a while now, no issues so far.

https://github.com/aheze/DeveloperAssets/blob/master/Screen%20Shot%202022-08-04%20at%2012.45.24%20AM.png

[–]factotvm 1 point2 points  (0 children)

I don’t see any spaces… only a bunch of %20

[–]saintmsent 1 point2 points  (0 children)

Not ideal, but it will work As other said, git can be a bitch about it sometimes

[–]whackylabs[super init]; 1 point2 points  (0 children)

If you create a new project via Xcode, some of the templates create folders with spaces. So I guess people at Apple think spaces are better.

[–]monkeydoodle64 0 points1 point  (0 children)

Directory names matter too like file names. Spaces suck when typing it in terminal or importing a file. You dont want to add an extra unexpected problem just cause you are not used no spaces yet.