Slashdot Mirror

← Back to Stories (view on slashdot.org)

Linux.conf.au Coming Soon

Posted by Hemos on from the best-show-ever dept.

One of my most favorite Linux-centric shows of all time, Linux.conf.au is gearing up in their latest location - Canberra. The registration is still open; I highly, highly recommend attending the show.

3 of 150 comments (clear)

  1. I Know this has been said a million times ... by GNUALMAFUERTE · · Score: 3, Interesting

    But, since the topics include :

    # Debian Miniconf
    # OpenOffice.org Miniconf
    # Gnome.conf.au Miniconf

    Shoudln't the conference be called GNU.conf.au or GNU/Linux.conf.au?

    Names are important, that's why we use them in the first place. Calling it Unix.conf.au would be misleading. Calling it Linux.conf.au is misleading too ...

    --
    WTF am I doing replying to an AC at 5 A.M on a Friday night?
  2. Great dunking by gstone · · Score: 2, Interesting

    I hope the Canberra weather isn't too cold for another great dunking

  3. Re:Which LCA did you attend? by jonoxer · · Score: 2, Interesting

    A session on profiling web apps was poor. Yes, I *would* expect a web-mail app to spend a lot of time in regexs, that's how you look for injected content.

    You're right, I did a pretty crappy job of doing that presentation. I was stressed, I had lots of trouble getting my laptop to work with the projector, I got the timing wrong, it all just fell in a heap. Oh well, sometimes that happens. At least I learned from my mistakes and revised the presentation: I've since done an extended version of it at 3 other confs and did a dramatically better job of it each time.

    Regarding the regex comment though, it seems you missed the point I was trying to make: sure, regex is appropriate in that situation but I didn't really care about the low-level details. My point was that running the profile showed that all the expensive regex checks were being done on *every* *single* *message* in the mailbox, even when there were only a few being displayed. It's an issue of program flow and structure that becomes blindingly obvious when you do profiling, but may not be obvious when you're working in the guts of the code.