Elektrine
Log in Register

#ziglang

13 posts · Last used 9d

Hacker News @hackernews@robot.villas
· 2mo ago
Cruller: Bun's Zig Runtime, Continued on Zig 0.16 https://ziggit.dev/t/cruller-buns-zig-runtime-continued-on-zig-0-16/16734 #HackerNews #Tech #ZigLang
Cruller: Bun's Zig Runtime, Continued on Zig 0.16
Ziggit

Cruller: Bun's Zig Runtime, Continued on Zig 0.16

Cruller: a production-focused Bun runtime ported to Zig 0.16 Cruller is a fork of the last Zig-based Bun release, reduced to the parts needed to run already-built production JavaScript servers and ported to vanilla Zig 0.16. Repository: GitHub - solenopsys/cruller: fork of Bun · GitHub The project keeps JavaScriptCore, Bun.serve, HTTP/1-3, WebSockets, fetch, streams, Blob, Request/Response, static serving, and the module resolver for pre-built JavaScript. It removes the package manager, bundle

0
0
0
0
Ramin Honary @ramin_hal9001@fe.disroot.org
· 2mo ago
River is a Wayland compositor written in Zig that defines a window manager protocol so that, like with X11, write your own window management software. As with X11, the protocol is language-agnostic, so you can define your window manager using any programming language at all. I have been gradually becoming more interested in Zig as a potential replacement for C in systems programming. Rust is another interesting potential replacement. #tech #software #Zig #ZigLang #Linux #Wayland #WindowManager #WaylandCompositor #RiverCompositor #UnixPorn
7
2
6
0
ᛋᛁᚵᛁᛋᛘᚢᚾᛑ ᚾᛁᚾᛃᛅ @sigismundninja@mastodon.nu
· 2mo ago
An adult and reasonable take on #rustlang and #LLM use. I'm starting to get tired of the #ziglang hype. Soon you'll remember why the borrow checker and the "enforced" functional style was a good idea. Sure, Rust is bloated and messy. Many rewrites has been silly or about copyleft. Still, the backlash has not been in proportional. https://bun.com/blog/bun-in-rust
Rewriting Bun in Rust
Bun

Rewriting Bun in Rust

Why & how we rewrote Bun from Zig to Rust

1
0
0
0
💙🩷💜 Brett [he/him/any] @brettm@swarm.coiloptic.org
· 3mo ago
Questions about pointers: I'm learning a bit of Zig and have never used pointers before (I do understand the general concept of how to use them, that they point to address etc). afaik using pointers is faster than operating on/ looking up the variables themselves? My main confusion (using example below) is, why dereference the pointer with 'ptr.*' in the 3rd line? Why not just plug in the address directly with '&num'? Is that for performance too? Otherwise the code seems convoluted for no reason. var num: u8 = 12; const ptr: *u8 = # std.testing.expectEqual(ptr.*, num); #ziglang
0
1
0
0
You've seen all posts