I’m trying to determine whether my office should branch out or change its primary web coding language. If so… to what. Hoping you’ll help me reduce my options.
We are using HTML and JavaScript with a CGI to access legacy data. We show and accept data and process it with our legacy system. Since things have worked well so far, we want to expand the amount of information we’ll accept and the general content of the site (example: enter applications, change data, display information).
I knew little about our language options (little, as in HTML and JavaScript). Y’all are my best hope. Please… share your opinions on web languages. What do you think I should check out?
Pretty pleeeze? ?
they are all open source[/quote]I've heard the terminology, but don't really understand. This is different from licensing, isn't it?
I believe Java's strength would be on the application side versus how strong PHP and Perl would match up. [/quote]I'm assuming menus, basic screen displays, and links are standard. We'll also have considerable validation, calculation, and rule checking on the forms. Is this what you mean by "application side"?
By application, I mean writing a program that has nothing to do with the net. Like using Java to create a text editor. Java can be used with web technologies, but it also works as creating nothing, but programs you use on your computer. Java as a server side language, aka JSP, is on the slower side compared to thing like Perl and PHP.[/quote]Java is clearly not the way I need or want to go. Thanks for explaining why, Spufi.
By two languages playing nice, do you mean PHP playing nice with Perl, or PHP playing nice with something like XML?[/quote]In the HTML forum I've seen threads that remark on using PHP with HTML. That's what I mean by playing nice. We can be working in one language, but bail temporarily to use the strengths of another.
By two languages playing nice, do you mean PHP playing nice with Perl, or PHP playing nice with something like XML?[/quote]Maybe I understand better what you were asking.... We are presently using HTML with JavaScript. We aren't going to throw those out, so anything we use will need to be HTML friendly. For example, you can embed PHP code in HTML code. Will this work with Perl, too?
Offhand I don't know how well JavaScript will directly work with PHP. The big reason being that JavaScript tends to run client side and PHP tends to runs server side.I think the full meaning of "server side" just sunk in. It's not just that it runs on the server, but it has to run [i]before[/i] the html page is displayed... not [i]while[/i] it's displayed. Right?
[/quote]
[i]Originally posted by moreta [/i]
[B]Otherwise, I'll concentrate on data options first (not the legacy side, but data to make our web programming easier and more efficient). SQL? XML?[/B][/QUOTE]
whatever your past programming experience is. - PeOfEo[/quote]That's a good rule, but this time there are more factors than my preference. That's why I wanted input from y'all (read that "desperately needed"). I want to go with things that will be best/easiest for my company to use, not necessarily easiest for [i]me[/i] to use.
You can use things called flat files, but I'm thinking in this day and age that using XML files would be better when you want to use a file. - Spufi[/quote]I'll check further into XML. Could use flat files... don't know best way to access with HTML as a base? Would rather not... (in this day and age) programmers might have to work harder to use flat files than XML.
If you do go for it and want a hand with it, let me know, im looking for challenges to make my knowledge of php grow. - TeenLife[/quote]Be careful what you offer... people may take you up on it.?
ASP.NET and PHP can do this, but what happens is the server side scripting will genorate the client side scripting. [/quote]?
Looks like it will have lots of information and some code I can check out, too. Thanks!http://www.phpbuilder.com/ [/quote]
0.1.9 — BETA 5.20