Clever Geek Handbook

Does the choice of language use who will use the application, especially in terms of web applications?

I think this mostly applies to web applications as you often see things like language and database vendor in relation to web applications, but not so much on desktop applications.

If a web application is built using the X language, this could have a noticeable impact on who deploys the application? For example, can a company using .NET products use a Python application that suits their needs, or can they find a .NET product that they can use?

EDIT 1: Clarified the question to refer to applications intended to be deployed and not just used.

0


source to share


5 answers


I'm assuming you are talking about companies that buy and deploy web applications in their organizations. If you're only talking about using external applications, I don't think they notice or care.

I think this is very subjective, but from my past experience, companies tend to come with technologies that they have already installed and working with. They tend to do this for several reasons.



  • The new application will require fewer changes to the existing infrastructure (e.g. running PHP on IIS)
  • Interacting with existing apps will probably be easier
  • They probably already have their own experience to support whatever language / server / db etc they are currently working on.
  • Their IT pros may already have formed prejudices against other languages ​​/ OS / db

Every time I've been about to evaluate web applications in the past, I've limited my search to technologies we've already used.

+2


source


It depends on how much customization and integration is required - and whether the application provides any sane API.

For example, you may need the following types of customization:



  • User authentication through the module; platform can be important
  • Create your own reports; the database is likely to be important.
  • Act against a web service that is part of an application; protocol (SOAP, REST, custom, etc.) will probably be important, but not the implementation language.

Also, there is a support and maintenance issue - Windows ISV will most likely support IIS better than Apache, for example, and vice versa. It also helps if you already have servers that have the required operating system installed ...

+1


source


I don't think most companies will even know what you were talking about, especially for web applications. I write these things for life, and even I don't know which platforms my favorite sites are using. I don't even know how SO works, for that matter.

+1


source


Not unless your choice of language has a clear effect on functionality. Ideally it won't.

Two examples: jEdit is a great program, but its Java roots really support it. The default is Java GUI look and feel (swing?). It's also very slow (although Java programs don't have to be slow, this is one of them).

On the other hand, the Stack Overflow website is based on .NET - but what does that mean? This has little effect on the functionality of the site.

0


source


It would be interesting to experiment with building an application (for example ASP.NET), then modify it a bit, put it on a different web server and rewrite the extensions (from .aspx to .py or .php) and see which ends up being more popular ...

0


source






More articles:


All Articles