Filter
Exclude
Time range
-
Near
Congrats, and we support
3
movy 0.3.0 is out! - neon render layer · movy.Frame - kitty keyboard protocol - high throughput output · movy.DiffOutput - linear float colors · movy.color.V3 rendered live, in the terminal. github.com/M64GitHub/movy #Zig #ziglang #demoscene #terminal #rendering
24
Five months ago TSUNAGI was just an idea. No grants. No treasury funding. No VC money. No paid engineering team. Just a belief that Cardano deserves independent builders willing to take risks, fail publicly, learn, and keep going. We started on Zig 0.13. Then Zig 0.15. Today TSUNAGI runs on Zig 0.16. The journey was anything but smooth. We fought through era mismatches, sigma drift, opcert failures, stale parents, propagation issues, delivery bugs, and countless nights staring at logs wondering what we were still missing. Every time we solved one problem, another appeared behind it. There were moments when quitting would have been the easy option. But today, for the first time, I can honestly say: TSUNAGI is no longer missing blocks. That isn't because we got lucky. It's because we stayed in the fight long enough to find every reason we were failing and fix it. More importantly, I want to say thank you. Thank you to everyone who delegated to TSNG on Preview. Thank you to everyone who followed the journey. Thank you to everyone who believed in us when there was nothing to show except bugs, logs, and stubborn determination. Those delegations mattered. Those leader slots mattered. Without them we wouldn't have had the real-world data needed to find the next bug, prove the next fix, and keep moving forward. What makes TSUNAGI different isn't just that it's written in Zig. It's the philosophy behind it. We don't hide failures. We document them. We don't move on from bugs. We understand them. We don't treat mistakes as something to forget. We turn them into tests so they never happen again. Every failure becomes evidence. Every bug becomes a regression test. Every setback becomes part of the system's memory. While many people are focused on funding, proposals, and treasury discussions, I wanted to prove something first: You don't need permission to build. You don't need a budget to innovate. And you don't need to wait for someone else to solve the hard problems. You can sit down, do the work, and keep going until it works. Today I'm proud of what TSUNAGI has become. But I'm even more proud that we never gave up before getting here. This isn't the finish line. It's the beginning. The real work starts now. 🚀🎌 Thank you for believing in us. #Cardano #TSUNAGI #ZigLang
5
20
657
Replying to @njoguamo @ziglang
I seemingly saw a variant with it added already.
4
Joran Dirk Greef retweeted
@TigerBeetleDB CI, but on the track. We had a TigerBeetle fan come ask us about the connection, mentioned @ziglang as well. Can't escape tech shop talk, even at that track :-)
4
26
4,192
ChainSafe retweeted
How does Lodestar scale performance in a Node.js environment? By tapping into @ziglang. Yes, binding Zig to JS comes with challenges. That’s why we built ‘zapi.’ 🧵👇
1
1
11
509
I'm writing a database in Cpp because it's what I know best.... I'm regretting not using @ziglang every time I end up with a constepxr mess or template magic rather than just having comp time functions...
3
189
Fair then! Thanks for clearing things out. :)
1
34
I think you misread my post. I said my idea of compile zig compiler into WASM is not new and I took it from ZLS repo
1
1
50
Lol no zig tools is the org owned by the zls team and it's been around for a long time
78
Do you mean the Zig core devs took the idea from your repo? That would be strange because at least Andew mentioned that in Dec 2022 already: ziglang.org/news/goodbye-cpp…

2
44
ok. I lied. The other thing I want in #ziglang is for tuples to be converted to varargs when the function has extern(.c)
2
250
Congrats clean pass Full green across all lanes is impressive 🔥
35
Someone add @ziglang
Ya'll laughed at me for loop benchmarks. Now it's the future of coding. Hope Boris is using C and Rust exclusively.
1
50