NatoBoram

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.

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.

"An ex-Netflix engineer's take on piracy; in a YouTube drama near you"

Dang, I'm not even sure if I implemented the cake symbol in my Lemmy client

For anyone who has to install Windows 11; download the full ISO then use Rufus. You'll be able to disable some of the enshittification.

So hard to understand ><

Your "minimum wage" link states multiple times that it is only for federal employees, not for the general population. There are still states where you can get less than 10$/h.

Trying to find good subs

Clients can work around it by making a search on the home instance that filters by community id and submitter id. Something like this.

You can't have content addressing because it's mutable. On the other hand, UUIDs are made for that. There's even multiple types of UUIDs made for distributed computing with namespaces and such.

Amazing. One feature that is desperately needed on Lemmy is to open a post in another instance, not just a community or a user.

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.