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 😬
In another move[1] to stay up-to-date with latest version of Zig (v0.12.0), I've also updated all code (and .zig.zon depencency info) in the still-just-a-baby zig.thi.ng repo:
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:
Found a small #Zig issue with EnumSet, so raised an issue yesterday with a fix PR. One round of PR feedback to fix a test, and it's merged. ⚡ 10/10 would PR again.
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 :)
Started using @golang for simple command line tooling instead of Typescript. So far enjoying it very much, I think it’s bye bye to (cli/serverside) Typescript for me.
@yth@golang I know, I’m dreaming :) I don’t have experience with Go, never had but I was always fond of Ruby syntax and how gently it treats various data types and string operations. It was just not so robust to me regarding performance and infrastructure and I got curious about #crystallang trying to fix that, while inheriting baseline from #ruby. This is just POC to stay curious. i’m aware that #rust, #golang and even #elixir are more new wave,popular while #zig and #crystal have their niches
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.
As much as I love C++, its optional and expected objects can just envy one killer feature of their Rust counterparts. If you're working with a Result<T, E> in a function that returns a Result<U, E2>, you can use operator ? to simply unwrap the Ok value into a variable. If the result contains an error, Rust will not panic; rather, it returns that error from the current function similar to how exception would bubble up the code. The only limitation is that the function must return Result with the error type to which the propagated error can be implicitly converted.
Option also supports the operator ?, which either propagates None up the call stack or safely unwraps the stored Some.
I'd kill to have this in C++, where you would have to employ non-standard compiler extensions to create a macro that would be at least close.
@jakub_neruda#Zig ups it up a notch. You don't need to specify the error type, as the compiler will figure out the union of all possible bubbling-up errors and infer it into the function return type signature.
"Definitely the most underrated project on github without exception." — a recent response to the State-of-thi.ng user survey 2024, currently open until end of the month. If you have been using any of the hundreds of libraries in this larger project, please do consider participating...
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.
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)...