1. X
  2. Christopher / クリス
Log inSign up
Christopher / クリス
697 posts
Christopher / クリス profile banner
@atomicptr

Christopher / クリス

@atomicptr
Husband・programmer・🇩🇪 🏴󠁧󠁢󠁥󠁮󠁧󠁿 🇯🇵・bjj/judo・🐧
atomicptr.dev
Joined August 2023
1,715
Following
152
Followers
RepliesRepliesRepostsRepostsMediaMedia

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • @atomicptr
    Christopher / クリス
    @atomicptr
    Aug 23
    This is surprisingly clean in Odin
    Image
    Image
    @ChShersh
    Dmitrii Kovanikov
    @ChShersh
    Aug 22
    C++23
  • @atomicptr
    Christopher / クリス
    @atomicptr
    Aug 22
    RAD Debugger not only runs on Linux now but also has a surprisingly powerful theme system, my first attempt at a Catppuccin Mocha theme
    Image
  • @atomicptr
    Christopher / クリス
    @atomicptr
    Apr 9
    I wrote an article about how to turn #Neovim into a #Defold IDE
    Image
    From Scratch: Turning Neovim into a Defold IDE
    From atomicptr.dev
  • @atomicptr
    Christopher / クリス
    @atomicptr
    Oct 24, 2025
    I wrote an article about "Safer message passing in #Defold", which explores some approaches on how to make message passing safer
    Image
  • @atomicptr
    Christopher / クリス
    @atomicptr
    Oct 17, 2025
    I really like using asserts for setting up axioms, if one of them fails that either means I made a wrong assumption or more likely I found a critical bug. If these fail the program will not do anything useful going forward maybe even something really bad so a crash is exactly
    @iavins
    v
    @iavins
    Oct 17, 2025
    Arguably, Go doesn't have asserts because, well, Pike doesn't like them 🥲
    Why does Go not have assertions?¶
Go doesn’t provide assertions. They are undeniably convenient, but our experience has been that programmers use them as a crutch to avoid thinking about proper error handling and reporting. Proper error handling means that servers continue to operate instead of crashing after a non-fatal error. Proper error reporting means that errors are direct and to the point, saving the programmer from interpreting a large crash trace. Precise errors are particularly important when the programmer seeing the errors is not familiar with the code.

We understand that this is a point of contention. There are many things in the Go language and libraries that differ from modern practices, simply because we feel it’s sometimes worth trying a different approach.
Advertisement
Advertisement