3 ms·

Php & WordPress were fun. With that ugly php tag you could get pretty much everything working on the web. All you had to do was edit, save & refresh. No rebuil

Php & WordPress were fun. With that ugly php tag you could get pretty much everything working on the web. All you had to do was edit, save & refresh. No rebuild of code, server restart, compiling Just edit & save. Did it have the tendency to get ugly? Sure. But it was easy, quick and fast. Not every blog and needs a git flow, united, e2e, type-safe double encrypted dev environment. Both PHP & WordPress got shamed for their dirty nature so much that they are in identity crisis. PHP tries to mimmick Java as much as possible. WordPress plugin structure is a disaster. Having to run an entire npm project for every plugin, no easy data saving helpers, etc. Let alone the ux-disaster of the block Editor. Feels like the php decade is truly over. And it was php that killed itself. Laravel is a joy btw.

8n4vidtmkvmk 3y ago
Laravel is not a joy. It moved everything in the wrong direction by adding a ton of magic (which murders IDEs) and a ton of version churn.
redox99 3y ago
> All you had to do was edit, save & refresh. No rebuild of code, server restart, compiling Just edit & save. The majority of webdev is either exactly like that, or effectively like that with very fast rebuilds/restarts. It's not really something unique to PHP. In fact in your modern stack you'd probably have autosave, and most importantly "fast refresh", so you don't need to manually refresh and you don't lose state.
- wouldbecouldbe 3y ago
  Nah you don't yet it. Nowadays there is so much build config you need 4gb just to run wepback. Php is just a save of a file. That's it's. So for instance we would use remote file save. Edit & save via ftp. Most editors have such a plugin. Then you could work remote easily. But also hosting php is 10 times easier and stable then node. Php servers don't run stale or crash. Because there is no server.

8n4vidtmkvmk 3y ago

Laravel is not a joy. It moved everything in the wrong direction by adding a ton of magic (which murders IDEs) and a ton of version churn.

redox99 3y ago

> All you had to do was edit, save & refresh. No rebuild of code, server restart, compiling Just edit & save. The majority of webdev is either exactly like that, or effectively like that with very fast rebuilds/restarts. It's not really something unique to PHP. In fact in your modern stack you'd probably have autosave, and most importantly "fast refresh", so you don't need to manually refresh and you don't lose state.

wouldbecouldbe 3y ago
Nah you don't yet it. Nowadays there is so much build config you need 4gb just to run wepback. Php is just a save of a file. That's it's. So for instance we would use remote file save. Edit & save via ftp. Most editors have such a plugin. Then you could work remote easily. But also hosting php is 10 times easier and stable then node. Php servers don't run stale or crash. Because there is no server.