Nato Boram

  • 2 Posts
  • 127 Comments
Joined 1 year ago
cake
Cake day: July 28th, 2023

help-circle
  • Nato BoramtoLinux@lemmy.mlWhich CLI app/utility you wish there was a GUI for?
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    2 months ago

    That UI is called VSCode

    At the top of your .yaml file, you can set a JSON Schema. Example:

    # yaml-language-server: $schema=https://json.schemastore.org/prometheus.json
    
    scrape_configs:
      - job_name: caddy
        static_configs:
          - targets:
              - caddy:2019
    

    This way, you don’t have to memorize every possible setting and what it does and risk making a typo in the config. VSCode will just tell you.


  • Nato BoramtoProgramming@programming.devDo you use VS Code?
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    2 months ago

    What’s even the point then?

    The point is that you can enable each separate extension you want running on your code editor or uninstall them if you’re unsatisfied. This makes it as light as you want it to be - or as heavy as you need it to.

    I was doing fine with just vim and tmux

    VSCode is like vim without vim controls and in a browser. Seen that way, it makes more sense. With Vim, you have to hunt for obscure Github repositories and follow arcane installation instructions for hidden extensions that you may or may not need and you have to learn a whole-ass keyboard-shortcut-based programming language just to use any of it.

    With VSCode, you click on Extensions, search what you want and it’ll probably be there unless it’s a toxic ecosystem like PHP/C# or some niche ecosystem that no one heard about.











  • Well, that reminds me that Mastodon has huge, unresolved problems, such as tags being part of the post’s body like Twitter rather than being a separate field like Tumblr.

    Reading tweets with a hundred hashtags at the bottom seem really thirsty for attention, which is bad because Mastodon wants to fundamentally work with these, yet doesn’t have good in-post integration for them. It makes interactions less genuine, more performative.

    Rome wasn’t built in a day, and Mastodon won’t be good tomorrow either. In the meantime, you can vote to make it better on https://github.com/mastodon/mastodon/issues/10743.




  • Nato BoramtoLinux@lemmy.mlLaptop Recommendation for Light Gaming
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    4 months ago

    The issue with gaming on laptops is that you’ll need to spend at least 1200$ at the bare minimum to play anything and 1600$ to have a good experience. And even then, the laptop is pretty much disposable and will be severely outdated in 5 years.

    The best option for a laptop would be the Framework Laptop, but these can go for 3000$. The big advantage is that they’re worth every penny as they are upgradable. You can literally swap every part, including the motherboard. The aftermarket value for these laptops is going to be amazing.


  • Tumblr is a blogging experience that’s similar to Twitter, but more focused on the user itself than on the central feed.

    • You have your blogs and you post there. Yes, you can have many blogs.
    • There’s global feeds with posts from all users, potentially including yours.
    • Posts can have non-intrusive hashtags, meaning they are not #partOfThePost, but in a separate, smaller, dedicated section of the post.
    • You can’t post stuff to someone else’s blog, but you can comment on their posts. Comments are tiny next to the post.
    • You can quote posts, but that makes a duplicate in a blockquote rather than linking to the original post like Twitter




  • Yep. And clients would be able to participate to the seeding.

    Servers software developers would still have a massive amount of work to do to implement IPFS integration, but it’s doable. IPFS also has work to do here to make IPFS work natively with cloud storage protocols (like Amazon S3), but it already exists.

    One issue with open source software is that you often have to pick the least-effort solution to avoid burning out your free labour. Free time is limited, and if IPFS takes slightly too much work to add, then it’s off the table.