A simple file is beautiful.

I agree, there is nothing more beautiful than simplicity, when simplicity is all that is required.

However, take a good look at a moderatly complex distribution and note that modules are anything but simple. Look the not untypical set of ancillary files involved: 

ANNOUNCE    
ChangeLog   
Event.h     
Event.xs    
INSTALL     
MANIFEST    
MANIFEST.SKIP
META.yml    
Makefile.PL 
README      
TODO        
Tutorial.pdf
c/
    ev.c       
    generic.c  
    group.c    
    hook.c     
    idle.c     
    io.c       
    queue.c    
    signal.c   
    tied.c     
    timeable.c 
    timer.c    
    typemap.c  
    unix.c     
    var.c      
    watcher.c             
demo/ 
    echo.t                  
    group.t                
    msg.pm                 
    perlqt.t               
    process.pm             
    queue_pending.t        
    rand_interval.t        
    readline.t             
    repeat.t               
    semaphore.pm     
lib/        
    Event.pm     
    Event.pod   
    Event/    
        EventAPI.h               
        MakeMaker.pm            
        Watcher.pm              
        generic.pm              
        generic.pod             
        group.pm                
        idle.pm                 
        io.pm                   
        signal.pm               
        timer.pm                
        type.pm                 
        typemap                 
        var.pm       
ppport.h    
t/  
    attach_to.t   
    bored.t       
    callback.t    
    data.t        
    delete.t      
    eval.t        
    fifo.t        
    generic.t     
    group.t       
    hook.t        
    hup.t         
    idle.t        
    idle2.t       
    io.t          
    leak.t        
    leak2.t       
    loop.t        
    now.t         
    reenter.t     
    signal.t      
    timeout_cb.t  
    timer.t       
    unconfigured.t
    var.t                    
util/ 
    bench.pl         
    filehandle.txt

[download]

I can't think of any other situation where developers would not reach for the benefits of a database to manage access to this amount of data and meta information.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco.
Rule 1 has a caveat! -- Who broke the cabal?

In reply to Re^2: CP6AN should be a database by BrowserUk
in thread Notion: CP6AN <strike>should</strike> could be a database by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.