2014-03-26, 03:10:51
Now you see why these are still in a file?
You just went from 1 to 2 features, both depending on a global refactor feature.
So now we need an advanced config also , see how quickly this becomes not "simple" ?
If you are doing this stuff on every install then use a custom gsconfig file with every install, that is the simplest solution, hell you can even write your own implementation using gsconfig to fetch stuff from an ini file if you wanted or server env variables in htaccess.
So do you want this feature or what I am working on now, making everything I can 10 times faster ?
The middle ground is "Which of these things are NECESSARY", ior precisly which gsconfig options need to be in settings, do they need to remain in gsconfig and settings ? Do somethings need to be overridable, do we need to keep this backward compatible? Some ?
You just went from 1 to 2 features, both depending on a global refactor feature.
So now we need an advanced config also , see how quickly this becomes not "simple" ?
If you are doing this stuff on every install then use a custom gsconfig file with every install, that is the simplest solution, hell you can even write your own implementation using gsconfig to fetch stuff from an ini file if you wanted or server env variables in htaccess.
So do you want this feature or what I am working on now, making everything I can 10 times faster ?
The middle ground is "Which of these things are NECESSARY", ior precisly which gsconfig options need to be in settings, do they need to remain in gsconfig and settings ? Do somethings need to be overridable, do we need to keep this backward compatible? Some ?