> some really ugly code sometimes, well ok, alot of times, but you shouldn't blame the
> language for code produced by someone better suited to flipping burgers.
Ahh. _That_ is why I hate java so much!
Or maybe it's because of the programming burger-men that 128 megs
of java memory is like 4 megs in any other case. Actually, CPU looks like
a similar function. cubed route of required CPU for java task == CPU
required to do the task in visual basic with lots of bloaty options.
I can't wait to see the next generation programming languages when
CPUs are all read in gHz dropping fractions, and all memory is super-fast,
solid state and nobody knows what a megabyte means anymore (as if they do
now). Who knows, maybe competition will drain out and standards will be
efficient and enforced.. once the aliens get here.
On Tue, 17 Sep 2002, Bob Crandell wrote:
> I was attracted to PHP because it reminds me of C. They both put the power of
> choice back in the hands of the programmer where it belongs. Yes, you end up with
> some really ugly code sometimes, well ok, alot of times, but you shouldn't blame the
> language for code produced by someone better suited to flipping burgers.
>
> $0.02 more.
>
> Jacob Meuser ([EMAIL PROTECTED]) wrote*:
> >
> >On Mon, Sep 16, 2002 at 07:38:16PM -0700, Bob Miller wrote:
> >> Bob Crandell wrote:
> >>
> >> > Larry, I'm crushed. Do I detect a bit of prejudice here? Please
> >> > tell me it isn't so.
> >>
> >> It isn't so.
> >>
> >> Larry isn't prejudiced, he's just accurately describing PHP.
> >
> >Granted, php will let a person write horrible code. One way
> >to minimize the ugliness is to use php.ini-recommended instead of
> >php.ini-dist as the php.ini.
> >
> >I really think Larry was talking more about postnuke in particular
> >than php in general, tho. I can't tell the difference in execution
> >time between a purely Apache http authentication and a php http
> >authentication, and none of the sites I've built with php look like
> >slashdot.
> >
> >Also, running a chrooted httpd with mod_php is much simpler than
> >with mod_perl or mod_python, as perl and python need to be able to
> >find their modules at will (a modularly built php loads it's modules
> >when httpd is started). One could use 'mount --bind' or mount_null
> >to put the modules into the chroot, but the point of a chroot is to
> >keep as much as possible out of reach. IOW, an attacker could
> >modify 'remounted' perl or python modules that would later get
> >executed outside of the chroot by unsuspecting users, possibly by
> >root. Other options include copying the modules into the chroot or
> >having two separate perl/python installations. Neither of these seem
> >to be very easy to manage.
> >
> >Just my $0.02.
> >
> >--
> ><[EMAIL PROTECTED]>
> >_______________________________________________
> >Eug-lug mailing list
> >[EMAIL PROTECTED]
> >http://mailman.efn.org/cgi-bin/listinfo/eug-lug
> >
> --
> Bob Crandell
> Assured Computing
> When you need to be sure.
> Voice 541-689-9159
> FAX 240-371-7237
> [EMAIL PROTECTED]
> www.assuredcomp.com
> Eugene, Or. 97402
>
>
> _______________________________________________
> Eug-lug mailing list
> [EMAIL PROTECTED]
> http://mailman.efn.org/cgi-bin/listinfo/eug-lug
>
_______________________________________________
Eug-lug mailing list
[EMAIL PROTECTED]
http://mailman.efn.org/cgi-bin/listinfo/eug-lug
