Slashdot Mirror

microsoft are funding MySQL Server now?

those guys over at http://www.mysql.com/ will be so pleased!

bad news for the http://www.postgres.org/ guys though.

;-)

Sybase ASE: same original codebase as MSSQL Server
Oracle: most well-known database engine in the world
MySql: Most popular Open-Source database in the world
PostGres: Not my cup of tea, but its an option
DB2: IBM's DB2... SuSE and RedHat only

I always shudder at the thought of running a database engine on Windows...

At some point, your customer is likely to need or want commercial software (esp RDBMS), and they will find that Debian is simply not supported by any commercial software vendor.

What about MySQL, or do you not consider them to be "comercial" because their support offerings are optional and you can use their product for free if you choose to? MySQL offers comercial support to any and all who use their product, regardless of the platform you've installed it on (even Windows!), but of course you'll have to get your .debs from Debian, even if you do plan on using MySQLs support offerings..

Or you can use PostgreSQL on Debian and get your support from PostgreSQL Incorporated, but only if you're truly interested using using a reliable, and standards compliant database available (for raw performance, you'll want MySQL).

I understand your point, but it simply is not true that there is no commercial support for Debian (and that list is sorely incomplete). Yes, it is best if at least one person in your company take the time to become familiar enough with Debian to handle problems on their own, but that is true no-matter what OS you are using. If the consultant is most familiar with Debian, and Debian provides the capabilities needed by the client, then there is little reason not to use Debian.

Uhhhh. What is "PERL"?

where did you try to look?
this currently gives the most important sites within the first result set (by the way: why does mysql.com score so high?). i'd like to propose using lower case unless you know better.

removing X (yes X!) from any given dist (which uses it) is relatively easy [i do so on old hardware == small budget and for the pro look *g*], removing perl (if it is in default install) is a lot more of a problem. coding in perl is fast (and dirty), the amount of modules is amazing.

Apache: granted, this one should not be in any desktop default. it seems quite common (for dists) to use it to display html docs on a webserver rather than out of the the filesystem. this might be acceptable use with a lightweight alternative (e.g. boa) but apache mem footprint is to large for my taste.

mysql: this is a true database (not Excel or Access). it may not be (an) oracle, but it already contains a lot of heavy (at least for me) math, as such i find it interesting. sql (meaning the language) is quite easy to understand and use (perl is a good one for this, as it is so easy on strings). MS is thinking about moving the entire(?) filesystem into a database, and some projects (here a rpg) are already using it, more a sure to follow. though i prefer postgres.

php: diversity has it's prize (megs=harddisk=money), but one could (probably) not install anything depending on php.
if you do use a http server and mysql, php is needed to support phpmyadmin (and you probably do want this one).

about x11: the thread says it all: either there is a hardware problem, or you are talking about something other than x. it may include some quite old source, but so does windows (and mac-os is gone). creating a graphical windows system (with support available for hardware built before me up till the latest 3d hardware cards) is quite some project, though indeed there is an alternative ftp://ftp.linux.org.uk/pub/linux/alan/Software/Obs olete/Mini-X/, but most probably not what you want.

• Which IDE you want to use, ranging from Open Source $0 IDE to commercial ones.
• Which source control you want to use, ranging from Open Source $0 source control to commercial ones.
• Which middle tier implementation you want to use, ranging from Open Source $0 application servers to commercial ones
• Which database you want to use, ranging from Open Source $0 databases to commercial ones.

In short, you choose J2EE in order to have a choice of what software you want to use within your business and how much you are willing to pay for it, what hardware (Intel, Sun, IBM) and operating systems (Linux, Windows, Solaris, AIX, OS/400) requirements you have, and what requirements you have on the performance (single Intel box to 64 CPU Sun box to IBM mainframe) and scalability of your application.

You make J2EE match your requirements rather than force yourself to match .NET requirements.

SAP DB and PostgreSQL come to mind.

While I agree that vi doesn't use many system resources, I would argue that it doesn't because it's because these programs are more efficient.

--

Actually, MySQL is one of the best databases out there; and remember, this is old database code. On a similar note, MySQL is not actually open source, it's a very-close-but-not-quite-with-an-old-version-GPLd database. Check out PostgresQL, under a BSD-ish license.