• 0 Posts
  • 98 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle

  • Helix has better defaults for sure and I get why people might prefer it but I have a very hard time imagining it being a better choice than vim in every situation even with a lot more development.

    Also, if you work with programming for example your editor is going to be one of your main tools and I think that “reading guides” is an acceptable amount of effort to put in to learning such a tool. Vim has a higher barrier of entry than it needs to (this can to some extent be explained with backwards compatability) but with Helix you still have to put some time in to understanding the editing model anyway.


  • The biggest thing missing from helix right now imo is plugin support, so a lot of plugins that I really like wouldn’t be available. I use fugitive a lot for working with git for example.

    Another one is the quickfix list in combination with ex commands. One thing you can do for example is setup :make to run your compiler and then when you get compilation errors they’ll show up in your quickfix list. You can then use :Cfilter to focus on one type of error and then :cdo to for example do a find and replace on the remaining lines.

    In general, if I don’t have an lsp available for whatever reason (I work in cmake a fair amount at my $DAYJOB for example) I would much rather use vim, in particular because of the stuff that you can do with ex commands that I mentioned above (also works great with grep) but also because of the ctags support.

    Helix can do a lot of nice things out of the box for a lot of cases of software editing, but it’s not nearly as broad or as customizable of a tool as vim





  • With arch, I’d recommend just jumping in the deep and and installing it, looking things up on the wiki when something goes wrong. Just do it in a virtual machine or on an old laptop or something to start with. I broke my previous distro (mint) by doing some really stupid stuff, and I decided to just go fuck it and install arch. I don’t think I’ve ever learned as much about linux as that weekend.

    I suppose that I was already pretty comfortable with the terminal since I was studying computer science at the time so I had a lot of reason to use it. I think the best way to use the terminal is to force yourself to use it, programming is great for this but you can try e.g. sorting your photos or mp3 files or something as practice too.


  • Debugging is kind of a weak point in vim to be honest, there is a plugin called termdebug which comes bundled with vim that can do gdb debugging ok, but anything more complicated mostly just feels like a lot more work and a bit more jank than just using vscode.

    I use just as well, it’s a more vimy approach than something more tightly integrated so that makes sense.

    Helix is nice, but I don’t think I could leave behind some of my vim plugins, fugitive in particular is an integral part of my git workflow. Haven’t used the kakoune editing model enough to really decide if I think it’s better than vim personally.



  • The first game is a bit different from the rest and it’s greatest strength is the world building of the universe, where it is the strongest title of the trilogy. People mostly like the mass effect series for the companions though, and they are at their best in the second game.

    The first game suffers a bit from being an awkward hybrid between an infinity engine game and a more action-oriented game. It was a rough time for RPGs in general in that respect. ME2 and 3 lean more in to the action game play for better and worse (mostly better).

    Unless you are in hurry to get on to the next game, I’d encourage you to do some of the optional and very easy to miss sidequests that you can get from exploring planets. Its worth checking the wiki for these if you don’t feel like doing enough exploring to stumble across them organically, I can in particular recommend the Cerberus quest chain and Talis geth quest chain.



  • It can be hard to bootstrap yourself up from zero followers. I’d recommend posting something just so that people have an idea of the kind of thing they can expect if they follow you from checking out your profile. But you probably won’t get much engagement from your own posts at first, so it will probably be more fun to just reply to other accounts.

    Bluesky has a feature where you can set up customized feeds to filter for any kind of content you want. The person who saw your post might have seen it in the “newskies” feed which just contains every first post that any account makes for example. So one way to get engagement can be to write posts that show up in a certain feed that people follow, like there exist some feeds that are based around certain topics that usually trigger based on your post containing certain keywords. Most people just use the following feed though, I think.







  • I’m a bit skeptical that a borrow checker in C++ can be as powerful as in rust, since C++ doesn’t have lifetime annotations. Without lifetime annotations, you have to do a whole program analysis to get the equivalent checks which isn’t even possible if you’re e.g. loading dynamic libraries, and prohibitively slow otherwise. Without that you can only really do local analysis which is of course good but not that powerful.

    Lifetime annotations in the type system is the right call, since it allows library authors to impose invariants related to ownership on their consumers. I doubt C++ will add it to their typesystem though.