Just moved from laravel/PHP to JS.

Now I find out their is PHP 8.

Everyone said this was going to be dead.

https://stitcher.io/blog/...

Looks like they're paralleling typescript now. Can't say it's a bad idea.

"x is dead" is utter bullshit 95% of the time

you better not believe that bs, everything will be used even in a little niche environment.

“Dead” was over exaggeration.

What I should have the trend was going towards js/node, hence it would be easier to find a job as JS developer.

Which turned out to be true in my areas but I still hate JS when PHP is much more powerful and has better frameworks, dependency managers and templating languages.

@katbreitin it's nothing personal, but this type of thinking (need job, what's "trendy", let's do that although I have no frigging clue about it) is one of the reasons programming sucks.

Some people become really invested in the job and learn it properly, others just slip from trend to trend, doing half assed shit and leaving their mess for others (nah I'm leaving, I won't bother, will do XY instead).

For me your statement proofs that you're exactly that type of programmer that just doesn't give a fuck.

I don't want to piss you off, rather to give you a non subtle hint about how such statements can lead to unemployment.

NodeJS doesn't work the same way than PHP, and it's the interest of it.

Now, if you want my opinion, a new version doesn't say if the language is appreciated or not.

There are definitely very opinionated lingering prejudice toward PHP based on the shortcomings of older versions, but it keeps being updated and keeps getting better. It's far from dead. I kind of understand why people would think PHP's time is long overdue, but tbh, I think that's more due to sucky devs not understanding it and making a mess courtesy of the very forgiving nature of the language and leaving someone else a hot mess to deal with, possibly.

@miksaraj
Most of us prefer to refer to them as "legitimate reasons to be wary."

@miksaraj Shortcomings of older versions aren't a problem; legacy solutions to those problems are. While those solutions are no longer needed in new versions, a large portion of PHP devs are older (pre-7.0) and used to doing things the old way, while "fresh" devs generally prefer other languages. On that note it's definitely going to take a while for the community to truly shift towards the "new" PHP, but even then the most widely-used projects and ecosystems (CMSs) simply won't truly do it, since it would be just too hard and drastic.

While I do like the direction PHP is heading, those changes break backwards compatibility every 3 - 5 years, so I'm not willing to use it for any long-lived project, because I'll end up with codebase no one will pay to upgrade to the next major version, but I (or someone else) will still have to constantly add new features to.