lerno

Yes, lesson learned.

TLDR; people think that a "C-alternative" means "used for what C is used for today". But that's not what the C alternatives (except for Zig) try to achieve.

This is partly true. But I want to add that the ergonomics of C3 is there to make general app development smooth, whereas for Zig that is not really the focus. So the goal for C3 is to also be used …

This isn't a very exciting release: it adds a few useful things to libraries and to generic compile time introspection – but that's pretty much it. Just some incremental improvements. If you…

Yep

Counterpoint: https://news.ycombinator.com/item?id=47989154

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…

Early days of Wikipedia was the wild west. Surely you must agree to that.

No, Grokipedia is just a crapfest. I'm talking about actually asking ChatGPT

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 …

The C3 grokipedia entry was horribly bad, so I don't really have a favourable impression of it.

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…

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 p…

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 ca…

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 bin…

$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 …

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.

As a contrast to Zig: C3 is strongly invested in contracts and is able to use them for static analysis at compile time to some degree.

The difference is that in the unsigned case you get a seemingly plausible value, and in the signed case you get a negative value which you can be sure is wrong. This is the problem.

Odin started in 2017, had a fraction of the contributors and is soon 1.0, so that explanation isn’t cutting it. If you instead look at the over 500 kloc of the Zig source compared to the 70 kloc of th…

I think Andrew should seriously think about decoupling the toolchain from the language to put focus on reaching stability there. As it is, we have the compiler with surrounding toolchain, the standard…

C3 0.7.11 is the final release in the 0.7 series. This version focuses on tightening semantics, improving type inference, and cleaning up edge cases rather than adding new features. Some parts of the …

I just have to add another reflection: One thing that tends to be overlooked when discussing changes is the ecosystem effect of frequent changes. A language that breaks frequently doesn't just im…

> Not at all, if the team needs 30 more years they should take it. Yes, I understand that is the opinion in the Zig community. As an outsider, it seems odd to me to pick a language that I constantl…

I am using games, because they pop up more often (gamejams etc), but we can see the same if we'd look at utility apps. Do you want to broaden that to "Odin is more explicitly marked towards …