• 2 Posts
  • 132 Comments
Joined 1 year ago
cake
Cake day: April 27th, 2024

help-circle





  • For myself: Dan Simmons’ Hyperion Cantos. I know that I will never be in a situation to do as the question above suggests (nor that I would have the knowledge or skills required), but I am currently re-reading the books (Hyperion, Fall of Hyperion, Endymion, Rise of Endymion), and I can’t stop thinking about a big screen adaptation.

    Or rather, Simmons’ writing is so vivid, so vibrant that you can’t help but visualize it in a cinematic way before your inner eye anyways. The alien, but still somewhat familiar environments, the gargantuan forces of nature and expansive backgrounds just as much as the more intimate set pieces, cities, secret meeting rooms, and so on. “Every Frame a Painting” is something I’ve heard said about some movies, and these books are the textual equivalent: “Every page cannot be helped but be turned into a Painting”. The Hyperion Cantos isn’t even my favorite book or anything the like; it’s just something that screams for an adaptation IMO, and a beautiful one at that.

    I also think that the story is exceptionally well suited for either a limited series (Hyperion & Fall of Hyperion) or a movie (Endymion, Rise of Endymion). In fact, I am convinced that if this had been made into a series back in the early/mid 2010s, it could have had a genre- and generation-defining impact akin to (the early seasons of…) Game of Thrones. Today… I’m not sure a studio would spend the required amount of money to make this good.

    (Also yes I made this post simply because I had nowhere else to put this comment.)




  • Because a commit should be an “indivisible” unit, in the sense that “should this be a separate commit?” equates to “would I ever want to revert just these changes?”.

    IDK about your commit histories, but if I’d leave everything in there, there’d be a ton of fixup commits just fixing spelling, satisfying the linter,…

    Also, changes requested by reviewers: those fixups almost always belong to the same commit, it makes no sense for them to be separate.

    And finally, I guess you do technically give up some granularity, but you gain an immense amount of readability of your commit history.




  • Same. And even if you were to fuck up, have people never heard of the reflog…?

    Every job I’ve worked at it’s been the expectation to regularly rebase your feature branch on main, to squash your commits (and then force push, obv), and for most projects to do rebase-merges of PRs rather than creating merge commits. Even the, uh, less gifted developers never had an issue with this.

    I think people just hear the meme about git being hard somewhere and then use that as an excuse to never learn.


  • Grew up on it. My dad set up a Ubuntu 4.10 PC for my brother and I when we were 3/5 (no internet, obv), and it stuck.

    Used Windows for a brief time in highschool to be able to play online with friends.

    Went right back to Linux when going to university. Will never change back, both for ideological reasons and because Linux is just better.

    Next step: NixOS on a phone