Nato Boram

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”

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.

It’s still like that with programming languages like Go and Rust. Job offers are exclusively for senior staff engineers with 5 years of language-specific experience.

It’s already happening on Pixiv…

Steam Controller! Excellent idea!

… or just use Rust?

It’s a better foot-gun, that’s for sure

For the Nexus 7, you might want to download its LineageOS build before it’s lost to time:

• https://download.lineageos.org/devices/debx/builds
• https://download.lineageos.org/devices/flox/builds

It’s on Android 11, a huge jump from its last official build on Android 6.0.1.

And to be fair, this is the reason to get a Google device.

You know already that all Android manufacturers are assholes and will use planned obsolescence to make you buy a new device, including Google. You can plan accordingly by getting one that can be easily flashed and flashed back to stock in case of problems. That leaves you with one single Android manufacturer: Google.

And with this in mind, a device that lasted from Android 4.3 (2012) to Android 11 (2021), or 9 years… that’s pretty damn good.

Usage: ./malware [OPTIONS]

Options:
  -h, --help            Display this help message and exit.
  -i, --infect          Infect target system with payload.
  -s, --spread          Spread malware to vulnerable hosts.
  -c, --configure       Configure malware settings interactively.
  -o, --output [FILE]   Save log output to a file.
  -q, --quiet           Quiet mode - suppress non-critical output.

Advanced Options:
  -a, --activate [CODE] Activate advanced features with code.
  -b, --backdoor [PORT] Open backdoor on specified port.
  -m, --mutate          Evade detection by mutating code.

Description:
  Malware toolkit for educational purposes only.
  Use responsibly on authorized systems.

Examples:
  ./malware -i                  Infect local system with default payload.
  ./malware -i -s               Infect and spread to other systems.
  ./malware -a ACTCODE -b 1337  Activate advanced features and open backdoor.
  ./malware -q -o output.log    Run quietly, save logs to 'output.log'.

Except that you should use Prettier for formatting instead of ESLint. That said, semicolons are useless noise

Should’ve written the malware in Go, smh

Ok, thank you for your time.

GitHub’s actions are so good once it clicks and you understand them. On GitLab, you start from a docker image, so it’s harder to setup some things but easier for others. If you are very good at docker and don’t mind making your own images just for CI purposes, then go ahead.

Ideally, you should just try them both. You can mirror a project between the two and setup the CI at both places.

You can also use GitHub as a mirror to make your project more discoverable

It did, but the interface is still dogshit for new users and it’s impossible to know how to access a project’s page or its download page. When I started using GitHub, I didn’t even realize that SourceForge was a git hub for a fucking while, yet I was still downloading stuff from there.

Wish there was a first-party clipboard manager in GNOME so I don’t have to hunt for an extension