3 ms·
I agree with a lot of your comment, but what's wrong according to you with php.ini? I've always found it a really handy way to customise the behaviour of my php
by aaviator42 3y ago
I agree with a lot of your comment, but what's wrong according to you with php.ini? I've always found it a really handy way to customise the behaviour of my php installs and apps, and I've actually learnt a fair bit from just reading through the comments and following the links it contains.
- endofreach 3y agoActually, i can't say what i would propose as a better way without having to spend some time thinking. While i was expanding on my php.ini mini-rant, i realized that i wouldn't be able to answer a question like yours. I just seem to be hater for no valid reason other than very personal things like: - hating the ini syntax - issues with module conflicts - how the overloading works Might be my experience of annoyances when i didn't know the issues might be related to php.ini settings. And (still today), i only find out after googling issues like a moron. I just have the feeling another solution might offer much better dev experience. But yeah, i can't offer any helpful insight here. Maybe it's just that i don't want to have to initialize at all, given that the PHP we talk about is not the one running on funny hardware, but rather purposefully configured servers anyway. But yeah, not sure what a better alternative would be right now without digging in to it.