Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Re^2: [OT] Why I don't use Mysql for new projects

by moritz (Cardinal)
on Jul 10, 2008 at 14:50 UTC ( #696717=note: print w/ replies, xml ) Need Help??


in reply to Re: [OT] Why I don't use Mysql for new projects
in thread [OT] Why I don't use Mysql for new projects

You say that MySQL has solved problems but you won't count it because it's not the default?

No, I say that solutions of these problems aren't as valuable as they could be if they were default.

Discovering glitches and then finding that they have already been solved but that I didn't know about these solutions, always leaves that nasty feeling that I'll come across more of those.

Sane defaults are important. Very much so. The Postgres 8.2 manual has about 1700 pages (A4), I'd expect mysql to have about as much documentation. You can be sure that I won't read them all before starting to use my db engine. If the defaults can easily hurt me, I'm lost.

The reason it's not the default is that people expect to be able to upgrade from older versions without having to change their code. I think this is a fair expectation.

Yes and no. Backwards compatibility is valuable, but it shouldn't be the first ruling principle. When our notion changes of what is sane and what not, we sometimes have to break something. Perl does that from time to time as well.

If you really care about compatibility, you can define a set of options that can be activated with a special variable or flag, some kind of a compatibility level.

Update: consider an analogy: if you had the choice between two programming languages, one being perl, and the other being strictperl, that is perl with use strict; use warnings; enabled by default - which one would you use? I'd stick with perl for my old scripts that aren't strict safe, and chose the strictperl version for everything that I newly write.


Comment on Re^2: [OT] Why I don't use Mysql for new projects
Download Code
Re^3: [OT] Why I don't use Mysql for new projects (strictperl)
by chromatic (Archbishop) on Jul 11, 2009 at 08:25 UTC
    I'd stick with perl for my old scripts that aren't strict safe, and chose the strictperl version for everything that I newly write.

    Good news: strictperl exists (though it only enables strict; warnings are more problematic conceptually.)

    Bad news: it's a patch against bleadperl and much of the Perl core does not run with strict enabled unilaterally.

        The use 5.11; feature is good and welcome, but its goal is very different: to reduce the amount of boilerplate necessary to enable newer features. The goal of strictperl is to experiment with a Perl that forces you to be explicit about where you need to avoid strictures; it's an experiment in maintainability and reliability in Perl 5. (The suggestion "Can't you just use a source filter?" I find silly.)

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://696717]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (4)
As of 2014-07-12 14:01 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    When choosing user names for websites, I prefer to use:








    Results (240 votes), past polls