I would say the learning curve for MySQL and PHP would be much higher than learning XQuery.
Whichever way you go, you'll still need to learn HTML, JavaScript, JQuery and other JS frameworks to build a pretty site.
-c
Chris Misztur | Engineer, Business Systems
1000 Allanson Rd, Mundelein, IL 60060 (Map)
Office +1 847 837-3729 | Cell +1 312 504-0681
www.macleanfoggcs.com
-----Original Message-----
From: e-letter [mailto:inpost at gmail.com]
Sent: Wednesday, December 11, 2013 10:12 AM
To: Misztur, Chris
Cc: Christian Grün; Liam Quin; talk at x-query.com
Subject: Re: [xquery-talk] xquery technology now ready?
On 11/12/2013, Misztur, Chris <CMisztur at macleanfogg.com> wrote:
> For me it is what fits right now and xquery fits perfectly.
>> Can you describe practical and cost effective?
>
A web host service provider has advertised a service less than US$ 2 per month, which features the range standard web host tools, in this case an sql database and web server script language
So being technology agnostic, whilst xquery and xml technologies are interesting per se for a novice who has negligible prior knowledge, learning sql and php would suffice for the personal objective, creating a simple web site where information in a database can be viewed in a web page. Xforms is a great concept, but if it doesn't work with opera, or firefox or another w3-compliant browser, its advantage is lost.
Excuse my ignorance of the web host market, but if it was possible for a customer to say to a US$ 2 supplier "please install [xquery web server software name] and I'll use your service", I'd sign up and be more likely to learn xquery. From what others have written so far, the market state now seems a bit pre-mature.
________________________________
The contents of this message may be privileged and confidential. Therefore, if this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author.
Please consider the environment before printing this e-mail