My inner self cries when I see:

Copyright © 2002-2013

  • 17
    Never hard code! NEVER!
  • 10
    Maybe it actually marks the date of rights end?
  • 6
    @norman70688 Copyright's always applicable
  • 14
    We should just be writing - © Always.
  • 8
    Why, this makes clear from when to when a project was being actively developed and maintained.

    As for my website, I do hardcode the date - in the footer template. Once per year, I have to change the year, re-compile and upload. Not that hard, and no server load at runtime.
  • 2

    For 1 website?
  • 3
    @Linux yep. Of course, if you are using a CMS anyway and do 80 requests and 200 database queries for each page, then one more to insert the current year won't matter.
  • 5

    I mean, most webdevelopers have alot more sites ;)
  • 4
    @Linux then again, most web devs aren't into performance optimised websites so that one tiny runtime slowdown more won't matter.
  • 0
    My inner self tells:

    A vulnerable application ahead
  • 2
    @Fast-Nop Most web devs have so many more tasks for their multitude of sites that it’s just a pain in the ass to update.
  • 2

    No, that's not it.

    You can't speak for all webdevs when you only manage one or two websites.

    Aswell as I can't speak how to take care of banana trees when I've only grown tomatoes.
  • 1
    ffs, automate what you can
  • 2
    My favorite ones are (had coded):

    Presently ©️ Copyright

    And the one I use the most is

    Copyright 2007 - Present.
  • 0
    @Linux that's exactly that. The vast majority of real world websites are far away from any performance optimisation. Just check out stuff with gtmetrix.com and see.

    Even devrant.com, which is already above average, doesn't earn more than a C, and that's not because of complicated things, but just some sloppiness.
  • 1
    @Fast-Nop Why on earth would you want to do that? You could even just document.write the actual year on the client side.
  • 0
    @CodeMasterAlex because static things have zero runtime cost, and that's what I'm aiming for if possible. Changing the year in the footer template once per year, re-compile and upload isn't a burden for me.

    It would be if I had a lot of websites to maintain that way - in which case I would of course automate these steps completely.
  • 1
    Performance is not a good reason, it takes almost no time to print a year. If you want a fast website, look at compression, caching, use optimised images (webp?), HTTP/2 and split your css/js, etc...

    Maintaining that shitty copyright line is a pain in the ass when you do lots of websites. It is useless anyway, copyright is foreseen by the law, you don’t gain anything by adding that line.
  • 1
    a cronjob that changes the copyright date in your footer.html once a year
  • 0

    assuming that you use the same server
  • 0
    I don't think you can claim copyright for counting up by one.
    The end of "(c) start - end" marks the last change you claim copyright for, so 70 years (might be more) after you die it enters the public domain.

    Tl;dr: counting the end up for unchanged projects is a lie.
  • 0
    const endYear = document.getElementById("endYear");
    endYear.innerText = (new Date()).getFullYear();
  • 1
    Webdev here: copyrights are extremely useful to see when something was actively developed. I use a small CI pipeline to update the year if a commit comes in at CURRENT_YEAR. Just updating something automatically without contributing can be dangerous and cost me a lot of nerves when using some deprecated open source projects etc.
Your Job Suck?
Get a Better Job
Add Comment