• 0 Posts
  • 70 Comments
Joined 2 years ago
cake
Cake day: November 23rd, 2023

help-circle







  • I love that FreeCAD exists and use it often, but I really hate how much you have to “fight” the UI. I even briefly considered learning OpenSCAD out of frustration with the ui and the toponaming problem (before realizing that switching to OpenSCAD would just shift my frustration onto Javascript fuckery).

    Now that the latter is fixed, though, I have just forced myself to forget how to do things the “normal” CAD way (i.e. using patterns and flows that most other software has standardized around) and instead how to do them the FreeCAD way.

    I hope at some point we get an overhaul of the UX, but in the meantime I’ll grin and bear it since I have yet to find an even remotely comparable F/OSS CAD software that works the same on both Linux and Windows.



  • I can attest to projectivy and smarttube, they are great. I went with the internet’s recommendation on the $20 Walmart/onn Google tv 4k box, with projectivy as the launcher instead of the default.

    My only gripe so far is that the remote doesn’t seem to consistently turn the box on, I have to go unplug the box every so often to reset it. probably some misconfiguration that’s making it not wake from sleep correctly.

    Despite that issue, 10/10 experience: ad free YouTube, fast jellyfin in 4k, fully customizable ui…








  • No. Symlinks and hardlinks are two approaches to creating a “pointer to a file.” They are quite different in implementation, but at the high level:

    • Symlinks can point to other filesystems, hardlinks only work on the same filesystem.
    • You can delete the target of a symlink (or even create one that points at nothing), but a hardlink always points to a real file.

    In both cases, the only additional data used is the metadata used for the link itself. The contents of the file on disk are not copied.




  • No, but you’ll have much more overhead. I have a VM that hosts all Docker deployments which don’t need much disk space (most of them)

    This is a big point. One of the key advantages of docker is the layering and the fact that you can build up a pretty sizeable stack of isolated services based on the same set of core OS layers, which means significant disk space savings.

    Sure, 200-700MB for a stack of core layers seems small but multiply that by a lot of containers and it adds up.