• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: July 18th, 2023

help-circle


  • It’s been almost a decade since I used C++ and had to verify, but after some quick searching around it looks like it hasn’t changed a ton since I last looked at it.

    You can use smart pointers, and certainly you should, but it’s a whole extra thing tacked on to the language and the compiler doesn’t consider it an issue if you don’t use them. Using new in C++ isn’t like using unsafe in rust; in rust your code is almost certainly safe unless marked otherwise, whereas in C++ it may or may not be managed properly unless you explicitly mark a pointer as smart.

    For your own code in new codebases this is probably fine. You can just always make your pointers smart. When you’re relying on code from other people, some of which has been around for many years and has been written by people you’ve never heard of, it becomes harder to be sure everything is being done properly at every point, and that’s where many of these issues come into play.


  • C and C++ require more manual management of memory, and their compilers are unable to let you know about a lot of cases where you’re managing memory improperly. This often causes bugs, memory leaks, and security issues.

    Safer languages manage the memory for you, or at least are able to track memory usage to ensure you don’t run into problems. Rust is the poster boy for this lately; if you’re writing code that has potential issues with memory management, the compiler will consider that an error unless you specifically mark that section of code as unsafe.


  • Honestly? Bash. I tried a bunch a few years back and eventually settled back on bash.

    Fish was really nice in a lot of ways, but the incompatibilities with normal POSIX workflows threw me off regularly. The tradeoff ended up with me moving off of it.

    I liked the extensibility of zsh, except that I found it would get slow with only a few bits from ohmyzsh installed. My terminal did cool things but too slowly for me to find it acceptable.

    Dash was the opposite, too feature light for me to be able to use efficiently. It didn’t even have tab completion. I suffered that week.

    Bash sits in a middle ground of usability, performance, and extensibility that just works for me. It has enough features to work well out of the box, I can add enough in my bashrc to ease some workflows for myself, and it’s basically instantaneous when I open a terminal or run simple commands.






  • Ruff is super nice, the speed increase means that I no need to wait a second after saving a file to make sure my linter or formatter don’t confuse me.

    Python packaging is kind of a mess where each tool that solves a problem also feels like it bogs down the process. It doesn’t help that I need multiple tools to manage both my python and package versions. It sounds like uv isn’t far enough along for me to bother with yet, but it also has a goal and team behind it that make me optimistic that this isn’t just another packager to throw on the pile.


  • I’ve been using Obsidian lately. Proprietary with an open plugin ecosystem. Works well, makes it easy for me to integrate with other notes and such, but I haven’t figured out a good workflow for exporting work for submission. That said, it’s all markdown and there are lots of plugins for stuff like that, so it’s probably mostly just that I haven’t tried very hard.

    In the past I’ve used Google Docs (proprietary), Scrivener (proprietary), Manuskript (open), Zim (open), and probably a few I’m forgetting. Really it just comes down to what you’re looking for out of the software, there are lots of options.

    The biggest thing to keep in mind from a self-hosting perspective is local storage and easy backups under your own control. I use syncthing to keep my whole Obsidian vault synced across a few devices; for some software that’s easier or harder due to file formats and accessibility.