So it really is that simple: a small bash script, building locally, rsync'ing the changes, and restarting the service. It's just the bare essentials of a deployment. That's how I deploy in 10 seconds.

I'm strongly opposed to local builds on any semi-important or semi-complex production product or system.

Tagged CI release builds give you a lot of important guarantees involved in release concerns.

I'll take the fresh checkout and release build time cost for those consistency and versioned source state guarantees.

It's been over 10 years since we released Rogue Legacy 1, and in the pursuit of sharing knowledge, we are officially releasing the source code to the public.

https://github.com/flibitijibibo/RogueLegacy1/

License head

Rogue Legacy 1's source code is made available under a custom license. Basically, you can compile yourself a copy, for free, for personal use. But if you want to distribute a compiled version of the game, you might need permission first. See the EXCEPTIONS.md page for more information.

What is Tails?

and Tails, a portable operating system that uses Tor

If you only care about contributing improvements, no, it doesn't matter.

If you want to at least be recognized as an author, and be able to say "I made this", the license opposes that.

Waiver of Rights: You waive any rights to claim authorship of the contributions […]

I don't know how they intend to accept contributions though. I guess code blocks in tickets or patch files? Forking is not allowed, so the typical fork + branch + create a pull request does not work.

I wish standards were always open access. Not behind a 600 dollar paywall.

When it is paywalled I'm irritated it's even called a standard.

TOML instead of YAML or JSON for configuration.

YAML is complex and has security concerns most people are not aware of.

JSON works, but the block quoting and indenting is a lot of noise for a simple category key value format.

What do you mean by professional?

Be paid, even if really bad, and a net negative for the projects and companies you're involved with? Then it's certainly possible.

That's a whole lot of assumptions, and cascading of them.

Gender-neutral is a factual, grammatical term. How do you call it if not that? The first PR in that case was rather neutral and not presumptuous or critical. It was a suggested improvement. But they made it [more] political by calling it political. And then denied it - which is inherently taking a political position.

Did you stop programming altogether? /s

I think you can potentially get stuck with worse when you stop Java.

Webcrawlers count as users too, right?

This article is much the same if we replace “Discord” with “GitHub”, for instance, or “Twitter” or “YouTube”.

There is a fundamental difference between what they listed as one though: GitHub and YouTube are open to read and access and download and clone. Discord and Twitter are not.

I have much more of an issue with Discord than I have with GitHub or YouTube. Both GitHub and YouTube have free access, and host the largest part of the relevant userbase (synergy effect of having an account).

It's certainly worth discussing in project teams, but personally, I'd never leave GitHub in the current ecosystem for a niche product or platform - if I want contributors and collaborators or visibility. The vast majority of users already know GitHub and most accounts are on GitHub. That can't be said for niche platforms or self-hosted alternatives, which introduce barriers.

Before GitHub Sourceforge was somewhat similar. It was a proprietary but open platform. In a project I participated in (Mumble) it was reasonable enough (no more complicated than between any other platforms) to make the switch to GitHub. I see todays GitHub the same way. As long as it remains so primary prevalent and open to free access it's good enough, and when it goes downhill it's easy enough to switch away to a better alternative.

I'm still fond of alternative FOSS platforms, that they exist and evolve, and maybe easier account creation, synchronization, or federation will make them real alternatives. But for now, they are niche. Which of course doesn't mean niche is unviable or an alternative. But even as an invested and interested FOSS developer, user, and collaborator they're barriers to me. Which makes it obvious to me it's even moreso for less invested people.

Memory safety issues were a thing even before bootcamps and "bootcamp culture".

Even if you fix expertise, intention, and mindset - the entire workfield environment and it's people - mistakes still happen.

If you can categorically evade mistakes and security and safety issues, why would you not?