[ale] [EXTERNAL] Is PHP the easiest way to make a web application?

[Jon "maddog" Hall]

I remember when keeping the display layer separate from the business logic
was not taught in "Programming 101", and in many shops it still isn't
enforced.

Dr. John Donovan made a good sum of money showing IT executives how
projects that would take an estimated nine months by the executives own
staff could be done overnight (or even less) by Donovan's three programmers
using the equivalent of LAMP.

[I just read the Wikipedia entry on Dr. Donovan and his legal issues.  I
have no data about those other than what I read there.

All I know about Donovan is what I read from his early books and
experienced through his seminars.  While some of the performance that he
presented in his seminars could be explained through the magician's trick
of limiting possibilities, basically he was demonstrating to business
executives the power of LAMP.]

Of course there is the process of writing the initial code and the process
of verifying it and putting it into production.....and these were the days
of "waterfall" vs "agile" production.

Recently Michael Stonebraker (Ingres, PostGRES) has implemented a project
"DBOS" that takes this a step further.  Not for every type of processing,
DBOS is probably interesting for transaction processing.

md

On Thu, Jun 13, 2024, 09:41 DJPfulio--- via Ale <ale at ale.org> wrote:

> On 6/13/24 03:08, Steve Litt via Ale wrote:
> > Adrya Stembridge via Ale said on Wed, 5 Jun 2024 09:25:55 -0400
> >
> >> Thirding LAMP stack for simple and quick development project.
> >
> > Thanks Adrya,
> >
> > I'm guessing you mean [perl | python | ruby] CGI. I used to do that.
> > Trouble is, I needed to build every scaffold for every start tag and
> > end tag, and I needed to write all the sanitization code from scratch.
>
> Depends.
> Perl has a 'taint' mode and if you use DBIx for all DBMS access, then it
> handles all escaping to prevent nasty things.  Basically, you only need to
> specific valid inputs all others will be refused.
>
> As for tags - use Template::Toolkit.  It is more complex than just doing
> it manually, but it is 1000x more extensible and they've thought of
> everything you might want/need to do in the display layer.  Keeping the
> display layer separate from the business logic is programming 101 stuff.
>
> Or did I misinterpret everything?
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> https://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.ale.org/pipermail/ale/attachments/20240619/52836729/attachment.htm>