Too new

DaveK1

@DaveK said:
@FrostCat said:
@bridget99 said:
@MiffTheFox said:
Android's SDK has been TRWTF since 1.0 and each new version only made shit worse.

I've never had much trouble getting it to do what I want. Then again, I'm not the sort of person who has to have the latest version of everything, nor do I attempt stubborn, pointless crap like trying to install open source shit under "c: \Program Files." A lot of that stuff doesn't work too well if you're not willing to "go with the flow."

If only Unix filesystems supported spaces in file names since the 80s. Oh, wait!
If only Unix shells made random guesses about which spaces were word separators and which spaces were part of paths like cmd.exe and CreateProcess. Oh, wait!

If only...oh, wait, now you're just trolling.

So why are you taking me seriously then?! ;-p~

@FrostCat said:

Unix has always[1] had a way to tell the shell spaces aren't argument separators; it's called quoting. Windows has supported the same thing since it allowed spaces in filenames. Guess what, CreateProcess at all have ways to do the same thing, as you would know if you spent three seconds searching: http://stackoverflow.com/questions/4053241/windows-api-createprocess-path-with-space

Yes, I know all that, but people still manage to screw up despite that. On both platforms, as it happens.