To be charitable, yes — PHP has access to low-level system details like the file system, sockets, and processes.
> I know a person who wrote Linux X Desktop Environment using PHP. Worked for them.
However: (a) "Worked for them" is an anecdote, not evidence of comparative suitability; (b) Don't confuse possibility with empirical fitness for purpose. Virtually all decisions are relative to alternatives [1]; (c) Even PHP describes itself as only a "general purpose scripting programming language" [2].
Note that "scripting language" itself can hide important differences. PHP 8 introduced JIT compilation [3] which helps.
[1] In negotiation terms, your BATNA (Best Alternative to a Negotiated Agreement). When evaluating technologies, don't forget the human cost, so consider your BATSHIT: Best Alternative To Shackling Humans In Tedium (or whatever expansion you prefer).
'Member when a major crypto exchange, which had original been a market place for Magic the Gathering cards (so it was not a mountain named Gox), was hacked and everyone's crypto stolen because the owner had implemented his own SSH server in PHP?
Yeah I've used it for a long time but not for its commit graph feature, which still isn't as nice as Git Graph. Actually the main feature I used it for was "Compare working tree with <commit>" which gives you a nice "what have I changed overall" view but one where the files are editable still in the diff view.
If I understand that correctly, I think that can be accomplished in [name-redacted] by viewing the combined diff of your branch by selecting its commits, or selecting one branch tip then another to see the “interdiff”. If this is something else I’d be interested to add support though.
I used MacPorts back in the 00s and early 10s but switched to Homebrew when it came out because it was less hassle.
Wanted to give it another shot with my latest clean OS install, but wound up installing Homebrew again due to broken packages on MacPorts. Probably should’ve tried to contribute by fixing those packages but didn’t have the time or mental energy available at that point in time.
Installation is similar just a standard mac install.
apps are the same.
The only difference is that Homebrew gets confused if you install your code or another build in /usr/local oh and Homebrew forces you to use non standard permissions on /usr/local
Back when I switched, it wasn’t unusual for MacPorts packages to not compile for some reason or another, and at that point my skills in that realm were lacking which meant I had little ability to fix these issues, rendering its technical superiorities over Homebrew moot.
Homebrew was less hassle in that most of the time, it successfully installed things and when it didn’t, it was fixed in short order.
Since then I’ve become much more capable of diagnosing and fixing broken packages but it’s still not something I’d like to spend my time on if I can help it.
