• 8 Posts
  • 598 Comments
Joined 11 months ago
cake
Cake day: November 12th, 2024

help-circle






  • Googling and finding these options

    Well, it’s not in that bad a condition.
    All options (hopefully, because I didn’t check) that are applicable to any version of rustfmt are available using rustfmt --print-config default and you only need to use the internet in case you either did not understand the option from the name or if you are looking for an option not in your specific version.

    It should have been as a configuration enforced as standard for every contributor.

    That was most probably just another instance of oversight, I’d say.
    The one determining which configuration went into the formatting configuration (or the one making the default one, in case there was no config file for the Linux project), might have just not thought of that particular implication of the option been set.





  • Because rustfmt does not have enough proper customisations.

    I just started Rust a few days ago and after my code became >20 lines (following the docs, understanding the basics), I decided to look for a formatting tool for Rust.
    I found out rustfmt, read :

    Rustfmt is designed to be very configurable. You can create a TOML file called rustfmt.toml or .rustfmt.toml

    and was kinda happy.

    And since in cmake I use BreakBeforeBraces: Allman, I looked for a similar option.
    Found out in the docs, it was not available in stable. inner-thoughts: How old is Rust? I already waited 4+ years before picking it up. Well, let’s look up the unstable features on GitHub.
    There are 2 configuration options relevant to the functionality.
    Both of them have enough parts where they don’t work, so they are useless even if I were to use the unstable version of rustfmt.
    And it seems like either none of the people participating in that issue is good enough to make changes in its source code or the rustfmt team doesn’t want that feature implemented.


    And if someone requires a reason for Allman style for BreakBeforeBraces:
    The Allman style makes it much easier to identify block scopes without having to rely upon IDE features such as highlighting.






  • No, pacman -S firefox will not update your firefox.

    pacman -Sy firefox will update your firefox and nothing else.

    If you have done pacman -Sy once, then your list of packages and their versions gets updated.
    From then on, using pacman -S <package> on any package, whether or not it was already installed, will now get the new version of it.

    On the other hand, if you have not updated for long, then if you run pacman -Su to update, it will update nothing, because it looks at the old package list and compares it to installed packages and all of them match.
    If you were to use pacman -Sy and then pacman -Su, then it would do the update, similar to pacman -Syu.
    If you did pacman -Sy yesterday and then do pacman -Su today, then it will update up to yesterday’s packages and will ignore any updates from that point to today.

    This can be considered analogous to apt update and apt upgrade.
    If you run apt upgrade without apt update, you only upgrade upto the packages that you got until the last apt update.


    If arch used apt, then in this case, the recommendation would be to never use apt update without using apt upgrade right after it.


  • I am comparing a 10 year old version of Office on Windows 10 with a version of LibreOffice I used in the same week on that same computer on Linux.

    My conclusion of “Office has gotten worse” comes from comparing the ability of MS Office 2015 on Win 10 on a Laptop with Core i7 6700H with 8GB DDR4 RAM vs MS Office 2007 on Windows 7 on a Core2Quad with 4GB DDR2 RAM (oh and an old SATA2 HDD here vs SATA3 7200RPM HDD on the laptop) and observing that they are able to open about the same amount of files before starting to hang.
    In fact, at that time, I decided to use the old Desktop PC for that particular work, because it was working better in general and was more productive despite me having to keep it off the internet.


    I am no longer making that comparison, because I don’t use MS Office on my PC any more.

    But I can say this, if I were making that comparison of LibreOffice of that time with MS Office 2007 (which would actually be much older), then LibreOffice would have lost.


    No one should have 8GB of RAM in their pc in 2025 either

    And guess what saved my old 4GB DDR2 computer from becoming e-waste, making me still be able to use it when I want?
    KDE Plasma. Yes, it works well on a system which I wouldn’t even dare try installing Windows 10.


  • No, LibreOffice is way better nowadays.

    And that is mainly thanks to MS Office having gotten way worse than before.

    There is a long standing problem where LibreOffice becomes very slow when adding images. That hasn’t been fixed, last I checked.
    But thanks to MS Office now being slow all the time and also taking up way too much RAM, meaning that opening 4-5 Word+Excel documents on 8GB RAM means you are constantly using the page file (my exp. with Office 2015 back then), LibreOffice’s problem is not a big deal any more.

    Your experience might not match what I am saying, because I am comparing MS Office on Windows vs LibreOffice on Linux.


  • The differences can largely be mitigated at the operating system level.

    Exactly. And that also means that they have to be mitigated at the OS level and in this case, the kernel level.
    It would usually be fine if the system had nothing other than RAM and fixed storage, but anything else (as simple as keyboard drivers and stuff) and you will need to make the program accordingly. Maybe even SATA would require handling endianness.

    Honestly, I thought that they already handled endianness, due to how many different things Linux works on.
    But if it doesn’t then I don’t see there being much of a requirement.

    For networking devices and such, I’d rather favour more customised solutions either way.