@ginerjmMar 26.2019 — #Having no idea what you meant I did a little research (a little!). What I found was:
- most of the posts were over 10 years old. Hmmm....
- They stressed that the contents were rather limited. Not sure what that meant.
So - since I have a good handle on php I would say that it's a good investment in your career or whatever to learn the language. It ain't that hard, despite the complaints of a few posters here. Sure - SSI seems to be using a form of HTML and if you know that already you get away for free. But what did you gain?
BTW - what kind of code were you looking at as you stated in your question?
@NogDogMar 26.2019 — #It's never wrong to question implementation decisions. However, that doesn't mean I can affirm either approach is "better" in your case without a deep understanding of your requirements -- including potential _future_ requirements.
@tracknutApr 04.2019 — #I have a web site completely driven from a large volume of XML data (which should probably be a database, but I prefer the simplicity of just being able to edit it directly), and PHP to structure the pages. It's really a nice setup, to my mind, and is completely flexible in how I want to sort, select and display information. Can't imagine just doing it all with XSLT. So imo, yes it's worth it if that's the kind of thing you do. I'm not even sure how SSI is supposed to be an alternative, isn't it just a way to do an include?
@Mr_Initial_ManauthorApr 04.2019 — #@tracknut#1602504 That's the reason I use XML+PHP (though I did have an entire website based on XML+XSLT ages ago)
I used Server Side Includes back in the day simply because all I needed was to include header information and navigation menus. And honestly--basically, that's all I really need to do even now.
