Finally someone understood precisely what PHP needs to evolve as a language for the next 35 years! #not
On Mon, Oct 26, 2015 at 8:26 AM, Joe Watkins <pthre...@pthreads.org> wrote: > This brightened up my Monday morning. > > Cheers > Joe > > On Mon, Oct 26, 2015 at 11:43 AM, Michael Kliewe <i...@phpgangsta.de> > wrote: > > > Hi Frank, > > > > On 26.10.2015 11:09, Frank Meier wrote: > > > Hi to all of you, > > > > > > first I want to apologize for may bad English, > > > > > No problem, it's good enough to understand you. > > > I write because I feel that that the way how you see your own product > PHP > > > is totally wrong. I do not mean with it that the construction of the > > > language is wrong. > > > > > > Your basic aproach is wrong. > > > > > > PHP is a server side programming language. That means that the most > work > > > what PHP have to do is to be the boss of the data servers and handle > the > > > data. > > > > > > Create database or tables or records, edit, delete and read and > write > > > them. > > Which database do you mean? MySQL, MSSQL, CouchDB, Redis.... > > > And where is your fantastic programming language so incredible lousy > that > > > me, I am since 35 years a database programmer, just shake my head??? > > > > > > Exact in this operations!!! > > > > > > I know that it is for free and I can not tell you how much I value your > > > work on it, but all of you, WAKE UP!!!! > > > > > > You sent the handling of records from modern handling via recordsets > back > > > to computer stone age. It is a torture to use PHP without tools (and > > they > > > are lousy too) for database operations. > > > > > > > > > I can give you a example: > > > > > > It is in PHP a lot of work to just read the next record in a table. > > > > > > With ADO is it just nextrecord(). > > With PDO it's > > $result = $sth->fetch(); > > > > http://php.net/manual/de/pdostatement.fetch.php > > > > I don't see that much of a difference... And PDO is built-in. > > > The PHP way is a insult to the modern world of programming. > > > > > > Maybe you should consider to write internal functions for the record > > > handling which do take all the sql waste of time away from the > > programmer > > > and create just short command words that the developer can use them. > > > > > > This would be a "small step for you but a huge leap for mankind!". > > > > > > And you would finally win the race in the language battle. > > > > > > I am sorry that I write it so harsh, but PHP is for me the definition > of > > > server data handling and exact there you fail in a big way. > > > > > > All the programmers around the world reinvent every time the wheel new? > > > > > > Have this really to be? > > > > > > In my opinion should exist commands like: > > > recordnew(table) > > > recordread(id, table) > > > recordwrite(id, table) > > > recorddelete(id, table) > > > recordprev(currentrecord, table) > > > recordnext(currentrecord, table) > > > > > > This is the minimum what I expect from a program language in the year > > 2015. > > Maybe you should have a look at PDO: > > http://php.net/manual/de/book.pdo.php > > > > Or other database abstraction layers out there, there are plenty. Search > > at packagist.org for example. > > Just to name a few that I heard of, but don't use myself: Doctrine, > > Propel, RedBeanPHP > > > I am database programmer for international police organizations. > > > > > > Please keep my name confident. > > > > > You are writing to a public mailing list, what do you expect? > > > > Michael > > > -- Guilherme Blanco MSN: guilhermebla...@hotmail.com GTalk: guilhermeblanco Toronto - ON/Canada
