So, to get back onto having fun with programming after some bad experiences with #rust people I decided to do a bit of #nim (skull) to get back into the groove again.
One thing that I really like about nim is just how natural and extremely readable it feels. just being allowed to overload stuff, being able to pretty easily just extend stuff small things like indexing a 2D array with a point or that making a contains functino automatically lets me use the "if point in grid" style syntax is really nice.
The one thing from #zig that I kind of miss is that each struct kind of works like a namespace where you can add your functions that works on that type, it kind of makes the code more ordered, because as I end up doing it in my code, it does become a bit more cluttered since everything is on the top level.
Another really nice thing that I like with nim is that it allows me to use the (oca)ml type function calls, so that I can do "seq.add blah" rather than having to do "seq.add(blah)" it's a small thing, but it's really nice.
After 10 years of commercial experience in #cpp I think I’m ready for a new chapter. I have played around with #rust#golang#zig and #clojure but most job offers that I see are for people with at least X years of commercial experience in this exact languages. Do you have any hints how to approach this? I would think that my previous experience as a #software engineer would matter. Especially since I do not expect to move to another senior role, I’m checking junior positions too. #jobsearch
I’ve been using new shiny languages for a while now. #Rust, #Zig and #Swift in particular.
I love Rust’s tooling, Swift’s syntax, and Zig’s philosophy, but I feel like good old #Cpp is still the goat.
Yeah, the syntax can get out of hand really quickly.
Yeah, the STL is bloated.
Yeah, the tooling ecosystem is a mess.
But at the end of the day, with a good style guide and some discipline, it can check most of my boxes.
But learning new languages is always fun so I’m still doing it 😬
Just updated all https://thi.ng/wasm-api packages, bindgen, build scripts, readmes and examples to be compatible with the brand new Zig v0.12.0 released a couple of days ago... This includes adapting to breaking changes (esp. Zig's build system) and updating the hybrid Zig/WASM/TypeScript project template:
i hope #zig will be sustainable. i like its way more than #rust. and like in C or even RISC-V microarchitecture, but not so much in Rust and C++, the language definition is compact enough so that it just stick into your head. also, comptime is really cool invention in my opinion. #C#rustlang#riscv
The #zig experiments continue, still very much liking it.
Dropping random C/C++ files in the build and having it just work is great.
Only minor issue I hit so far is missing syntax to make a slice from a single-item pointer (like slice::from_ref in Rust), but looks like this is getting fixed for 0.12 (https://github.com/ziglang/zig/issues/16075). And can work around in 0.11 with some comptime trickery.
I must say, I really like the QOI image codec despite its shortcomings for coding efficiency and flexibility - it is dead simple, easy to implement, and super effective for what it is! I'd be happy in a world where we used QOI instead of PNG for a lot of stuff. And I've already fallen in love with Zig, which I think is very easy :)
Un beau troll de BOFH lors d'une discussion sur le développement du langage de programmation #Zig. En réponse à une suggestion que davantage de gens donnent leur avis, le mainteneur répond "'If you don't have any open source project written in zig with 100+ commits, don't bother" https://github.com/ziglang/zig/issues/6025#issuecomment-1949254383
Tried to use it on my second 💻 today, to no avail and much grinding of teeth.
I'm not setting up any more #venv . I'm fed up. I'm bloody rewriting everything, even libraries in #perl so it works proper on #unix damn it. And maybe throw a look at some #zig porting while at it.
To achieve a better sample size, I'd highly appreciate if you could circulate the link to this survey in your own networks.
It's already been almost 9 years since the last user survey for these projects. Please help me/us to get more insights into your own experiences, your interests, hopes and pain points — allowing the projects and everyone involved to move forward more intentionally.
There're 15 questions here, with ~10 of them marked as mandatory. The main focal points are the matrices in the middle of the survey. Please also do use the final freeform comments box to share any further feedback you might have. Thank you very much for your interest, trust & taking the time to provide some much needed answers! 🙏
The survey is anonymous and will remain open until 23:59 (CET) on February 29, 2024. I will then share a public summary of the results on my Mastodon in the days following (do keep an eye on the #ThingUmbrella hashtag)...
This weird fileformat I am parsing right now has packets of 64 bit length. Some are headers, some clock "heartbeats", some "hits". For whatever reason, the magic of header packets is in the least significant bytes while the magic of all other packets is in the most significant bytes. Who comes up with something like that?
Either way, parsing is super neat because #zig lets me just read the entire file as u64's which I can then cast onto packed structs.
I'm inviting a little randomness into my work schedule by seeking serendipity on the fediverse:
I'm looking for a small project starting late Feb/Mar - a couple of days a week at most. If you could use a bit of help for a competitive day rate, say hello 👋
Youtube premieres are garbage for RSS readers... they share the moment the premiere is shared, not when the thing is actually playing...
I've been waiting for the latest talk of the #Zig Showtime since yesterday AAAAA.