241–250 of 333 posts
Earlier quoted context omitted.
You can't have nginx and php in the same container?
Does not docker recommend a single process story? Nginx is typically a reverse proxy in front of an application server.
Earlier quoted context omitted.
PHP was the Visual Basic 6 for web. People without proper training and theoretical knowledge just went and did stuff.
I think this is a sound analogy. I certainly recognize myself in the person without proper training and theoretical knowledge that just went and did stuff. Of course I changed and so did my tooling.
I owe everything I have to Rasmus and his beautiful "shitty" language.
Earlier quoted context omitted.
> The language is very unplanned, go look at an equality chart for PHP, it makes JavaScript blush as well. This has been fixed in PHP 8. https://wiki.php.net/rfc/string_to_number_comparison
> make non-strict comparisons more useful and less error prone, by using a number comparison only if the string is actually numeric. Otherwise the number is converted into a string, and a string comparison is performed. That… makes it even worse.
Earlier quoted context omitted.
> make non-strict comparisons more useful and less error prone, by using a number comparison only if the string is actually numeric. Otherwise the number is converted into a string, and a string comparison is performed. That… makes it even worse.
why?
Earlier quoted context omitted.
I think you missed my main point: That people are different. I have not doubted that there are people who like the more rigid structure which the current maintainers push for. I actually mentioned that. But the success of PHP comes from the people who like PHP the way it was. Empowering them to write their own web projects with the least amount of code and bloat.
> But the success of PHP comes from the people who like PHP the way it was I'm sure that was the case for many years, but I believe the successful resurgence of modern PHP is coming from the people who want to see PHP actively improving . Not those who like PHP the way it was! PHP got a nasty reputation thanks to things like the "Fractal of Bad Design" site. Modern PHP has resolved (effectively) all of those early cr…
But people who build the future rarely use PHP now. Look at jobs at YC startups:
https://www.ycombinator.com/jobs
It is rare to see PHP mentione anywhere. It's mostly Python and JavaScript now.
Look at how lean Python's syntax is compared to PHP's new obsession with "public static function {}" insida a \namespace\which\is\not\needed\when\you\have\a\module\system tagged as "#[AllowDynamicProperties]". None of that is needed in Python:
https://www.online-python.com/Da8nQUlAEp
And look at how backward compatible JavaScript is. You still can run code from 20 years ago just fine.
The fractal of bad design post resonated with people who are paid to code. Who have to adhere to "best practices" and who don't mind spending time on bureaucracy. All makers I know just shrugged it off with "None of that get's in my way".
Earlier quoted context omitted.
StackOverflow has been trying to address that problem. I've recently seen them show a newer answer on top of the "accepted" answer even though it had fewer votes. This helps the answer evolve over time. https://meta.stackoverflow.com/questions/405302/introducing-...
But that’s not the problem. The problem is that the questions are old. It’s better to have the same question in a new era. The version info should be in the question. The question has either been answered or not, but it’s not relevant anymore for the original poster. Only if it really is, you could add a new major version to it to indicate compatibility
Questions are often timeless. The answers change and SO shows them all with their timestamps ordered by its best guess at which will help you, the reader, not the original poster.