Could a website be written in more than one language, if yes, whatcombination of languages do you recommend?

Java + PHP, Ruby+PHP, Ruby + C++, or what else?

..oO(Erwin Moller)

>Java + PHP, Ruby+PHP, Ruby + C++, or what else?

Of course you can write a website in a dozen different languages if you
want, each page in a different one if necessary. Why do you ask?

Micha

PS: As said before - please write your question in the message _body_.

On May 5, 7:43 pm, Erwin Moller <hi.steven...@gmail.com> wrote:
> Java + PHP, Ruby+PHP, Ruby + C++, or what else?

Languages generally have strong and weak points. It all depends on
what you wish to accomplish. From there you select the language(s)
that can help you meet those goals.

As an example say you are having a website report on real time data
collectin stats, you might want to write the data collection portion
in C as it is a faster language and have PHP grab the stats
periodically from the C component and report them, etc.

A great deal in good web sites is not the coding as much as the
planning, then after you have a good plan and idea, you look at how to
get there with the right code.

On May 6, 10:55 am, Michael Fesser <neti...@gmx.de> wrote:
> .oO(Erwin Moller)
>
> >Java + PHP, Ruby+PHP, Ruby + C++, or what else?
>
> Of course you can write a website in a dozen different languages if you
> want, each page in a different one if necessary. Why do you ask?
>
> Micha
>
> PS: As said before - please write your question in the message _body_.

Sorry, I will pay attention to it from now on.

Erwin Moller wrote:
> Java + PHP, Ruby+PHP, Ruby + C++, or what else?

You can also combine PHP with both Perl and Python.

best regards
Piotr N

Erwin Moller wrote:
> Java + PHP, Ruby+PHP, Ruby + C++, or what else?

C, Assembler, Fortran..perl, python, BASIC..anything that can produce a
stream of text to stdout in fact.

On Tue, 06 May 2008 10:24:04 +0100, The Natural Philosopher wrote:
> Erwin Moller wrote:
>> Java + PHP, Ruby+PHP, Ruby + C++, or what else?
>
> C, Assembler, Fortran..perl, python, BASIC..anything that can produce a
> stream of text to stdout in fact.

I did a small one in CGI Cobol once. (It was that or Fortran on that
machine....)

--
CS is about lofty design goals and algorithmic optimization. Sysadmining
is about cleaning up the fscking mess that results.

On Mon, 05 May 2008 19:43:11 -0700, Erwin Moller wrote:

> Java + PHP, Ruby+PHP, Ruby + C++, or what else?

A website can be written in every language the webserver and browser
support... but why would you want to do that?

--
0000001010011010 - The sixteen bit word of The Beast.
"May Darkness Consume You."


Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
http://www.usenet.com

> Java + PHP, Ruby+PHP, Ruby + C++, or what else?

Nice list of languages; there are more of course. What else what?

In our last episode,
<a3763bca-1843-406f-937a-67cd07945096@f24g2000prh.googlegroups.com>, the
lovely and talented Erwin Moller broadcast on comp.lang.php:

> Java + PHP, Ruby+PHP, Ruby + C++, or what else?

Anything that can write plain text to STDOUT can be used to make HTML
documents because HTML is just plain text. This would include sh and other
shells and a large number of commands --- nanoblogger, for example, is a
blog written in sh with various uniod commands. Perl is an obvious omission
in your list. And Python, I suppose. Lisp --- if you are nuts for
parentheses. Even --- heaven help us --- FORTAN or COBOL. A number of
editors can be called with the name of an initial macro to execute, so you
conceivably use editor macro languages (about as many as there are editors)
to generate a whole website. Since many of these can use system calls (such
as backticks) to get output from the others, you could use whatever your
server's cgi module recognizes to direct the whole process. If you just
want to generate static pages that fit together as a website, there are even
more possibilities.

Okay, some of these possiblities are only theoretical unless you are already
cutting out paper dolls in a room with cushy rubber walls. People who get
out without attendants in white coats will usually want something with a
prebuilt library interface to their favorite database, but some database
clients do sensible things when called in a stream context that would make a
roll-your-own database interface not quite so intimidating as it might
otherwise seem. Likewise many commands, like various calendar commands.

The main problem with unconventional approaches is lack of portability. Even
a monkey can write stuff that works on his own machine. What makes a
programmer is writing stuff that will work on many/most machines. Of
course, many of these languages *should* work the same on any machine with
any OS (with a compiler/interpreter installed), but in varying degrees, that
is not always entirely true.

--
Lars Eighner <http://larseighner.com/> usenet@larseighner.com
Countdown: 258 days to go.