Forum Moderators: open
Thanks
It's pre-installed on Windows webservers and runs native on Windows servers.
You can do many of the same functions using PhP or JSP or Cold Fusion, but those require separate installs on Windows servers. PhP sometimes runs natively on Linux servers.
"Microsoft's Internet Information Server (IIS) is the most common Web server in the Fortune 500
And who sponsors PDC?
You need to read a few chapters further in your Penguin big book of conspiracy theories.
You can check the facts for yourself by visiting the web sites of the Fortune 500 companies and checking what web server they are using.
You should really be asking who sponsers the Fortune 500, and the answer to that would be AOL Time Warner.
Considering that AOL Time Warner have sued Microsoft for Anti-Trust, I doubt they'd be rigging the Fortune 500 list in Microsoft's favour.
However, don't let that stop your conspiricy theories. The Anti Trust suit might just have been a clever ruse by the Illuminiti just to put you off the scent because they knew you were on to them.
:-D
There's a larger supply of Windows programmers and that brigs labour prices down, so it's cheaper to maintain.
Also, in my opinion, development in ASP is faster than in any other web oriented programming language.
There may be competing platforms that are free (as in beer) to opbtain, but saving £2,000 on the software is a drop in the ocean compared to the development and maintenence costs of a large web site.
I'm not aware of any bigwigs that use asp. In fact, in my area, Boeing, Edward Jones, and all the big companies are hiring and none are looking for asp/.net or any MS stuff.
This means that their Microsoft stuff is running flawlessly and thus they don't need to hire staff to fix what's not broken. :)
Who sponsors/runs PDC is significant because if you are going to MS to find the best product to run, MS is not going to send you to Java/Apache/Linux, etc.
Last report is almost 80% of the web does not run on MS software. I agree that it's possible they use .net/asp because it's easier to use than Perl but I do not know how all these companies use it.
I have a couple of hours to kill this morning so I think I'll try and do a little research.
Last report is almost 80% of the web does not run on MS software. I agree that it's possible they use .net/asp because it's easier to use than Perl but I do not know how all these companies use it.
Well, last report also showed something like 71% of my users are still using internet explorer as a browser. The choices of the masses are not by definition the best choices.
When you point out '80% of all web sites' it should be considered that many, many, many websites are:
a) not for profit/hobby sites
b) educational
c) 'businesses' in a limited sense (aka the website IS the business, with no extensive business structure behind it)
These types of websites would naturally choose open source freeware, it is likely the only option.
Compare the stats for the Fortune 500 and the top 500 sites in Alexa and you'll see a very different story, and in neither case is it a useful guide to what is best for your site.
This could be a problem for them in the near future if another company decides to cater to us (Google?).
It seems to me that I can get all the cool functions that ASP websites embrace with by just sticking with these.
Tis true, but there are some things to take into account. MySQL - Last I looked, it still doesn't support stored procedures, which help to greatly reduce SQL injection attacks (if you are even aware of such). I'm not saying that stored procedures are the holy grail, just a chink in the full armor body suit that you need to be thinking about.
XML - Unless you are using PHP 5, last I looked, it was a PITA to actually send an XML request to a server, receive the response, then either load an XSL stylesheet to transform your XML result set, or just parse through it manually. (Is it SimpleXML thingy in PHP 5?)
Regardless, you will use what you are comfortable with. I currently work as an ASP.NET development programmer for one of the largest financial institution software companies in the Nation. We are celebrating our 30th anniversary and are a full M$/IBM shop.
Take it for what you will.
Since they probably already own enterprise licenses for the tools, the cost of deploying one more system on that language is not high. On the other hand, if they opt to use a different toolset (even if it is free or low-cost) the question of "who is going to maintain it" comes up. If all of their internal developers are already working with VB/C++/C#/SQL Server, the long-term maintenance costs are spread out among several systems. Deploying a "renegade" system will require hiring one or more new people that can maintain it (or forking over money to cross-train existing employees).
VB was the tool that really let corporations develop custom desktop applications to match their work processes. Consequently, many large corporations have a lot of developers that work with the MS toolset.
Don't think that this chicken-and-egg situation is overlooked by MS. They spend a lot of time and money courting developers and IT managers. Their certification program, the routine overhauls of the entire "languages" of VB and C (++/#), the upgrades to the developer IDE, etc. are all calculated to keep developers locked in to their products: If most of the work requests you get are on the MS platform, then you want to stay up to date on the MS platform. If you take the time to stay up to date on the MS platform, it is difficult to delve into or keep in touch with other languages and platforms.
MySQL does use stored procedures now.
with serious bugs... see the recent InfoWorld review from the Dec edition.
- Large Sprocs cause the database to lock up (and that's not the worst bug either)
I think john_k hit on something. VB!
VB was the worlds most popular programming language (might still be). So it's only natural for that development community to recommend and move themselves and their companies into other microsoft technologies. Picking up ASP from VB involved almost zero learning curve.