Re: [Slashcode-general] Can I run slashcode via cgi-bin of an ISP?

[Joel K. <jkl...@ea...>]

At 10:20 AM 4/23/2001 -0400, you wrote:
>At 16:43 -0500 2001.04.20, Joel Kleppinger wrote:
> >Consider this the long way of saying, "You guys make a great product,
> >however, you have little foundation to stand on when someone complains
> >about it being difficult to install."  While it might be nice to have a CD
>
>If you don't already have mod_php compiled in to Apache properly, and don't
>already have the database server installed, then the PHP projects will be
>"difficult" too.
That's not the point.  No self-respecting shared (or even dedicated) web 
host isn't going to offer both mod_perl, mod_php, mysql and whatever 
else.  The difference is, for slash, you have to have recompile mod_perl 
and possibly/probably apache as well.  I know nothing I say or do will 
change that because I understand the reasons for it.  But don't shrug off 
recompilations by saying "well everyone has to do it." Stop thinking about 
this discussion in dedicated server terms, at least for my sake.


> >Even though I don't know much perl, I believe that what is holding slash
> >back from being easier to install is the fact that perl just doesn't come
> >with all of those modules installed.
>
>Nope.  Many of the things required here would be additional modules or code
>for PHP, too!  The same reasons why you  -- and pretty much everyone --
>admits that Slash is so much more powerful than PHP* are the same reasons
>why we have external modules required.
>
I don't remember saying slash was more powerful than PHP.  What I said was 
that slash was more powerful than any weblog currently written in PHP.  I 
hold to the opinion that pretty stinking good slash-type weblog can be 
created in PHP, if only enough quality effort would be thrown at it.  And I 
think it can be done while still offering PHP-level ease of installation 
(download, untar/gz, create the db, put the settings in a config 
file/script, and run the install script.  Viola.  takes about 20 minutes 
for the whole kit and caboodle... from nothing whatsoever to now working on 
customizing it).

I personally don't give a rip about some distribution that might have the 
right stuff already installed and configured for slash.  Practically no web 
host is going to use that distribution anyway.  Now if it gets into RedHat 
8.0, then we're talking.  Sure, I'd love it if more hosts used slack, deb, 
or whatever -real- distro <wink>, but they don't.  So what do I or other 
cheap shared-host users care?

My only point is to not misrepresent the situation of installing slash vs. 
installing anything else.  It's easy to make it sound like it's all 
basically the same when it's not.  As for saying that if a PHP 
slash-quality weblog would require the same sort of installation 
complexities as slash...  well, whatever.

Thanks for your time and ear,

Joel