615 karma · joined April 18, 2020
"More readable" is self-documenting! Doesn't matter how you get there (though it's a bummer you've lost faith), just matters that you did.
> No type system will replace docs or even comments. No type signature will give you the why, the big picture or the context.
Types are just one small part of the picture: did you read even the first full message, much less the full post? Are you aware of the other non-type-related benefits Rust provides?
OP helpfully gave an illustrative list I'll reproduce here for you since I'm not sure you saw it:
> When a callback is called are any locks held or do you need to acquire your own? What about free callbacks, are they special? What's the intended locking order? Are there special cases where some operations might take locks in some cases but not others?
> Is a NULL argument allowed and valid usage, or not? What happens to reference counts in the error case? Is a returned ref counted pointer already incremented, or is it an implied borrow from a reference owned by a passed argument?
> Is the return value always a valid pointer? Can it be NULL? Or maybe it's an ERR_PTR? Maybe both? What about pointers returned via indirect arguments, are those cleared to NULL on error or left alone? Is it valid to pass a NULL * if you don't need that return pointer?
Only a few of those are concerned with type safety. You really should read the whole thing.
Furthermore, that's not even the main contention I was highlighting. Without a proper definition, the advice of "just copy/paste these" is dangerous. Someone will draw their line at something too large, copy/paste that in and inherit bugs/vulnerabilities they never fix. That's a big problem.
Are people sending multiple branches of the stack for review at once? It should only ever be the "bottom" branch out-for-review at any time.
> - Namely there would be review comments on the first PRs that then cause a cascade of merge conflicts in the follow-on PRs
This can still happen in the model above of course as you need to make changes to the bottom branch in response to review comments/requests.
However, as I noted elsewhere, `--update-refs` is an absolute god-send in those situations: https://andrewlock.net/working-with-stacked-branches-in-git-...
It reduces a ton of manual work (scaled by how many branches you have stacked!) to one operation.
> Also, cherry-picking (effectively an atomic rebase-type) is underrated.
This this this, all of this.
I never really "got git" until I finally committed to learning how rebase works.
+1 to cherry-picking. Also patch-add (`add -p`).
RIP to an absolute legend.
Not that I ever had the chance to play the pre-release version of the game, but the explosion of complexity has made me yearn for exactly this, a "smaller, more limited version"... so much so that I wrote https://twmtg.computerpho.be/ to try and capture it (and also, admittedly, as a bit of a joke/dig)
It sounds like this means the official end of SPG, the group that Tony Fadell took over to eventually build the iPod (among other things). A storied history, to say the least.
RIP SPG.
-- https://chriswarrick.com/blog/2024/01/15/python-packaging-on...
Chris Warrick has done a ton of thinking - and a lot of writing [1] - on the subject and has very sage things to say about it. But unlike the author, he didn't decide to write another one. Because there are many good reasons not to. Thanks for letting me know you didn't bother reading that follow-up though: pretty clear who is providing zero value here :shrug:
[1] In fact, here's more he has to say about it: https://chriswarrick.com/blog/2024/01/15/python-packaging-on...
"I did not feel well throwing yet another Python packaging tool into the ring.
Yet it exists now and has user. (sic)"
TL;DR: I knew it was a bad idea, but I did it anyway.
But I wouldn't have had to, anyway. Because I know how names work: "Rye" is not in the set of current named tools. Doesn't matter that it wraps them. It becomes one by doing so, and now we have 15.
https://chriswarrick.com/blog/2023/01/15/how-to-improve-pyth... https://xkcd.com/927/
This, x1000.
I cannot count how many hobby projects I have outright abandoned at the first failure, never to return. The fix may have been simple too! I'll never know, though: the startup effort required to re-contextualize myself with the complex mess I'd made was never worth it at the time, and the longer you let them languish the less-likely you are to return. RIP, projects.
Simple Lasts Longer.
Such a juicy premise, let's dig in. In my opinion the primary "speed up" to development comes in allowing changes - especially sweeping refactors - to happen without worry. As a corollary, they provide "primary source documentation" on the inner workings of the code so that less-experienced developers can approach such tasks without worry. The value of these are exactly the same regardless if your tests take 10 seconds or 10 minutes to run. The only difference is that we've sped up our critical path development work by not focusing on hyper-optimizing tests. And to start out the gate with such a premise but then fail to provide any data related to the effects on developer cadence, in a data-heavy writeup!?
They really are fun. In fact making small games was my pandemic challenge: I decided that it was finally time to try these things. I ended up building a tool for cutting up and annotating tile maps first - https://tmt.computerpho.be/ - then used it to create a minimal browser city simluator, https://pc.computerpho.be/. These also served as experiments into building single-file "apps" for the browser, which was fun as well!
Regardless of your feelings on the status quo, there is one thing you must do when building a game engine if you want it to succeed: support Windows.