It has a very mature web dev ecosystem around Rails. It: is quick-to-learn, is OO to the bone, is FP where is fits with the OO, is easy to read, has little quirks.
Personally I'd go with something with stronger types, no "null" and proper sum types. But if you are cool with dynamic typing: Ruby is a great choice.
> Elixir
Ruby-like syntax (some advantages just mentioned) and BEAM runtime. Yields very scalable apps.
I do thing GP raises a valid concern. PHP is not for new apps, or even better put: for new teams. It's just too quirky and does not have the native browser support the other super popular + super quirky language JavaScript has.
As as a comparison: who'd start an app in Perl these days? Or COBOL?
At some point a language may be considered "legacy".
> is quick-to-learn, is OO to the bone, is FP where is fits with the OO, is easy to read, has little quirks.
Exactly same applies to PHP - without FP part but in exchange one is getting enormous, gargantuan ecosystem of libraries, developers, hosting, language oriented and designed to rapidly deliver result and easiest deployments out there.
Todays PHP is good, may be not trendy and hip right now, elitists may snark a bit but it's good language to deliver products.
Full of quirks (there's a whole subreddit for that /r/lolphp), not OO to the bone (more like tagged on), hellish to read, no proper FP stuff.
You may call people categorizing PHP as legacy "elitist", but big shops that use a lot of PHP are heavily investing in other tech (yes I look at FB).
> it's good language to deliver products.
Never said it was not. But it is not, anno 2021, a good language to start a new project in. Not as bad as Perl and COBOL, but still legacy.
It seems you have identified a lot with that language, and I see this often. Usually this happens to people who have little experience with other languages. The defend it like it is their home.
> It seems you have identified a lot with that language, and I see this often. Usually this happens to people who have little experience with other languages. The defend it like it is their home.
My take on this topic comes from extremely pragmatic and focused on results angle: delivering product. Not sure what about 2 sentences I wrote allows you to make broad assumptions about my experience, I don't feel need or desire do describe it here but it's not only my own opinion [0]
I think that Reddit "lolcontent" could be not good metric to use when deciding what should be used for building software.
> Not sure what about 2 sentences I wrote allows you to make broad assumptions about my experience
That you defend PHP like it is your home. We can deliver a product in Perl, but it's a bad choice these days. Unless... someone is reaaaaly well acquainted with Perl and little else.
Hence I suspect that's whats going on here. As I've seen this happen many times before, also outside of programming.
> allows you to make broad assumptions
I voiced my suspicion based on your defensiveness. That's all.
It has a very mature web dev ecosystem around Rails. It: is quick-to-learn, is OO to the bone, is FP where is fits with the OO, is easy to read, has little quirks.
Personally I'd go with something with stronger types, no "null" and proper sum types. But if you are cool with dynamic typing: Ruby is a great choice.
> Elixir
Ruby-like syntax (some advantages just mentioned) and BEAM runtime. Yields very scalable apps.
I do thing GP raises a valid concern. PHP is not for new apps, or even better put: for new teams. It's just too quirky and does not have the native browser support the other super popular + super quirky language JavaScript has.
As as a comparison: who'd start an app in Perl these days? Or COBOL?
At some point a language may be considered "legacy".