[herpderperator]

phpMyAdmin was (is?) such a great tool and really got me into SQL/MySQL over a decade ago. Not to mention the whole PHP stack was so fun to use and let you iterate quickly and just build stuff with an immediate feedback loop - just reload the page and your updated server-side code is executed.

[acomjean]

It’s still there and still very good. Our non profits web host has an install and it’s pretty good at browsing/ searching / dumping the tables.

Dbeaver is my stand alone app of choice. It’s Java based but has some nice features as well.

[Tostino]

It was the first tool I ever used when I was learning about how to manage a private lineage 2 server in like 2005. Had a MySQL backend and the tutorials I was following had me using phpMyAdmin. I remember fixing a performance problem by changing a setting that (I had no idea what the implications were at the time) got rid of durability entirely on a number of tables, and months later I had to restore from an earlier backup with data loss because of data corruption.

Your right though, the interface really wasn't too terrible. Was definitely better than what was available for Postgres even a few years later when I first had contact with that.

[Cthulhu_]

I'm surprised that we've had a number of new languages and advancements in the past ten years or so, but none that tried to fill the same space as PHP & co did... unless I missed it.

But then, I suppose PHP itself is good enough and the people using it never felt a need for anything new. Laravel solved the lack of application structure / design handrails, and Facebook solved or worked on the bigger issues around the language - typing and runtime performance.

[bojan]

Symfony is there as well, a framework fit for large enterprise applications, and it works surprisingly well.

Despite that, php has its limits, and it's important to know them, and the workarounds for most of them. What is also tricky is a total lack of support from Azure for example.