ASP | Also Known As:
- Started
- Last post
- 29 Responses
- ToxicDesign
"Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Microsoft Access Driver] Operation must use an updateable query."
ASP sucks, use PHP. Had to be said.
...
- brandelec0
I'm going to name you ASP
- tfsmag0
nah asp is fine, you just suck at it....
- ToxicDesign0
Not me bruv,
If I just had 1cent for evey time I visited a site that had that f-ing error...I'd be in rich.
Do a Google search with that error message and see how many sites popup - fun!
...
- Anarchitect0
ASP is for wankers.
- JazX0
tee hee
- tfsmag0
hahahaha
i do both, pretty extensively where i work. i don't think either one is really better than the other in my mind.
but to clarify, that specific error comes from using an MS access database instead of a database that is meant for web sites like mysql or MS SQL. the error there isn't with asp but with crappy access.
- arench0
pronounced: "ass-sp"
- canuck0
doesnt the error message have to do with reading and writing to the access database?
I used to play around with asp and had that problem. It was solved by giving read/write access to the db file.
- rabattski0
asp (252,000,000 results)
vs.
php (345,000,000 results)
The winner is: php
http://www.googlefight.com/cgi-b…
also. why is it 345,000,000 and not 345,112,015 for instance?
- 1977_c0
And now for Something comPletely different.
- tfsmag0
canuck, that is what that error is from... but access shouldn't be used for web applications imo :\
- tfsmag0
most people that hate on one scripting language or another usually do it out of ignorance
ie: they don't know how to do it.
- nicora20
I can see that, I don't hate on other language's, but I wil praise the ones I like.
- brandelec0
drama queens!
*runs behind tfs
- ToxicDesign0
Actually tfsmag is right...
It's more to do with Access integration than ASP it's self.
So why does Msoft promote that combination?
I think more people have migrated away from ASP because their first experience with it was with an Access DB situation - I know mine was...
(could this be my longest thread ever?)
...
- nicora20
I used Access/ColdFusion as my first combo when I was learning. Gawd did that suck! Access sucks the same for me whether in ASP 3.0, .NET or CF. You can't even set a variable to the last identity...
newID = @@identity
I'm all about the MS SQL
- rabattski0
regarding hating a scripting language.
asp hate (1,710,000 results)
vs.
php hate (2,560,000 results)
The winner is: php hate
thus php is the language of luv. the language for the lesser ignorant coders :)
- arench0
last I used ASP ( a few years back now...) dynamic includes had to be called with a specific function and the regex function was darn near worthless.
I switched to PHP for these reasons alone.
i don't know anything about .NET and whether they've epanded in these areas, but it's too late now for me - i wouldn't switch back.
- Anarchitect0
]had this bookmarked bookmarked days ago]
http://otn.oracle.com/pub/articl…"Price. Here, we must consider not simply the price tag of the initial investment, which, in the case of PHP, is obviously free, but also the implementation, maintenance, and debugging costs. In the case of PHP, you may invest in the Zend optimization engine. With ASP, however, you're investing from the very beginning, and you're spending for add-on technologies—libraries for doing graphics manipulations, for instance. But, in the long term, PHP isn't going to press you to upgrade and collect more licensing fees. Everyone who has dealt with complex licensing also knows that companies spend time and money just ensuring they are compliant. Furthermore, you have a difference in response when getting bugs fixed. This, of course, translates to time, which translates to cost for overall development.
Speed and efficiency. As I mentioned earlier, ASP.NET is a framework allowing you to use various programming languages. In addition, it is touted as having a great object-oriented model. All this is true, but it becomes a detriment as far as speed is concerned. For all that advantage, there is a lot more code to run through to execute the same ASP page than you have to execute in the PHP engine for an equivalent PHP page. PHP is the quick-and-dirty type of solution, the one to get the job done. And though a lot of robustness has been added to it since its 2.0 and 3.0 days, it still retains that core optimized high-speed approach.
Speed is not the only consideration. Memory usage is also important.
Security. ASP.NET runs on IIS, which has been compromised innumerable times, as evidenced by IT news reports every other week. It has become such a liability, in fact, that in spite of all the marketing dollars spent on it, many IT professionals refuse to have their networks exposed with an IIS Web server. PHP, however, works with Apache, which has a proven track record of speed, reliability, and hardened security. Check www.securityfocus.com for more information.
Cross-platform applicability. ASP.NET runs on IIS and is starting to run on Apache, which can run on a whole host of platforms. PHP has been designed to work with Apache from the beginning, so you have many proven and reliable server platforms to choose from.
Open source opportunity. Open source is not just some philosophical torch idealistic programmers, or companies wanting to save a few bucks on licensing costs, are carrying. When you're dealing with bugs in the software itself, open source can be a serious godsend.
In either case, with PHP or ASP.NET, you have a large user base using the software and possibly encountering bugs. With ASP.NET, those bugs have to go through a bureaucratic process to get acknowledged, fixed, tested, and rolled out in a new patch or release. PHP fixes, however, can get fixed quickly and rereleased. Anyone who has watched open-source development knows new releases and patches often come out in days rather than in weeks or months, as with commercial software. If that's not fast enough, you can always fix a problem yourself if you have to."