I'm not going to defend the specific people your reference, as obviously they had other problems. But I will defend that Access isnt' that bad. First off, you DON'T run Access 2000 itself... it is just a tiny little driver that has no user interface, reporting or otherwise... it is just a SQL interface to a MDB file.
THE PROBLEM is that most web developers can't program a database worth crap. They use TEXT fields for everything, don't know about indexes, don't know the advantages of caching in-RAM data...
I've seen VERY HEAVY sites run on Access. It isn't slow... there is overhead when going over a Ethernet network to a remote database server... sometimes Access works great because it is nothing more than a 1MB DLL file on the WinNT / Win2K box.
Poor design is poor design. Good design can make a VW Bug do a 1/4 mile in under 10 seconds! You don't need a BMW JUST to get speed. Yes, it makes it easier, but also a lot more expensive.
Slashdot Mirror
haha true.
I'm not going to defend the specific people your reference, as obviously they had other problems. But I will defend that Access isnt' that bad. First off, you DON'T run Access 2000 itself... it is just a tiny little driver that has no user interface, reporting or otherwise... it is just a SQL interface to a MDB file. THE PROBLEM is that most web developers can't program a database worth crap. They use TEXT fields for everything, don't know about indexes, don't know the advantages of caching in-RAM data... I've seen VERY HEAVY sites run on Access. It isn't slow... there is overhead when going over a Ethernet network to a remote database server... sometimes Access works great because it is nothing more than a 1MB DLL file on the WinNT / Win2K box. Poor design is poor design. Good design can make a VW Bug do a 1/4 mile in under 10 seconds! You don't need a BMW JUST to get speed. Yes, it makes it easier, but also a lot more expensive.