Yes! I went to a meditation class once, and thought to my self "huh, this is just like long distance running but without the exersice". I'll stick to running. 😆

This one really affected me. It's one of the first images from the surface of Mars. I was quite young, and it clicked in me that other planets actually exists and are out there in space.

Call me autistic, but does this need to be an image? It uses like 10 000 bytes to say what 100 bytes would say in text. :P

A life hack is that you don't have to answer what I would perseive as an aggressive phone call. Stand you ground and keep the communication in you preferred way.

Not sure how to interpret this. The use of any tool can be for good or bad.

If the quality of the game is increased by the use of AI, I'm all for it. If it's used to generate a generic mess, it's probably not going to be interesting enough for me to notice it's existence.

If they mean that they don't use AI to generate art and voice over, I guess it can be good for a medium to large game. But if using AI means it gets made at all, that's better no?

Ha, I was thinking this is a perfect llm question so I tried. And I was right.

Great questions! Let's break down the differences between GitHub, GitLab, and Forgejo, and address your specific queries.

Overview

1. GitHub:

   • Company: GitHub, Inc. (owned by Microsoft since 2018).
   • Software: GitHub is a proprietary platform. The software running GitHub.com is not open-source.
   • Primary Use: Hosting Git repositories, collaboration, CI/CD, project management, and more.

2. GitLab:

   • Company: GitLab Inc.
   • Software: GitLab is an open-core platform, meaning the core functionality is open-source (GitLab Community Edition), but there are proprietary features in the Enterprise Edition.
   • Primary Use: Similar to GitHub, but with a stronger emphasis on CI/CD and DevOps.

3. Forgejo:

   • Software: Forgejo is a fork of Gitea, which is a lightweight, open-source Git service.
   • Primary Use: Self-hosted Git repository management with a focus on simplicity and community-driven development.

Detailed Differences

Software Used by GitHub

GitHub.com uses proprietary software developed by GitHub, Inc. The exact details of their software stack are not publicly available, but it is known to be highly customized and optimized for their scale.

Pros and Cons

GitHub:

• Pros:
  • Largest user base, making it the de facto standard for open-source projects.
  • Extensive integrations with third-party services.
  • Robust features for collaboration, including Issues, Pull Requests, and Actions (CI/CD).
• Cons:
  • Proprietary software, so you cannot self-host it.
  • Limited customization compared to open-source alternatives.

GitLab:

• Pros:
  • Open-source core (Community Edition).
  • Comprehensive DevOps lifecycle support, including CI/CD, monitoring, and security.
  • Can be self-hosted.
• Cons:
  • Can be resource-intensive to self-host.
  • Some advanced features are only available in the Enterprise Edition.

Forgejo:

• Pros:
  • Fully open-source and community-driven.
  • Lightweight and easy to self-host.
  • Simple and user-friendly interface.
• Cons:
  • Smaller ecosystem compared to GitHub and GitLab.
  • Fewer built-in features for CI/CD and DevOps.

Self-Hosting

GitHub:

• Self-Hosting: Not possible. GitHub is a cloud service only.

GitLab:

• Self-Hosting: Yes, GitLab offers both a cloud service (GitLab.com) and self-hosted options. You can download and install GitLab Community Edition or Enterprise Edition on your own infrastructure.

Forgejo:

• Self-Hosting: Yes, Forgejo is designed to be self-hosted. It is lightweight and can be run on modest hardware.

Preferences

• For Open-Source Projects: GitHub is often preferred due to its large community and visibility.
• For DevOps and CI/CD: GitLab is a strong choice due to its comprehensive feature set.
• For Lightweight Self-Hosting: Forgejo (or Gitea) is ideal if you need a simple, self-hosted Git service without the overhead of more complex platforms.

Conclusion

Each platform has its strengths and is suited to different use cases. GitHub is great for visibility and collaboration, GitLab excels in DevOps and CI/CD, and Forgejo is perfect for lightweight, self-hosted Git management. Your choice will depend on your specific needs, whether it's community size, feature set, or the ability to self-host.

!

Right?! I've just assumed the GNU/Linux nitpick to be a meme at this point. An old and tired one at that...

You expect a different outcome every morning?

I've done this with debian in the past, you just install different DE in parallel. Works well enough, don't remember it causing any issues. It just makes a mess of your home folder, so I don't do it outside of testing purposes.

I think it's due to single sign on (SSO) or other means of authentication (OAUTH), which is convenient when used.

But I agree, annoying if you use username and password.

I actually built my own 2 kWh battery setup after finding available commercial UPS overpriced.

It took some work and cost me about 2000 euro, but now I run everything (including networking, servers and monitor) directly on a battery feed DC net in my house.

It's pretty cool too have all IT equipment unaffected by a power outage.