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

help-circle

  • It should be offered as an option really.

    One caveat is that you need to think ahead about how much space you want to assign to each partition. You could end up with your /home/ partition being full while the system partition still has plenty. Or vice versa. You can manually readjust the boundaries but it requires some understanding and can’t be done on the fly by a non-technical user. By contrast if everything’s stored on the same partition you never have to worry about this.

    You can, by the way, manually recreate this set up even after the initial set up although it will require lots of free space to shuffle around files (or some external storage to temporarily hold them). Basically what you do is create a new empty partition, copy all your /home/stuff there and then configure your system to always mount that partition as the /home/ directory when it boots. Files are just files after all and the operating system doesn’t really care where they come from as long as the content is correct. Once you got it working you can delete the originals and free up the space to be used otherwise.


  • Typically your personal files and app settings are stored somewhere in your user home folder, eg under /home/bob/. Ideally you’ve set up your system in a way so that the entire /home/ folder is stored on its own disk or partition at least. That let’s you boot up a different distro while using the same home directory. But even if you haven’t set it up separately from the rest of the system, you can still manually copy all those files.

    Not every single application setting is transferable between distros as they sometimes use different versions but generally it works well. Many apps also let you manually export profiles or settings and reimport them elsewhere later. Or they have online synchronization baked in.



  • Good point.

    I guess just having a staggered temporal restriction is fine, don’t need to wait until you retire necessarily. You would still receive a portion of your salary package in the form of classic currency and plenty for a good life too. An example could look like this and I’m obviously making up the percentages and durations here, they would need to be fine tuned:

    • 40% of salary as cash
    • 10% of salary as stocks that can’t be sold within 6 months
    • 10% of salary as stocks that can’t be sold within 12 months
    • 10% of salary as stocks that can’t be sold within 18 months
    • 10% of salary as stocks that can’t be sold within 24 months
    • 10% of salary as stocks that can’t be sold within 30 months
    • 10% of salary as stocks that can’t be sold within 36 months




  • It’s so dumb that JSON doesn’t officially have comments.

    So much this.

    Used to work at a company where I sometimes had to manually edit the configuration of devices which were written and read in JSON. Super inconvenient if you have to document all changes externally. As a “hack” I would sometimes add extra objects to store strings (the comments). But that’s super dicey as you don’t know if it somehow breaks the parsing. You’re also not guaranteed the order of objects so if the configuration gets read, edited and rewritten your comment might no longer be above/below the change you made.

    Always found it baffling that such a basic feature is missing from a spec that is supposed to cover a broad range of use cases.