• 3 Posts
  • 8 Comments
Joined 2 years ago
cake
Cake day: July 6th, 2023

help-circle




  • I personally welcome this decision. I am fairly happy with the current syntax and I enjoy the explicit “does what it says” nature of Go code. None of the proposed alternatives would have made error handling more robust, they were pure syntactic sugar with no nutritional value.

    Saying no to multiple proposals when you feel that the status quo is better can be difficult to do and I am happy that the Go team is able to make these kinds of decisions.



  • In the subject you wrote “successful full sys update” but the script and the other suggestions I see so far don’t actually handle the “successful” part.

    The log message only tells you that the update was started and the db mtime only indicates that the db was touched without saying anything about success.

    I’d go about this by always performing the updates through a wrapper script that could check the exit status of the pacman or yay command and record a timestamp accordingly.