I don’t know if it’s due to over-exposure to programming memes but I certainly believed that no one was starting new PHP projects in 2023 (or 2020, or 2018, or 2012…). I was under the impression we only still discussed it at all because WordPress is still around.

Would a PHP evangelist like to disabuse me of my notions and make an argument for using PHP for projects such as Kbin in this day and age?

  • farizer
    2•2 years ago

    I know it sounds childish but PHP is lame as hell same as java. Rust or go would have definitely been a cooler choice. I mean PHP gets the job done, but still…

    • werni
      15•2 years ago

      Choosing a language for a project because it’s “cool” is so stupid

      • @aksdb@feddit.de
        1•2 years ago

        No it’s not. If I work one something in my free time / voluntarily, I want to have fun. I want to enjoy it. If PHP pisses me off but Rust thrills me, of course I choose Rust. That’s the freedom you have if you start a project. That there are more maintainers and even a bunch of contributors underlines that it was the right choice.

        • @ipkpjersi@lemmy.one
          3•2 years ago

          In a way though he’s right, picking a language because it is “cool” is the wrong reason to pick a language. You should be looking at other things like performance, scalability, security, functionality and see if those facets align with the requirements for your project.

          • @Hexorg@beehaw.orgM
            2•2 years ago

            When doing a project where those things matter - sure. But if it’s your hobby protect you can do anything

              • @Hexorg@beehaw.orgM
                2•2 years ago

                I think the challenge arises when your hobby project gets funding and thousands of people start using it… But at that point the codebase is likely locked into many previously made decisions. Locked in as in - it would take too much effort to change it.