Member Avatar for Sam367

Hello everybody! I'm thinking about creating a website using either of these listed different languages such as PHP, ASP.NET, JSP, RUBY(i don't know this one), COLDFUSION(same with ruby), etc. I created a personal website of my own as part of my college project last 2 years using Dreamweaver. I only had a knowledge and background with DW, other than that, no more else. Which one should i spend my time focusing and start learning other website languages?

I have a little bit background as well with sofware development but i'm more of interested with developing/designing websites.

Thanks in advance.

  • 3 Contributors
  • 6 Replies
  • 199 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by Sam367

Dani AI

Generated

— short, practical perspective that updates the earlier replies from and and points to current, easy-to-follow next steps.

Modern snapshot: PHP is still viable but works best when paired with a structured framework such as Laravel. (laravel.com) Microsoft’s web stack is now cross-platform as ASP.NET Core, suitable for both APIs and full web apps. (dotnet.microsoft.com) The traditional JSP/servlet route has largely been superseded in new Java projects by opinionated tooling like Spring Boot. (docs.spring.io) For rapid full-stack development, Ruby on Rails remains a maintained, productive option. (rubyonrails.org) ColdFusion still exists (Adobe and the open-source [Lucee] site) but is a smaller, more specialised ecosystem. (lucee.org)

How to choose and learn: match the tech to the goal — simple content/portfolio sites and many shared hosts → PHP/Laravel; enterprise or MS shops → ASP.NET Core; large Java shops or microservices → Spring Boot; rapid MVPs/startups → Rails. A practical path: solidify HTML/CSS/JavaScript and Git, pick one backend stack, build a single CRUD app with authentication, then deploy it (shared host, container, or a PaaS). Real deployed projects matter far more than theoretical comparisons.

Addressing points in the thread: ’ concern about unstructured PHP projects is solved today by frameworks, package managers and coding standards (framework conventions and dependency management reduce scattered “includes”). ’s instinct about raw JSP is consistent with current practice — modern Java development typically uses frameworks that handle configuration, security, and deployment out of the box.

Short, focused practice with one stack and a deployed project will give clearer signals about which language fits personal taste and job goals.

Recommended Answers

All 6 Replies

Member Avatar for hericles

Functionally there is little difference - the end result will be a working website. I find easy PHP easy to code with but a little messy in the long run. I prefer .Net and avoid JSP where possible. Its a fine product to use from a functionality perspective but I find the resulting project has more pages, files, servlets than I would like.
My ruby knowledge is limited but I quite liked it, it is something I would prefer to put more time into and learn better.
You should, of course, learn the one that you find the most interesting and sensible. .Net, PHP, ruby will all be around for a while I imagine.

Member Avatar for Sam367

Functionally there is little difference - the end result will be a working website. I find easy PHP easy to code with but a little messy in the long run. I prefer .Net and avoid JSP where possible. Its a fine product to use from a functionality perspective but I find the resulting project has more pages, files, servlets than I would like.
My ruby knowledge is limited but I quite liked it, it is something I would prefer to put more time into and learn better.
You should, of course, learn the one that you find the most interesting and sensible. .Net, PHP, ruby will all be around for a while I imagine.

Thanks for the response!

But why should i avoid JSP? Is that a litte more difficult than the others which i may find more complicated for me? And why would it become messy in the end with PHP? :)

Member Avatar for hericles

Personal preference, nothing more. I have a dislike for JSP thats all, you may really like it.
PHP makes use of a lot of includes to make better use of code and large projects tend to gather a large number of small code files. They can be handled properly of course, and stored efficiently but I find that unless you (or your team) are highly structured, things just get messy. Its human nature.

Member Avatar for Sam367

Personal preference, nothing more. I have a dislike for JSP thats all, you may really like it.
PHP makes use of a lot of includes to make better use of code and large projects tend to gather a large number of small code files. They can be handled properly of course, and stored efficiently but I find that unless you (or your team) are highly structured, things just get messy. Its human nature.

Well, guess i have to try JSP and see it for myself and also with the .NET and PHP. Thanks for your opinion. :)

Member Avatar for stultuske

the whole JSP-servlet story is getting a bit outdated. are you planning to use JSP's with a framework (Struts, for example)? another option would be JSF, it's a newer technique then JSP. also, if you are familiar with java, you could also take a look at GWT.

Member Avatar for Sam367

the whole JSP-servlet story is getting a bit outdated. are you planning to use JSP's with a framework (Struts, for example)? another option would be JSF, it's a newer technique then JSP. also, if you are familiar with java, you could also take a look at GWT.

Maybe, i'll go and take a look with JSF as well. Thank you

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.