Skip Navigation

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/)ST
Posts
2
Comments
114
Joined
2 yr. ago

  • If the DuckDuckGo result for your search doesn't yield anything then just append it with g! and it'll take you straight to the Google results.

    It's a useful trick but very rarely do I find I need it. Only really when researching a very specific error.

  • You don't have to look at reducing your Google use as a monumental effort. You can slowly transfer, minimise the number of services you use.

    Simple - Switch your default search provider to Duck Duck Go.

    Easy - Switch to Firefox

    Mid - export your documents from Google Drive

    Complex - Transfer your primary email to another provider.

  • Has GitHub actually done anything negative? Your comments really just sound like fear mongering, I can't see any actual issues.

    What is the bloat you're referring to? The UI is clean and simple. Navigating and searching code is intuitive. The issue tracker is basic but reliable. Releases are clear. GitHub Actions are complex but featureful and incredibly useful. GitHub Packages are basic but useful. GitHub Copilot is damn impressive.

  • C# is a superb language, it's a shame it's not used more often for open source projects.

    The only argument people seem to have against it is that it's maintained by Microsoft - which apparently is the worst thing imagineable. The reality is the Microsoft of today is very different to people's pre-conceived image. They've done a fantastic job with C# and .NET.

    .NET has the best documentation of any language I've worked with, it makes life so much easier.

  • I've only read the headline and first paragraph but... I already think there's this is flawed.

    It's treating the symptom rather than the problem. Really we need to be standardising how applications are configured. Standardise the command line arguments, add logical defaults. Pick a single configuration format and a centralised location where is defined.

    This is one reason I favour docker compose for running apps. Everything is configured through a docker-compose.yml file.

  • The truth is I would buy it...

    I've been following cableporn for a very long time and I still don't really know why things I set up as they are. I have intricate knowledge of the software side of things but hardware is alien to me. By playing around with it as a game I'd finally grasp the concepts.

  • You should consider who your audience is, are they all CLI experts familiar with the difference in syntax? That seems unlikely.

    I'd always write documentation in a way that's accessible to most users. The difference between $ and # syntax is highly esoteric.

    sudo on the other hand is familiar to almost everyone. It's one of the first things mentioned in beginners guides.

    I wouldn't even prefix your commands with $ as an experienced user is quite likely to include that when copying the command.

    A lot of people are citing the arch wiki as a standard that uses # but isn't the entire meme around arch that its a notably complex system?