folkrav

  • 0 Posts
  • 812 Comments
Joined 2 years ago
cake
Cake day: July 25th, 2023

help-circle






  • A “server” is just a remote computer “serving” you stuff, after all. Although, if you have stuff you would have trouble setting up again from scratch, I’d recommend you look into making at least these parts of your setup repeatable, be it something fancy ala Ansible, or even just a couple of bash scripts to install the correct packages and backing up your configs.

    Once you’re in this mindset and take this approach by default, changing machines becomes a lot less daunting in general. A new personal machine takes me about an hour to setup, preparing the USB included.

    If it’s stuff you don’t care about losing, ignore everything I just said. But if you do care about it, I’d slowly start by giving from the most to least critical parts. There’s no better time to do it than when things are working well haha!




  • Tramp is more featured, but if all one cares about is being able to edit remote files using a local editor, vim can edit remote files with scp too: scp://user@server[:port]//remote/file.txt

    I tried tramp-mode at some point, but I seem to remember some gotchas with LSP and pretty bleh latency, which didn’t make it all that useful to me… But I admittedly didn’t spend much time in emacs land.


  • folkravtoCanadaNews Organizations.
    link
    fedilink
    arrow-up
    13
    ·
    edit-2
    16 days ago

    I’d be curious as to what you consider to be Canadian “leftist” media. I would love not to have this preconception, but let me guess - you consider the PLC to be left leaning.


  • folkravtoAsklemmy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    1
    ·
    17 days ago

    Eh, I’m about the same age as OP, I don’t have to get to 50 to know that I’d take my parents’ economic context over the two crashes. The rest… For many reasons, if medicine does some miraculous leap forward by then, maybe I’ll still wish I got a lot more left to go by then.




  • Really bigger updates obviously require a major version bump to signify to users that there is potential stability or breakage issues expected.

    If your software is following semver, not necessarily. It only requires a major version bump if a change is breaking backwards compatibility. You can have very big minor releases and tiny major releases.

    there was more time for people to run pre-release versions if they are adventurous and thus there is better testing

    Again, by experience, this is assuming a lot.


  • From experience shipping releases, “bigger updates” and “more tested” are more or less antithetical. The testing surface area tends to grow exponentially with the amount of features you ship with a given release, to the point I tend to see small, regular releases, as a better sign of stability.