271–280 of 284 posts
Earlier quoted context omitted.
cPanel could probably included, it's nearly on all web hosts.
cPanel is Perl, not PHP.
Most newbie coders would start out coding their own blogs in PHP/Nodejs or Python on shared hosting, some web host use web framework as well.
I'm skeptical about the methodology here. The Stack Overflow Developer Survey [0] is my go-to source for this kind of thing, and it has very different results. Of course, it's measuring overall popularity while W3Techs is looking at "server side programming languages for websites." Here's how the ranks compare: Language W3Techs Stack Overflow PHP 1 11 ASP.NET 2 8 (C#) Ruby 3 17 Java 4 5 Scala 5 26 JavaScript 6 1 stat…
https://w3techs.com/technologies
https://w3techs.com/disclaimer
They are not measuring cron jobs, mobile apps, services, games, etc, all large sectors within the field of programming.
If we combine this survey with the Stack Overflow survey we can conclude that websites are built with PHP in the backend and with JavaScript in the frontend, nothing really chocking.
One problem with the Stack Overflow survey is that I'm not sure that the community of more esoteric languages like Erlang even uses Stack Overflow, I guess that is why it is at place 11 for W3Techs and 35 for Stack Overflow.
Earlier quoted context omitted.
That doesn't make the language less capable or less suitable. That's just an irregularity, causing an itch in certain people's heads. Personal preferences and obsessive-compulsive disorders don't make good arguments.
> Personal preferences and obsessive-compulsive disorders don't make good arguments. And yet here you are defending PHP and indeed claiming that 'A fractal of bad design' was "particularly popular with" people who haven't written any PHP. Your poor paste is also not a good argument. It was a completely terrible language and now it's merely mediocre. And yet, it has a particular niche because among other reasons lots…
Earlier quoted context omitted.
Classic. Absolutely fabulous when this happens. Just want to nuke everything to oblivion. But there is hope, sometimes it can be better to inherit badly written repetitive & copy-pasted code, rather than badly written abstractions. Badly written abstractions can be really hard to get out of years later because it tends to be viral all over the project, however when there are no abstractions at all, you can decide the…
There's no unwinding. Boss says it should be done like this just to finish tasks quickly. For the last couple weeks I've been thinking I should look for a new jobs as it looks there's no future here.
You start by setting up the standard router for all URLs when the php file doesn't exist. You then setup your router to answer somefile.php or whatever file you want. You then have that route execute your own class. You simply delete the original file and it now loads from your router. You can typically copy/paste the code from the file into a function in a class without any modifications. As you go you can get rid of includes / requires all over the place because now you've got auto loader configured so you can just call code from other files at will.
So then I just repeat this process. Sometimes it takes years but I can typically make a huge dent in most systems in the first few months.
If I don't get buy in I do it anyway for any code I'm asked to work on cause it makes the work better and there's no reason not to do it at that point.
I actually kind of envy you. I enjoy refactoring projects like that. You can typically bring that 4k line file you mentioned down to just a few classes and views.
I’d be interested in seeing this graph with Wordpress excluded
I think this shows how much HN is a bubble in itself. Most discussions here happen around new/exciting/cool/weird technology. And don't get me wrong, I love those discussions! That's why I come here! But reality outside of this bubble is people building and maintaining web apps as efficiently as possible and PHP hasn't stopped being very efficient. On the contrary, it's getting better with time. Interestingly enough,…
Yeah, but who knows how many of those are “ghost ships” that were built for local businesses over 5-10 years ago, were never touched since, never got security updates, and now load slowly because there’s a bitcoin miner churning away in a subprocess because they got hacked 2 years ago. To make a slightly problematic, somewhat poor taste analogy: 50% of the worlds houses (not a real stat, I’m lazy) have sheet metal ro…
Earlier quoted context omitted.
That doesn't make the language less capable or less suitable. That's just an irregularity, causing an itch in certain people's heads. Personal preferences and obsessive-compulsive disorders don't make good arguments.
> Personal preferences and obsessive-compulsive disorders don't make good arguments. And yet here you are defending PHP and indeed claiming that 'A fractal of bad design' was "particularly popular with" people who haven't written any PHP. Your poor paste is also not a good argument. It was a completely terrible language and now it's merely mediocre. And yet, it has a particular niche because among other reasons lots…
I claim so because the article was, and is. It's not me defending the language per se - I have no particular feelings or preferences for PHP - but just setting the record straight in the same way I'd reply to a false or incorrect statement on any other topic. I've seen more than enough unsubstantiated lamenting over PHP from people with little or no experience of the language. The article is more than anything else cited in blasé fashion by commenters who disappear after coughing up a link to the article, failing to follow up with actual solid arguments when asked why PHP would be incapable or unsuited for its tasks. I don't know what paste you are referring to. All of my comments are my own.
> It was a completely terrible language and now it's merely mediocre.
A terrible language is one that just can't get things done without irate jumping through hoops, but that's simply not the case of PHP. That's an objective fact, not a subjective opinion or feeling. While I don't use PHP much these days I still know the language very well, and on that technical and substantial merit I disagree.
Earlier quoted context omitted.
This is likely more accurate than the OP link. My experience is that Ruby jobs are less common but that they seem to pay far more.
This is why I recommend converting from Ruby to PHP. Costs are way lower and it's easier to find devs.
Earlier quoted context omitted.
> It's incredibly hard to find good PHP developers. But... is it much easier to find good devs in any other tech stack? I don't see it, personally. My ruby friends complain it's hard to find ruby devs at all, and harder to find good ones. I do see a lot of JS/node folks that get accepted as 'good', but when the rubber hits the road, the code is often still... meh - cut corners, SO copy/paste, etc. I see bad node and…
You don't see as much bad python code as you see bad PHP code. PHP has no entry barrier. You can just start typing and things start working. Compare that with deploying a hello word website in python, java or elixir.