Long-term web-development: Win/MS or Linux/open src
-
I want to start developing a scalable web application, with the goal of starting a company in 1-2 years. The application would be something like a dating site, requiring: 1. Support for many users 2. Database access 3. Access to a toolbox of algorithms developed in a high-level language. (I'd like to develop something that has a simple front-end, not too much scripting stuff, with most of the coding done in something like C# or Java). I do not have experience with serious web development, and I am not a great systems guy (i.e. setting up servers, connections, tuning configuration files is not something I look forward to), so ease of setup and maintenance of the server, database, etc, is very important to me. In the past, I have worked a little in UNIX/Linux environments with Java, C, but most of my coding has been done in Windows using MS products (VisualStudio, C++/.NET), and in general I have found development with MS solutions easier, and in the case of .NET, more powerful. What I really want to find is some analysis of long-term web-development pros/cons for Unix/Linux vs. MS+.NET. Right now I am thinking about how to obtain all software/hardware to run something like: [MS Win 2003 Server Web]+[VS .NET]+[MS SQL or My SQL] but it seems pretty expensive, and I would like to be sure that going with Linux tools is not the better option in the long-run. I would greatly appreciate your thoughts on the subject, or any links to related information on the web. Thanks! - Vlad G.
-
I want to start developing a scalable web application, with the goal of starting a company in 1-2 years. The application would be something like a dating site, requiring: 1. Support for many users 2. Database access 3. Access to a toolbox of algorithms developed in a high-level language. (I'd like to develop something that has a simple front-end, not too much scripting stuff, with most of the coding done in something like C# or Java). I do not have experience with serious web development, and I am not a great systems guy (i.e. setting up servers, connections, tuning configuration files is not something I look forward to), so ease of setup and maintenance of the server, database, etc, is very important to me. In the past, I have worked a little in UNIX/Linux environments with Java, C, but most of my coding has been done in Windows using MS products (VisualStudio, C++/.NET), and in general I have found development with MS solutions easier, and in the case of .NET, more powerful. What I really want to find is some analysis of long-term web-development pros/cons for Unix/Linux vs. MS+.NET. Right now I am thinking about how to obtain all software/hardware to run something like: [MS Win 2003 Server Web]+[VS .NET]+[MS SQL or My SQL] but it seems pretty expensive, and I would like to be sure that going with Linux tools is not the better option in the long-run. I would greatly appreciate your thoughts on the subject, or any links to related information on the web. Thanks! - Vlad G.
it's to understand the size of the project from your post but I see here two options 1. MS technilogies: they are not cheap and maybe you should buy them. but ms technologies allow you to make extensible scalable things much faster. e.g. you can use 3rd party data access level generators that generate the DB structure, Views, SPs and .net code. VS generates useful code and allows easy to debug the code. MSSQL allow to use more complex data queries. as a rule, support is much cheaper using ms techs. 2. Unix/Linux/MySQL: most of tools are free(PHP,Apache,Perl,MySql etc). PHP and perl are script langs so they are slower than .net ones. I have never seen such powerful PHP IDEs as MS VS. Java IDEs are very powerful now(but I would prefer the .net technology it seems to me that it gets things done faster than Java) but you will have to write more code than when you use .net lang. mysql has many limitations sometimes you have to write many sql sripts to collect a required result when you need to write only one sql queries in T-SQL. I guess you need to take a close look at those techs and at your reqs. but before you have to analyze and define what you want to make. then look at the solution from the technology point of view. I guess that will help you to make right choice between cheap development/support and cheap technologies.
-
it's to understand the size of the project from your post but I see here two options 1. MS technilogies: they are not cheap and maybe you should buy them. but ms technologies allow you to make extensible scalable things much faster. e.g. you can use 3rd party data access level generators that generate the DB structure, Views, SPs and .net code. VS generates useful code and allows easy to debug the code. MSSQL allow to use more complex data queries. as a rule, support is much cheaper using ms techs. 2. Unix/Linux/MySQL: most of tools are free(PHP,Apache,Perl,MySql etc). PHP and perl are script langs so they are slower than .net ones. I have never seen such powerful PHP IDEs as MS VS. Java IDEs are very powerful now(but I would prefer the .net technology it seems to me that it gets things done faster than Java) but you will have to write more code than when you use .net lang. mysql has many limitations sometimes you have to write many sql sripts to collect a required result when you need to write only one sql queries in T-SQL. I guess you need to take a close look at those techs and at your reqs. but before you have to analyze and define what you want to make. then look at the solution from the technology point of view. I guess that will help you to make right choice between cheap development/support and cheap technologies.
Very good - thanks for your reply. Your comments echo my general impressions. About the size of the project - maybe something like the following progression of steps: 1. 1st prototype - almost no interface, very basic functionality, no real users, testbed for technologies (1 person * 0.5 years) 2. Beta version - basic interface, almost full functionality, several hundred users (2 person * 1 year) 3. Version 1.0 - unlimited users (developers?, time?) So by Step 2, need to lock into a set of tools for the rest of development.. Regarding speed and power, [JavaScript]+[Java] is more or less in the same league as [ASP.NET]+[C#], or am I mistaken?
-
Very good - thanks for your reply. Your comments echo my general impressions. About the size of the project - maybe something like the following progression of steps: 1. 1st prototype - almost no interface, very basic functionality, no real users, testbed for technologies (1 person * 0.5 years) 2. Beta version - basic interface, almost full functionality, several hundred users (2 person * 1 year) 3. Version 1.0 - unlimited users (developers?, time?) So by Step 2, need to lock into a set of tools for the rest of development.. Regarding speed and power, [JavaScript]+[Java] is more or less in the same league as [ASP.NET]+[C#], or am I mistaken?
Vlad Gabovich wrote: Regarding speed and power, [JavaScript]+[Java] is more or less in the same league as [ASP.NET]+[C#], or am I mistaken? well, JavaScript is entirely different thing... scripting language (typicaly for browser) that's it. It has only name common with Java (maybe similar syntax, but that can be misleading - these two are differend languages from different creators and for different purpose IMO). Java + .NET are similar, from architectural and usage views and yes even speed & power. It's no secret that .NET has many ideas from Java... whatever is in Java I'd expect it's better (faster) version in .NET... Many people may prefer Java just because it's not Microsoft's :) And there can be some things better in Java then in .NET, however I don't know any (more experienced developers?? maybe but thanks to similarity with Java and C# languages I think it's not a big deal that .NET is younger than Java). just my 2 cents I bet there are some Java developers who may have diferent opinion... go ahead guys! I'd love to learn where I am wrong about Java... David Never forget: "Stay kul and happy" (I.A.)
David's thoughts / dnhsoftware.org / MyHTMLTidy -
Very good - thanks for your reply. Your comments echo my general impressions. About the size of the project - maybe something like the following progression of steps: 1. 1st prototype - almost no interface, very basic functionality, no real users, testbed for technologies (1 person * 0.5 years) 2. Beta version - basic interface, almost full functionality, several hundred users (2 person * 1 year) 3. Version 1.0 - unlimited users (developers?, time?) So by Step 2, need to lock into a set of tools for the rest of development.. Regarding speed and power, [JavaScript]+[Java] is more or less in the same league as [ASP.NET]+[C#], or am I mistaken?
i think you will be able to decide what techs it might best to use basing on deliverables of the 1st stage. ASP.NET and JavaScript are different things. parts of an ASP.NET are content(web forms, html etc), program logic(executable files, scripts that could be JS) and config (iis setting, web config, css). I'd say that an ASP.NET is kind of JSP. but there are several differences e.g. codebehind. it is a division of the web page into two units those ones are view and program logic. so that it makes much easier to change the face of your application. Also ASP.NET has many useful web controls that JSP has not. when you use JSP sometimes you have to write own web control that takes time. JavaScript is a scripting language targeted specifically at the Internet. You can use JS language to interact with DHTML DOM from the web browser side. Yes, Java and C# are from the same league. but they have significant different architectures. Java code is compiled into kind of intermediate language that is interpreted by the java virtual machine. C# code is compiled into MSIL that later is compiled into e.g x86 instructions. so that C# code is much faster than Java.