One funny thing is that if you go on codeberg and want to submit a PR to Zig, you can't. Because Zig's too big for Codeberg, and you're over your free quota, so you can't push your update to your fork.
Yes there are ways around it if you have patience, but what the heck!!
Worth noting that while it's absolutely unfortunate that we're hitting this Forgejo design flaw, AGit honestly is just a better workflow, and I (Zig core team member here, full push access to the upstream repo) have started using it for pretty much all of my PRs. There are a couple of small things I'd like to see improved about Forgejo's implementation of AGit, but IMO it fundamentally makes so much more sense than the two-step push-then-PR workflow (especially if you're an external contributor who would also need a first step of "fork the repo").
It's funny. Today people say that of Wikipedia, as if it was trustworthy. But it used to be common knowledge to just "don't trust anything on Wikipedia". Wikipedia was never like a regular encyclopedia, it just wanted to be one.
Its biggest advantage over traditional encyclopedias was its breadth and how quickly it could be updated. The trade-off was that articles could vary greatly in quality and could be edited by anyone, making accuracy less consistent than in traditionally edited reference works. So the effort to reduce breadth and say it shouldn't be updated quick... that's just strikes me (as someone fairly old) as kind of funny.
TBH, "Don't trust anything on Wikipedia" was always just stuck up posturing. Plenty of badly sourced, badly edited and biased articles in regular encyclopedias too, but because Wikipedia is contributed to by the unwashed masses, don't trust it.
"Don't use Wiki as a primary source" is much more to the point - it's not meant to be. Use it to find the primaries.
Also, I don't see this as "reducing breadth" so much as attempting to hold to a minimum standard of "has this been written up anywhere by someone other than the people who started it?" which isn't perfect, but it's been the stance since the beginning.
1. So are most other encyclopaedias, and most don’t even give you references or citations for an article
2. We are literally decades from that point now. Surely you must agree that times have changed.
What kind of happens is that there are some people who invest their lives in Wikipedia, their opinions is what ends up mattering.
This has boths pros and cons. The good thing about it, is that these people are deeply invested in Wikipedia and therefore have a lot of incitament to do what (they believe at least) is the best for Wikipedia.
The downsides are: (1) that just because you invested a lot of time into Wikipedia you don't have biases (2) you are not immediately qualified to determine whether some article/source is bad or not from a factual point of view.
Also, it's very HARD to become a regular contributor, because you'll have to invest an insane amount of time initially to build up goodwill and reputation, when at the same time anything you do might just get reverted because someone thought it was too much detail or bad in some other way.
So it's a very punishing environment which makes sure that the actual group of Wikipedia editors is a fraction of what one could expect. (Also, the Wikipedia markup... it's really the worst dialect of Wiki syntax)
Anyway, all of this is probably not good for Wikipedia in the long run. LLM's will be much better than humans at creating "beginner" articles, and it will be increasingly hard to know what's LLM-authored. So I expect Wikipedia to go the way of Stack Overflow in the long run.
Sounds like you are describing Grokipedia (Grok), where the general public has rejected it as a replacement for Wikipedia. Way too much hallucinating, tainted algorithms reflecting political preferences, gossip, and unverified or disreputable sources.
And as an example of bias: I personally witnessed a wikipedia editors adding their own interpretation of a certain written article. This interpretation was very politically biased and not justified by the text, but these were influential wikipedia editors so that it stayed in. I then asked the author of the article on Twitter if this interpretation was correct. I was unambiguously told NO. This information (including the public twitter conversation), was rejected by the wikipedia editors because it was first hand accounts.
Which led to the rather odd result that the interpretation of an article's message by a Wikipedia editor was favoured over the explicit statement by the article's author.
Here I would have thought that it would have been prudent to simply leave out that part of speculation, but they adamantly insisted it should stay.
I must add that this happened on Swedish wikipedia, not the main English Wikipedia – which I actually found much more balanced. But the problem is that this mechanism exists in the first place.
It was at the time (5-10 years ago?) well known that the Wikipedia of some language – I don't recall which one – was at the time pretty much hijacked by a group. Oh, wait I found it - the Croatian Wikipedia.
This is unlikely to happen to the main Wikipedia, but it does demonstrate a certain brittleness and risk of bias in the system.
The Zig C import is going away, moving into a tool invoked from build.zig, so this might not be an ideal thing to point to.
C3 just has everything C compatible so not just calling into C but also C calling to C3 is just completely normal with no special compatibility types/functions, unlike Zig.
So which one has the most compelling feature kind of boils down to what one focuses on.
You can find Odin users that praise Odin for finding their sweet spot. Similarly for C3 users, just like Zig users.
And in each of those, they will say that the others didn’t quite match what they wanted (not in all cases though: the relatively high visibility of Zig means a lot of its users is unaware of the languages with less visibility, and just pick it by default)
If you use LLVM at least, they expand to a lot of code which is repeated on every operation. There’s a point where the inline code will just blow the instruction cache and just create unacceptable binary bloat.
$400k is serious money and will certainly help keeping the Zig team funded. I must gratulate Andrew and the team on their ability to create a product that is creating this kind of enthusiasm from its users.
One thing that’s sometimes overlooked though is that all donations are something that we’re grateful for, regardless of amount. If you have little to spend then even $1 a month is an investment that rivals $10000 by someone rich.
Also worth remembering is that the vast majority of language projects aren’t operating at Zig’s scale. For smaller projects such as C3, even modest recurring support can have a meaningful impact on long-term sustainability.
It doesn’t need to be $100000s a month to make a huge difference.
Zig syntax has been mostly stable since 0.2, it is extremely unlikely it will change beyond tweaks. You have to go to Odin, C3 or (in the future) Jai for an alternative.
Just some incremental improvements.
If you haven't tried C3, feel free to jump to https://learn-c3.org and try it in the browser.