Opinion: A good language for a bug reporting web app?

[new_tolinux]

Hmmm, well I guess my next question then is how do you make the choice of programming languages when creating a game plan for project?

Is it just down to personal experience and knowledge?

Afaik: yes
I would write something in PHP with a MySQL backend because that's about the only "modern" thing I know.

Long time ago I did a lot of programming in various DOS languages, but beside my knowledge about database structures and some basic "start1-start2-finish2-finish1" rules of programming that's not of any use to me anymore. It's more of a problem because sometimes I know how to do it in those languages, but can't find a simple way to it in PHP. Most times that's also my lack of knowledge, because it happens very regular that I find a simple way to do it in PHP afterwards. Didn't follow any course about it, didn't have any proper education on it, only use the PHP-manual from PHP.net in CHM-format to find my way (beside Google ofcourse )

I'm thinking about starting another language beside PHP, but since I can do almost everything I need/want with PHP, it seems of no use. Beside that, I really don't know which one to pick. So I'll probably stick with PHP for the near future.

[harx1337]

Wouldn't any web application require something like PHP, at least for the server side that is.

For the client I have no idea.

This. You'll have little complex logic here so why go with anything more complex?

[mharv]

C or Assembly. Your application doesn't require garbage collection or a full suite of run-time diagnostics so these people recommending Python and PHP are not recommending the correct tool for the job.

For the client your only choice is JavaScript.

[r-senior]

I am intrigued by the suggestion of using assembler to write a web application. Could you expand on your reasoning?

Would you plug assembler modules into a web server like Apache? Or would you write everything, right down to sockets?

[mharv]

Sockets are already written by the kernel developers and the C libraries already provide useful interfaces so I would not rewrite anything.I would use existing libraries as much as possible (http://curl.haxx.se/libcurl/ and http://dev.mysql.com/doc/refman/5.0/en/c-api.html) the logic could be written in assembler though OR C since needing to port to another architecture is very unlikely and definitely will never be necessary (or even beneficial).

[r-senior]

Would you be able to use the libcurl and mysql APIs from assembler?

Are you saying that Python and PHP are only appropriate choices if there is an immediate need to create a cross-platform web application?

[mharv]

Yes you can link to any C library from assembler and the other way around (Both are also accessible from any other high level language implementation but NOT the other way around). I'm saying Python and PHP are only appropriate choices if there is an immediate need to create a cross-platform web application AND you don't know C or assembly yet.

C is shorthand for assembly (and there are some other differences) but it is not shorthand enough to outweigh familiarity, so I would personally consider them interchangeable because of their ability to link together and would use whichever one was freshest in my mind at the time.

[ofnuts]

Yes you can link to any C library from assembler and the other way around (Both are also accessible from any other high level language implementation but NOT the other way around). I'm saying Python and PHP are only appropriate choices if there is an immediate need to create a cross-platform web application AND you don't know C or assembly yet.

C is shorthand for assembly (and there are some other differences) but it is not shorthand enough to outweigh familiarity, so I would personally consider them interchangeable because of their ability to link together and would use whichever one was freshest in my mind at the time.

Python and PHP are appropriate choices when you look at developer's productivity. The Python programmer will be having a beer to celebrate a succesul delivery when you will still be struggling with memory allocation problems in that C routine that receives uploaded files.

[mharv]

"struggling with memory allocation problems". I guess I'm just smarter than you.

[lisati]

From the forum rules:

If a post is older than a year or so and hasn't had a new reply in that time, instead of replying to it, create a new thread. In the software world, a lot can change in a very short time, and doing things this way makes it more likely that you will find the best information. You may link to the original discussion in the new thread if you think it may be helpful.

This is a three-year-old thread that has somehow come back to life.......