JetBrains Survey Declares PHP Declining, Then Says It Isn't (theregister.com) 29
JetBrains released its annual State of the Developer Ecosystem survey in late October, drawing more than twenty-four thousand responses from programmers worldwide. The survey declared that PHP and Ruby are in "long term decline" based on usage trends tracked over five years. Shortly after publication, JetBrains posted a separate statement asserting that "PHP remains a stable, professional, and evolving ecosystem." The company offered no explanation for the apparent contradiction, The Register reports.
The survey's methodology involves weighting responses to account for bias toward JetBrains users and regional distribution factors. The company acknowledges some bias likely remains since its own customers are more inclined to respond. The survey also found that 85% of developers now use AI coding tools.
The survey's methodology involves weighting responses to account for bias toward JetBrains users and regional distribution factors. The company acknowledges some bias likely remains since its own customers are more inclined to respond. The survey also found that 85% of developers now use AI coding tools.
PHP not dying yet? (Score:1)
Last time I did PHP was in 2007. JS is so powerful now that it's all I need for webdev.
Re: (Score:2)
Last time I did PHP was in 2007. JS is so powerful now that it's all I need for webdev.
The gnarl toothed beast is still lurking around, but its mostly just used for hosting wordpress and throwing together templates and plugins for it. Theres still a bit of use of Laravel, but its paradoxically very much in the "burger flipper" category of least sought after and lowest paid jobs out there. Congrats for those graduating college with a coding qualification, you get to work on nonsense!
Honestly, I wish JS would go the same way. I hate working with the language, and web dev in general.
Re: (Score:2)
Yeah, that's exactly what I came here to post, well, basically. More precisely, I was going to post that the only way I could see php was going down in popularity is that the same developers segment with propensity to use php would use node, js and the likes.
Not for me anyway, I prefer using a "real" programming languages for anything above really small quick and dirty applications instead of interpreted scripting languages and I find it pays off in the long term. For quick and dirty, I simply use bash scri
Re: (Score:2)
You write web pages in bash scripts?
Re: (Score:2)
Sure, simple web pages work fine in bash scripts. Use http basic auth for simple status pages and you are good to go!
Re: (Score:1)
Gag, shoot 'em both!
Re: (Score:2)
Re: (Score:2)
And replace them with ... ?
Shell script. (awk is fine, too.)
Or compiled machine code if you need performance; but if you need performance, you aren't going to use PHP or JS anyway.
You want to know what's cool and hip?
JS is the new Perl: Nobody knows what it is good for, but the kids are using it for everything.
(Although they are calling it TypeScript these days, it's still JS, with all the cruft and remote code injection that comes with it.)
Re:And replace them with what? (Score:1)
For one, get away from C-based syntax, at least the ugly parts. Second, don't overload "+" for both concatenation and math (Js); that was bigly stupid. Third, give us optional named parameters. Anonymous objects are not a good substitute. Fourth, clean up name-space management instead of using a hacked-on "fix".
Example function declaration:
func myFunc(aa, bb:int, cc:num.required, dd:required, ee:int=7) {...}
This example is "semi-typed" as "aa" doesn't require a type (is not validated). "dd" doesn't require
Re: (Score:1)
Addendum
I'd prefer "req" over "required" as it would be used often: frequent tokens/idioms should be short. And "str" instead of "string".
One could put ranges and other decorations, perhaps custom ones:
var x:num.range(0, 99.99); // shorter version of above, strings don't need explicit types. // untyped, but treated as string by default // automatically "int" based on constant. // automatically num (decimal*)
var s:str.maxLen(12);
var s:maxLen(120);
var u;
var foo=7;
var fi=7.0;
(Variable declarations and paramete
Wordpress (Score:2)
I think WP is poop... but, here we are.
That seems correct to me (Score:5, Informative)
Re: (Score:3)
We have loads of PHP applications in use where I am that will need to remain in service for the forceable future, ...
Hopefully, you meant "foreseeable". :-)
Come on now (Score:4, Insightful)
Whatever camp you're currently in is the camp you will be in for a while. Nothing new has come along recently, and AI will only keep the status quo. It's Java, PHP, .NET, or something else from here on out.
Re: (Score:2)
Big PHP got to them (Score:2)
Re: (Score:2)
You're thinking of PCP.
Re: (Score:2)
Re: (Score:2)
At least it isn't Big Perl.
No kidding. Those guys are scary.
Re: (Score:2)
Re: (Score:2)
Re: PHP remains stable, professional, and evolving (Score:2)
100%
If you do not like reality, simply lie! (Score:2)
This seems just another instance of that.
41% are Gen Z?!?!? (Score:2)
So one of the slides says that 41% of the respondents are Gen Z.
None of Gen Z are using PHP, but they only make up about 30% of the workforce.
I use JetBrains PhpStorm, Rust Rover, and Rider (C#) every day, and I didn't even know about this survey. I'm a Milennial.
Manufactured drama? (Score:4)
Long term decline: user numbers are going down over the long term.
Stable, professional, evolving ecosystem: PHP is solid to build on, well managed, and evolutions are happening.
Maybe it's just me, but I don't see a conflict between the two statements?
Professional? (Score:1)
Re:Professional? (Score:5, Insightful)