Is there a robust programming language for web programming?

A famous PHP user once said: "In any case, after 2 years, a restart will occur.

Those days are gone. Web applications older than 5 years are common. With original developer (s).

The release cycles of the operating system, programming language and structure interfere with the actual work if you do not have a large staff.

Is there a way to develop something that does not require constant porting to the next level, without fear of losing support and support in the community? For people who want to stay in programming instead of climbing the corporate ladder and leaving problems for the next "generation"?

+7
programming-languages web
source share
11 answers

My company quotes are almost exclusively in C #, however we have ColdFusion 5 applications still recurring in 2001 or so. There is no need to transfer them.

If it does not break, do not correct it.

Besides the security flaws (which are usually handled by the OS / Server patch, so they don't need code changes), there is no need to change the application just because a new version of the language has appeared.

If I'm not mistaken, ColdFusion had at least 2 new releases, since we stopped using it for new code. but this did not affect our ColdFusion sites one bit.

+20
source share

Firstly, you can exaggerate the difficulties in maintaining web applications. In many cases, changes to the language or platform are expansive, not destructive .. NET, python, etc. A few years ago they will work, but new options are added to make these tools more powerful for future applications. The case when significant changes occur, as a rule, refers to the first or second iteration of the language, for example. Rails 1 - Rails 2.

Secondly, still active development of web programming is something grateful. This means that it is part of an industry that will remain productive and exciting for years to come.

+9
source share

Write CGI programs to FORTRAN 77. It should be pretty stable.

+8
source share

Traditional CGI is stable. It's not sexy, but if your OS continues to work with the same binaries or scripts, it will still work.

+6
source share

The only programming frameworks that remain stable are those that were left behind. Frames that stood long enough would not have support, say, AJAX or JSON, or even XML.

You are not going to find what you are asking for. The best you can hope for is a mature framework with good support like ASP.net or JSP. And, as @Neil N said, don’t continue upgrading if you don’t need a business business.

+6
source share

The first web programming I've ever done was to write Apache C modules that communicate with a dBase database. I am sure that the code will still work today (if the company I wrote still exists).

I use most modern web interface related programs in Perl, which is very stable and has an excellent reputation for backward compatibility. Most, if not all, code written for Perl 4 (released March 21, 1991) should still run on the latest stable Perl (5.10) - although you can update it anyway to take advantage of the latest 18-year improvements both in software development methods and language features.

+2
source share

Consider the shear layers . Previously, I worked for large aerospace companies, where the same source code and Fortran databases had their interfaces from the paper tape era, through the mainframe, client server, and Intranet websites.

From the outside, you will usually have CSS and XHTML templates that you can modify to re-skin the application. They change quite quickly in large organizations, as top management seems to decide that the bike shed should be of a different color every few weeks.

As a rule, you have some logic for combining templates with data from the internal block and redirecting user actions to the internal server. This should not change quickly, but put the presentation on calls in the background. Expect updates every few years and rewrite it every ten years. We have been using Java for this since the late 1990s. Some parts change faster than others, but this is not a big problem.

The content is usually stable (some of the aerodynamics codes dating back to the 1970s, the laws of physics do not change so often), and it will go to the web interface because it has all the other interface paradigms. Fortran forever.

+2
source share

Write your own web server in C, then you don't need to worry about the web programming language.

(No, this is not a serious answer)

+1
source share

Are you serious about what TDD, CI, pair programming and a robust, fast-paced infrastructure (basic version of Django or Rails) can offer you as a developer in relation to how you write and develop code? There are some really huge benefits that all of these parts offer to the development process, which makes it almost a joy to be a programmer. Of course, there are drawbacks, but all sides - support for happiness and ease of development for the engineer, which leads to greater productivity. In my book, that helmet escape wins. And the result of my productivity and happiness is solid products and excellent engineering.

YMMV, but if you have serious thoughts that you (and I take them very seriously), I think you should explore what these tools have to offer. Accepting the good and leaving the bad from a flexible religion plus some of the things that I listed above, I returned to find joy in programming again last year, after a good 5 years slide of my happiness with this career. It's about finding what works for you. I can only help and lead the way, showing you what worked for me. I would be more than happy to discuss in detail if you want to talk offline, I think this is a really important topic ... it makes me look at career changes many times.

0
source share

Java Servlets and JSPs have been used for a decade or so, and they still work just like they did in 1999. But honestly, can you imagine something more ugly than a web application of the 90s without any modifications since then?

0
source share

Python web framework web2py promises backward compatibility:

Always backward compatible. We have not broken backward compatibility since version 1.0 in 2007, and we promise not to break it in the future.

And supports Python versions 2.4 to 2.7

EDIT: Updated an important project 2 times and every time a problem arose. Well,...

EDIT 2: Now requires Python 2.6 - 2.7. No support for Python 3.

0
source share

All Articles