lerno

4 ms·

1.
by lerno 6d ago
I believe all examples are derived from C++ examples on its new reflection capabilities.
2.
by lerno 6d ago
C3 has an even simpler way than Zig: `Color.RED.description`. From what I can see the example started from C++, and then comparing how each language would look building it in userland instead.
3.
by lerno 1mo ago
Yes, lesson learned.
4.
by lerno 1mo ago
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.
5.
Marketing failure: I thought I was building a C replacement. I was wrong(c3-lang.org)
19 points by lerno 1mo ago|4 comments
6.
by lerno 1mo ago
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 where you'd use C/C++/Swi
7.
C3 0.8.2 a Modest Improvement(c3-lang.org)
25 points by lerno 2mo ago|6 comments
8.
by lerno 2mo ago
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 haven't tried C3, feel free to jum
9.
by lerno 3mo ago
Yep
10.
by lerno 3mo ago
Counterpoint: https://news.ycombinator.com/item?id=47989154
11.
by lerno 3mo ago
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
12.
by lerno 3mo ago
Early days of Wikipedia was the wild west. Surely you must agree to that.
13.
by lerno 3mo ago
No, Grokipedia is just a crapfest. I'm talking about actually asking ChatGPT
14.
by lerno 3mo ago
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
15.
by lerno 3mo ago
The C3 grokipedia entry was horribly bad, so I don't really have a favourable impression of it.
16.
by lerno 3mo ago
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
17.
by lerno 3mo ago
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 a
18.
by lerno 3mo ago
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 wi
19.
by lerno 3mo ago
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.
20.
by lerno 3mo ago
$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 overlo
21.
by lerno 3mo ago
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.
22.
Odin 2026-06 Released(github.com)
1 points by lerno 4mo ago|0 comments
23.
by lerno 4mo ago
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.
24.
by lerno 5mo ago
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.
25.
Unsigned sizes: A five year mistake(c3-lang.org)
120 points by lerno 5mo ago|149 comments
26.
by lerno 5mo ago
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 the Odin one, it’s a bit clearer why the d
27.
by lerno 5mo ago
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 library and the language. The two forme
28.
C3 0.7.11: closing out the 0.7 series before 0.8(c3-lang.org)
4 points by lerno 6mo ago|1 comments
29.
by lerno 6mo ago
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 standard library (like matrices) have al
30.
by lerno 7mo ago
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 impose upgrade work on apps, but also disc

More ›