1.  

    I’m sorry, but how the heck are you able to program walking at 6 miles per hour? I can barely manage 1.3 mph

    1.  

      Saved my hapless ass when I took category theory. Great resource.

      1.  

        I had a lot of trouble following this essay, it really could have used another round or two of editing. Also, are you talking about feedback loops as in “things affect each other” or the more precise meaning of “system where one output is used as an input”? Many of the examples you give aren’t at all like that, they’re just cause-and-effect.

        1.  

          _why’s Poignant Guide was my introduction to Ruby. Definitely not a conventional tech book :) But I loved it.

          1.  

            This happens with credit card numbers too. Advise filters and validations on human input for sensitive numbers in and around order placement.

            1.  

              His experimental technique consisted of slowing UDP packet transmissions over the target cable to a very low speed and then transmitting single letters of the alphabet.

              So, not at all like any normal traffic you’d see over ethernet right?

              1.  

                I don’t understand what you’re getting at here

                I just meant, I can’t really evaluate what you are saying is true because everyone is biased that their own approach is best and I can’t see the code myself. I do want a good table system if it makes the code simpler though.

                1.  

                  I’m honestly happy he’s living the life the way he enjoys. But the justification post for living that life? That feels off… I hope he diversifies a little bit, because the options are that either he really is exceptional and can live this way a couple more decades, or much more likely he’ll want to / be forced to make a change sooner and having something else in life will be welcome. There’s a lot of things we can happily do in 20s that go away quickly.

                  1.  

                    By far the biggest problem with game engines is tooling for non-programmers being lacking, so I really agree that the author’s claim to disrupt the engine industry without ever engaging with the non-programming part of production, or doing any research in what engines could be better at whatsoever. Smells of hubris at worst (I guess the implied “10X” here…) or naivete at best.

                    Likewise, I suspect you can’t build an engine without a game to inform its design, or you just have architecture astronomy.

                    1.  

                      @pushcx, could you please merge this with Python Multithreading without the GIL, an earlier story on this topic?

                      1.  

                        dialectical materialism

                        Definitely a feedback loop.

                        1.  

                          In my opinion, you use “code editor” to equivocate between two different tools. One is for programmers, and it facilitates programming. We usually call these IDEs. The other tool is for product designers, and facilitates product development without programming. This is closer to the prototyping or WYSIWYG tools of today.

                          I think this equivocation is a disadvantage when it comes to answering some of your initial questions:

                          What metric can we even use to measure the perfect code editor? How will we know if and when we have it? Are we close to reaching that point?

                          You can’t hold IntelliJ and Figma to the same standard, nor VSCode and Squarespace.

                          This is why the problem statement appears contradictory: two different solutions to two different problems are compared as if they were of the same kind.

                          1.  

                            I’m on call this weekend so my movements are restricted. I’m reading and hacking on some old networking code.

                            1. 5

                              I dunno, I got into programming to make computers do stuff, but if all you do is play on the computer it’s more like the computer is making you do stuff than the other way around. The saying is “all work and no play makes Jack a dull boy” not “all work and no play makes Jack burn out”. Burnout concerns aside, I can’t imagine that spending this much time programming and doing nothing else gives one much perspective on what actually needs to exist in the world when you spend so little time in the world.

                              The author spent four years making a game engine in Go. That’s neat. I’ve been programming Go since r59, I work at a game studio where I program Go full time, and I’m in an MFA program for game design. I’m also a Zig sponsor and I’m highly interested in Zig. I’m very inclined to care about a game engine written in Go, excited about how Zig can be used for games (I think it might be a really great fit), and actively work on games. I’m writing this post procrastinating between programming tasks on my game design MFA thesis. I’m highly predisposed to like the author’s projects.

                              I’m working double-time on a secret ten-year vision to upend the gaming industry

                              ok cool, that probably needs to happen, but doing that requires a deep understanding of the game industry, which is not exactly on display.

                              Several real video games, which I believe can be competitive with what AAA studios offer today.

                              …what games? Where can I play them? I can’t for the life of me actually find a game of the authors to play. Am I missing something here?

                              My vision requires only time and diligence.

                              weee-oooo, weeee-oooooo, the alarms are going off, full klaxons blaring. If your vision is to upend the game industry, it’s really, really, really important to understand that programmers are not the majority of the game industry. Learning to work with artists and designers is incredibly important. Game engine developers are an even smaller portion of the industry. Your vision doesn’t only require time and diligence, it requires colleagues.

                              Spending four years developing a game engine in Go is not alarming. I think Go actually does have potential as a gamedev language and the cries of “wah you can’t use a GC’d language and succeed” are a little ridiculous when the vast majority of indie games are made in Unity, which is garbage collected. What I find extremely alarming is spending four years making a game engine that, according to its FAQ, does not have a level editor. That is a complete non-starter for… nearly all people who make games.

                              It’s not the time that I find alarming, it’s the lack of examples of games made by other people in the author’s engine that I find alarming, and the lack of games made by the author with non-programmers that I find very alarming. There’s a pretty huge difference between making games by yourself and making games with other people, and when someone has a github account but not an itch.io account… well… I wouldn’t place any money on their ability to upend the game industry.

                              1.  

                                I read _why’s poignant guide, but it was a slog and didn’t actually get me programming again. I read Dive Into Python and that was what set me on the path to professional programming. Mark was a real one.

                                1.  

                                  … but actions in time are acyclic

                                  Until you introduce economics / strategy / betting.

                                  1.  

                                    This reads like the author rediscovering the concept of dialectical materialism

                                    1.  

                                      I didn’t know Pilgrim’s story. I miss his posts.

                                      1.  

                                        I think that the analogy with reading is a great one. There’s a big difference between doing something because you have to vs. because you want too.

                                        I’m privileged enough that I still get high at work from coding, intense focus, deep concentration, complicated problems and a huge sense of satisfaction at the other side of the problem. But personally coding is something I do for a living but have a bunch of interests outside of it too (nature, music, reading, finances, radio, RC… kinda too many hobbies 😅)

                                        But I’m glad that the author enjoys what he’s doing!

                                        1. 7

                                          Whenever people mention _why, I immediately think of Mark Pilgrim. While his book Dive Into Python isn’t nearly as whimsical as _why’s, it was many people’s first introduction to Python. Similarly, Dive Into HTML5 was an critical reference if you didn’t want to have to parse the W3 specification.

                                          Similar to _why, Pilgrim also removed himself from the Internet. Incidentally, one of his essays is entitled “Addiction is…”; he was fired for writing it.