Zig compiler project is about 600,000 lines of code - roughly the same size as Bun before the rewrite, and I'm clocking 16s to build from scratch with a clean cache, followed by 90ms for each subsequent edit with incremental compilation enabled.

That's impressive compilation performance. And so most certainly when contrasting it to Rust.

Brb, I am rewriting everything in Zig.

If the original contract was for software without source code, you'll have to negotiate. I don't think it's helpful to look for options and licenses before knowing what they are ready to do and share and what restrictions they would require for that.

They would be very well within their right to outright refuse. The vendor-lock-in may even have been an explicit business strategy. I assume they offer maintenance, at a higher price than you would cost?

So, is the account actually read-only?

engine Passed 27 courses

Who is engine?

I guess the title stems from

@godot @godotengine Passed 27 courses

and that's a software bug?

I had never heard of opkg. I looked it up:

opkg: Fork of ipkg lightweight package management intended for use on embedded Linux devices;

ipkg: A dpkg-inspired, very lightweight system targeted at storage-constrained Linux systems such as embedded devices and handheld computers. Used on HP's webOS;

Wikipedia has no dedicated pages for either of them. I guess they're quite niche.

Commit with Co-authored-by: Copilot

or maybe better --author=Copilot

It would certainly help evaluate submissions to have that context

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

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.

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?