Der Marek

"c199c89db2159c554e7495df89b7d0d8157fe697805965f4a82ae15837fdec028c39dc2f1c9aa550b9cd49ef0a30cefd3ecbb3b8093c1ca174fa876c4fc0565e"

Last Notes

2025-02-06 18:09:32 GMT

- reply

@nprofile…rnwx Thank you for taking the time to answer. This is quite interesting to me, as I have encountered various diffuse perspectives—without having formed my own yet—on the use of 'interpreted' vs. 'compiled' languages.
Even though I am a computer scientist, I haven't worked much (if at all) with web technologies in the past ten years. However, I still remember that, back in the day (Typo3 era), I was often reluctant to use JavaScript-heavy frontends, as they tended to make parsing more difficult and, in my experience, worked against the principles of open and distributed data.
That’s why I’m so eager to understand the reasoning behind choosing PHP for this project. I've often heard people say that PHP is 'slow' because it's interpreted, while compiled languages like Ruby are supposedly faster—but I assume that's an oversimplification. I'm really interested in learning more about the actual trade-offs in federated web applications. What makes PHP a strong choice in this case?
No pressure to answer in detail—just curious, and if you have any good references on this topic, I’d love to check them out! 😀