undefined | Better HN

0 pointsinterstice1y ago0 comments

To be fair I’ve had similar issues with Rails

0 comments

thibaut_barrere1y ago

In that regard, my experience has been the following churn scale:

JavaScript churns more than Rails which churns more than Elixir/Phoenix.

I believe this is caused by “how sound the fundamentals are” (technical debt in the language itself and its stdlib).

creshal1y ago

PHP devs meanwhile: You guys churn?

For better or worse, you can take 10+ years old PHP code and it'll mostly just work.

rjh291y ago

I wrote a bookmark manager in 2005-ish using security-conscious PHP, and it still works great.

I rewrote it in React for fun and not only is it totally out of date, but Github's dependabot has sent me probably 200+ security advisories based on its dependencies.

lakomen1y ago

My handcrafted legacy.c64g.com site made in 2005 still works with php8.3 (I see I have to renew the cert). I just had to switch from mysql to mysqli. However my Symfony sites had to be rewritten. Friends don't let friends code using Symfony. There was no upgrade path. Deprecated components with no replacement. I was so fed up with all the bullshit from 2010-2013 with the OO fetishism the "treat PHP like it's Java" from fresh students and graduates that I had to abandon it and switch to Go, which gave me peace of mind and a factor 100 performance boost.

kalleboo1y ago

I maintain a PHP codebase that dates back 15 years and I can count the breaking changes on one hand, and they were all tiny one-line changes

thibaut_barrere1y ago

The backward incompatibility story https://www.php.net/manual/en/migration70.incompatible.php is not empty

2 more replies

j / k navigate · click thread line to collapse

0 comments

thibaut_barrere1y ago

In that regard, my experience has been the following churn scale:

JavaScript churns more than Rails which churns more than Elixir/Phoenix.

I believe this is caused by “how sound the fundamentals are” (technical debt in the language itself and its stdlib).

creshal1y ago

PHP devs meanwhile: You guys churn?

For better or worse, you can take 10+ years old PHP code and it'll mostly just work.

rjh291y ago

I wrote a bookmark manager in 2005-ish using security-conscious PHP, and it still works great.

I rewrote it in React for fun and not only is it totally out of date, but Github's dependabot has sent me probably 200+ security advisories based on its dependencies.

lakomen1y ago

kalleboo1y ago

I maintain a PHP codebase that dates back 15 years and I can count the breaking changes on one hand, and they were all tiny one-line changes

thibaut_barrere1y ago

The backward incompatibility story https://www.php.net/manual/en/migration70.incompatible.php is not empty

2 more replies

j / k navigate · click thread line to collapse