Digital Mark

  • 0 Posts
  • 18 Comments
Joined 3 years ago
cake
Cake day: March 20th, 2022

help-circle







  • I often had to poke around inside Atom to see what it was really doing, what some bug was, and to figure out how to write or configure extensions. I don’t as often do that with Vim, but it’s pretty clean C.

    Do you not look inside the overly complex tools you use, especially beta ones? The whole appeal of “open source”/“free software” etc. is you can read the code. But if it’s in something you can’t stand, that’s a disadvantage.


  • I liked Atom, performance was tolerable on my overpowered machine, but MS killing it just sent me back to Vim and modernizing my plugins.

    Zed positives: Metal rendering. I use a Mac, so one platform’s fine. But negatives: Rust, so I can’t/won’t touch any internals, and I loathe the Rustacean propaganda wing. No extensions yet. Config is another stupid json file.

    You know what’s great about vimrc? It’s easy to put in a few config commands, and then you realize you’re working in the scripting language. You don’t have to switch to a whole new file format. Thanks, Bram.




  • Perforce is great for dealing with media files, artists can actually use it without producing 500 variants of -new-old-2022-final-dontuse-revised-1.1-2023 filenames (I AM NOT JOKING.), and it doesn’t slow down with a lot of media like git does (which has to check out the entire history). Since usually only one artist touches a file at a time, locking doesn’t slow them down.

    Subversion’s kind of the same for devs. There’s a single source of truth, merging and branching is a lot easier, but it’s less possessive about files. You can do media in it, better than git, but not as nicely as p4. I have seen the -new-old filenames end up in svn, but if you delete a file and commit, it goes away.



  • Digital Mark@lemmy.mltoProgrammer Humor@lemmy.mlThe eye-opener commit
    link
    fedilink
    English
    arrow-up
    29
    arrow-down
    1
    ·
    1 year ago

    “My project” doesn’t exist in any team. It’s everyone’s project. A manager needs to have a long conversation with Pink Pants.

    If you build your project at anything but highest error level, clang -Wall etc., you’re letting errors in, relying at best on coincidence to work the way you think it does.

    Commit it and don’t revert it!