just found out golang exits the program if you call log.Fatal(...)?! that's absurd to say the least!
imagine writing your own piece of code in which you log at a fatal level (e.g. something very-very-very bad happened), and then, all of a sudden, your program just crashes...? without saying anything? and you spend an hour or two just debugging and finding out that a logger has been exiting your process??
i wont quote everything that has been said on the site i linked to, but that's totally fucked up. this should not ever happen in any library unless the user has manually opted that in (e.g. passed a parameter like exitOnFatal: true or something)
imagine writing your own piece of code in which you log at a fatal level (e.g. something very-very-very bad happened), and then, all of a sudden, your program just crashes...? without saying anything? and you spend an hour or two just debugging and finding out that a logger has been exiting your process??
i wont quote everything that has been said on the site i linked to, but that's totally fucked up. this should not ever happen in any library unless the user has manually opted that in (e.g. passed a parameter like exitOnFatal: true or something)