Skip Navigation

User banner
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)U

ulterno

@ ulterno @programming.dev

Posts
7
Comments
1235
Joined
2 yr. ago

"then" is used to depict time, sequence or a causal relationship. "than" is used with comparative adjectives, to depict comparison.

  • The Original Sin of Computing...that no one can fix

    Jump

  • This problem gives the best hugs!

    Jump

  • You need a python expert with experience in not-breaking-stuff.

  • The illegible nature of software development talent

    Jump

  • Thanks.Never would have thought to look for hardware, with the name VAX had I not read that.ycombinator seems like another interesting place.

  • The illegible nature of software development talent

    Jump

  • Unfortunately that's not good enough for my OCD brain.

  • The illegible nature of software development talent

    Jump

  • What's "Three pounds of VAX!" ?

  • People are complaining about rustfmt, but it is effectively unmaintained

    Jump

  • I considered that (talking about clang-format here, not rustfmt), but there are cases where some files are formatted while others are not, such that, you can't go around formatting the whole project to your liking and then expect it to return to the same, once you go back to the project's configuration, for committing.

    Here, the difference between clang-format and rustfmt comes up, because unlike clang-format, which has the required configurations, rustfmt does not have the configuration I require. The little part that is there, has not been fully implemented and a lot of the configuration hasn't even been defined.Meaning that even if I were to put the time into contributing to rustfmt, I will soon reach a point where I will have to be setting up groundwork. That's where I will fail, because I am too new to Rust to be able to define formatting for undecided conditions, many of which I don't even know about yet.

  • People are complaining about rustfmt, but it is effectively unmaintained

    Jump

  • I mean the clang-format in KDE code.I work with it, I don't like it, but I like KDE, so I put up with the formatting that I don't like.

  • People are complaining about rustfmt, but it is effectively unmaintained

    Jump

  • Neither do I, but I don't like the KDE formatting either, so it doesn't really matter as much.

  • Well well well.

    Jump

  • Until the user-based authorisation system of the server puts you in place.

  • So how is it going South Korea?

    Jump

  • Ironically, the Govt. official is a resource they have enough backups for.

    Can this now go to darkhumor@lemmy.world ?

  • Linus Torvalds Vents Over "Completely Crazy Rust Format Checking"

    Jump

  • You mean, "stop using nice and spicy original content made by a popular person, to create high ROI articles"?In this world when you could have an article when <insert movie-actor/singer name here> sneezes in front of the camera, why would someone not capitalise on someone putting years of past experience and thought into writing an essay?

  • Linus Torvalds Vents Over "Completely Crazy Rust Format Checking"

    Jump

  • 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.

  • Vibe Coding

    Jump

  • And then you find yourself on a journey to the centre of the Earth.

  • Vibe Coding

    Jump

  • That's nice.Although I don't understand how come an Architects drawing goes straight to a builder without a Civil Engineer in between.

  • Vibe Coding

    Jump

  • Well, if it were at a gap, as would be expected of a normal staircase, it would have enough space for the door to open and for someone to enter it from the side.

    I would not want to live in that room either way.

  • Linus Torvalds Vents Over "Completely Crazy Rust Format Checking"

    Jump

  • 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.

  • How We're Designing Audacity for the Future

    Jump

  • I used Audacity every now and then and while I wasn't very good at it before either, the changes over time, ended up jarring me now and then. Only after watching this, do I realise what was going on:

    • They removed the easily visible audio device selection
      • Instead of going into audio setup, I ended up right-clicking the thingy in the left of audio track and checking out the arrow-like buttons, hoping for some menu item to pop-up that would give per-track I/O device selection
    • They broke stuff down into clips
      • I was looking for how to "flatten" those things, because I wanted to select past the boundaries. After a while of trying, I realised I could just do so as-is

    Those were my faults as a user, coming up from the changes.

    Now come my little thoughts on Tantacrul's ideas:

    Modes

    They are not a real problem as long as the user knows what to expect. You just need to implement some basics:

    • These will apply to both, Audacity and a 2D + 3D CAD software
      • Have a default mode, that would be mostly about selection and moving around the viewport.
        • In this mode, right-clicking on a viewport item can open a menu showing options to show item properties of actions that would work on that specific item (the actions might change the mode).
        • Note that in this mode, accidental click and drag should not cause any change that would require the user to Ctrl+Z.
      • Always start the program with the default mode active
      • Whenever the user presses Esc with the viewport in focus, switch to the default mode.
        • If some extra (non-permanent) side-panel (or bottom panel) was opened, or if some object was selected in this mode, Esc should do these in order:
          1. Close side-panels, one for every Esc key pressed
          2. Deselect all objects on one Esc
          3. Switch to the default mode on the last Esc
          4. In case the user has made an unconfirmed change, that might be lost (or implicitly applied) on exiting the other mode, prompt.
        • This should give the user a feeling that no matter what state they are in, as long as the press Esc enough times, they will find themselves in the base state of whichever view they are in.
          • And since I don't have a degree in UI/UX design, to prove that I'm not pulling this out of a faecal dump, here are some examples that do similar stuff: Qt Creator, Inkscape, AutoCAD (ok I'm not sure if this one does, I just vaguely remember), Kate (the side/bottom-panel stuff). Oh, and vim
    • For the zoom behaviour, this should work specifically for Audacity:
      • Use scroll-wheel with keyboard modifiers (that is what I originally tried to use when I first used Audacity)
        • Normal scroll wheel to just scrolls through the track
        • Ctrl+Scroll for horizontal Zoom
        • Shift+Scroll for vertical pan (in case the vertical zoom has caused exceeding of bounds)
        • Ctrl+Shift+Scroll for vertical Zoom
      • Alternative zoom mode which just scales the track using mouse click-grab + drag
        1. User clicks on a position in the track-viewport | Set that position as an anchor point. If the position is close enough (upto 5 pixels maybe) to the vertical centre, set the centre as the anchor point.
        2. User drags the mouse horizontally | horizontal zoom, the anchor point as the centre
        3. User drags the mouse vertically | vertical zoom, the anchor point as the centre
        • You may call this mode, "Scale Viewport" or sth similar.

    Audio setup

    If Audacity can end up with functionality to record multiple tracks at once, then put the audio setup in a menu connected to each track.

    Of course I haven't used Audacity 4 yet and I'm just on whatever Arch is shipping rn. So maybe they already have something better.But relative to what I see, the above UX would be more desirable.

  • Escaping a string when passing through multiple tools

    Jump

  • Now say the CLI tool is passed a string that has "-arg1-" inside it.

  • Austria's Armed Forces Gets Rid of Microsoft Office (Mostly) for LibreOffice

    Jump

  • 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.