1. 33
  1.  

    1. 7

      Hey, this is my post! Happy to answer any questions.

      1. 3

        You don’t need to convert your repo to push the history! Just add the remote and push. You don’t need to convert it into a git repo; it’s already using a git repo under the hood.

        1. 2

          Wonderful! Thank you

          As an aside, it seems as though jj is positioned to ameliorate the git world as TS ameliorated JS? Perhaps too early to tell.

          1. 4

            The analogy works, but success is never assured :)

        2. 2

          “but this is the first time I really write something” - typo, should be “wrote”

          1. 1

            Thanks for reading to the end! I’m on a road trip, there are a few silly typos I will fix later, also need to get the repo up. Though I believe that use of ‘write’ was intentional, as in:

            this is the first time I really write [a project using the language].

        3. 4

          there is a deprecated API that shows up higher in the search results

          My experience with Zig in a nutshell :)

          1. 3

            Code is now up! Thanks @steveklabnik, your jj tutorial worked like a charm.

            1. 2

              Thanks for introducing me to “Semantic Compression” blog post, I love Casey’s stuff, but wasn’t familiar with this one.

              1. 2

                Welcome! I especially love the conclusion:

                The fallacy of “object-oriented programming” is exactly that: that code is at all “object-oriented”. It isn’t. Code is procedurally oriented, and the “objects” are simply constructs that arise that allow procedures to be reused. So if you just let that happen instead of trying to force everything to work backwards, programming becomes immensely more pleasant.

                While not all code is procedurally oriented, I like this conclusion because it explains why object-like constructs naturally arise even in non-OOP code.