<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
<br>Hi Niels<div>I agree with you, even though I have no experience. </div><div><br></div><div>But I'm restricted by hosting options for Zope at the moment, and will revert to Python once the project is deployed - and when I figure out whether mySQL is good enough or not. I hate having to type all those extra characters in php though.</div><div>sareesh<br><br><br><div>> From: nd@syndicat.com<br>> To: aysand@hotmail.com; zope@zope.org<br>> Subject: Re: [Zope] Help in deciding approach to Web App<br>> Date: Mon, 5 Dec 2011 11:25:18 +0100<br>> <br>> Am Sonntag, 4. Dezember 2011, 16:15:13 schrieben Sie:<br>> > As you mentioned, if I have to use mySQL, isn't it better for me to go with<br>> > PHP+mySQL - easier to learn and deploy?<br>> <br>> ...just from my experience:<br>> <br>> PHP is - for different, but mainly technical/historical reasons - very widely <br>> spread within web applications, one major reason was/is i.e. the large <br>> (because "easy") availability on low cost hosting environments in the past - <br>> but the most advantages was/are on the side of the hosting providers....<br>> <br>> PHP might be easier to learn then other languages or frameworks, but <br>> maintaining large / complex applications / software projects within PHP could <br>> be a real mess.<br>> <br>> We develop nearly any web application with Zope / ZODB since >= 10 years but <br>> are a hosting company byself - so we was not bound to PHP as many other <br>> internet hosting users in the past. A colleagues company produces very high <br>> level expert systems on Perl and Catalyst - requiring high skilled Perl <br>> programmers.<br>> <br>> From my experience developing within Zope / ZODB (with Python, DTML and/or <br>> ZPT) allows very high quality products within very short timeframes and even <br>> further maintaining the project is relative ressource efficient - especially <br>> compared to PHP.<br>> <br>> Most web application data structures (i.e. a "simple" web page) fit's much <br>> better by a oo object strategy then a relational (RDBMS) one. <br>> <br>> The major typical ressource hole within typical PHP+SQL web applications or <br>> i.e. a CMS solution is the translation of typical data objects into tables and <br>> vice versa. Producing i.e. one "simple" CMS page within a PHP-SQL CMS easily <br>> could trigger hundreds of SQL requests into many different tables - a <br>> significant overhead which has to implemented by developers and handled by the <br>> machines.<br>> <br>> But this is my view onto the issue - just my two cents...<br>> <br>> <br>> <br>> cheers,<br>> <br>> <br>> Niels.<br>> <br>> -- <br>> ---<br>> Niels Dettenbach<br>> Syndicat IT&Internet<br>> http://www.syndicat.com/<br></div></div> </div></body>
</html>