Vasco Costa

ES2024 brings some kind of pattern matching to switch, but I think it's more about object destructuring, so probably still not usable in the same fashion as say in Rust.

As a rustacean I must say I'm enjoying using TypeScript's neverthrow. In a way, the way it allows Result composition is even neater than Rust's.

No more try/catch/throw spaghetti code again. Makes TypeScript a bit more palatable for Rust lovers.

#rustlang #typescript

That good feeling when you nail a good #rustlang one-liner that may not be the most readable but is so damn neat...

Once you go cargo there's no turning back... It's one of the reasons why Rust becomes ever more popular. On top of all the language goodies, tooling is really important.

I've been myself thinking about getting back to some C/C++ projects but not getting enough motivation when I think about tooling.

A shoutout to @rockorager.dev for this, zeit, libvaxis and more. I often read his code as a means to improve my #ziglang skills.

Me standing next to Senna's Lotus 97T/2.

Today on the 40th anniversary of Ayrton #Senna's maiden #F1 win during the 1985 F1 Portuguese GP at the soaked wet #Estoril Circuit, I had the chance to see his Lotus 97T/2 (the original chassis he raced). Happy fan standing next to the mythical #12 machine I remember watching on TV as a kid.

I think people still consider C/C++ as a new language due to the sheer number of software written in them. Lots of job opportunities. Companies that are adopting Rust/Zig still need someone with C/C++ knowledge to convert old codebases. But from a purely enjoyment point of view, probably not many.

GitHub - vascocosta/zircon: A simple IRC library written in Zig. A simple IRC library written in Zig. Contribute to vascocosta/zircon development by creating an account on GitHub.

Released v0.6.0 of zircon, a simple IRC library written in Zig.

Add support for TOPIC, RPL_TOPIC and RPL_NOTOPIC
Add support for ERR_CHANOPRIVSNEEDED
Add support for ERR_ERRONEUSNICKNAME
Add support for ERR_NOSUCHCHANNEL
Add support for ERR_NOSUCHNICK

#ziglang

github.com/vascocosta/z...

I had a VPS with not enough RAM (for Python, Go and C#). I started coding in Rust and Zig and now I have a VPS with too much RAM I don't use. 👍

Day 682 of typing `zig build -Doptimise=ReleaseSafe` instead of `zig build -Doptimize=ReleaseSafe`. #ziglang ⚡

For those learning or refreshing their knowledge about #rustlang who enjoy reading on their e-reader, here's a list of freely available books in ePub format, including "The Rust Programming Language":

dieterplex.github.io/rust-ebooksh...

Thank you so much for sharing. 😍

Good observation.

In a way bork0 and bork2 looked a bit "funny" in my Rust example, because I was directly translating your go example as verbatim as possible, which included trying to mutate the data inside the function.

Even though we need mut in both bork0 and bork2's function parameters (because we are mutating the local variables), the real beauty of Rust like you mentioned is that when calling the functions, since we don't pass a &mut as argument, we clearly see there won't be any mutation of the parent data.

When I was learning Rust chatgpt had just been released. It did a good job, but also produced quite broken code (more than nowadays).

However the explanations it provided about the hard concepts to grasp in Rust were spot on and definitely taught me a lot!

I think LLMs are great as teachers.

This is a good-hearted piggyback on a previous post by @rkuris.bsky.social.

OK #golang experts who don't know #rustlang! Without running this code and with one eye closed, how many of these modify their parent's data value?

Playground: play.rust-lang.org?version=stab...

This.

For some time I didn't know this or would forget and need a refresher. Go is minimal and easy to keep in your head for life, but details like this weren't for me.

I would forget sometimes, finding out the hard way at runtime. Rust improved me as a go coder by being so picky at comptime.

As a golang coder I used to get confused by this. As you mentioned, there's no explicit indication of mutability/immutability.

Then I learnt Rust and it really made me think. The mut keyword is clear. Better than the implicit way in go where a reference implies mutability and a value immutability.

Rust makes me a better Zig coder when it comes to naive memory errors.

Zig makes me a better Rust coder when it comes to hidden allocation awareness.

I love both, for different reasons and projects.

#ruslang #ziglang

Git turns 20: A Q&A with Linus Torvalds To celebrate two decades of Git, we sat down with Linus Torvalds—the creator of Git and Linux—to discuss how it forever changed software development.

Git turns 20: A Q&A with Linus Torvalds

#git #github #linustorvalds

github.blog/open-source...

allocPrint is equivalent to template literals/strings in Javascript.

const name = "John";
const age = 30;

Javascript:
const message = `My name is ${name} and I am ${age} years old.`;

Zig:
const message = std.fmt.allocPrint(alloc, "My name is {} and I am {} years old.", .{ name, age });

Concatenating strings requires more memory as the resulting string will be bigger.

Zig is explicit when this happens. It does not allow, hidden allocations. So if we were to use something like a + operator, it would hide the allocation.

My favourite functions:

std.fmt.allocPrint
std.mem.concat

Maybe you'll also find arena allocators interesting. You allocate a region of memory once at the beginning of the program and then do a single deallocation at the end.

There's no need to match individual allocs with frees each time, lowering the chances of creating a leak by forgetting to free.

fn main() {
println!("Welcome!");
}

Well, as an oldschool IRC user I like the IRC channel at Libera, but I think the Ziggit forum is a better starting point for a newcomer who needs help about some Zig topic. If you're on Discord, that would be my third-choice. Anyway the community feels welcoming no matter which medium.

Anyway, it still hurts me that Hamilton lost it all at the last moment the way it happened.

I believe we share that feeling.

I don't think that in that case in particular he was reckless. More like a weird situation. That said, I think Max was reckless hundreds of times since he joined F1.

The reason they didn't have a serious crash in 2021 was probably because Hamilton took evasive action against his moves.

Do you think Max realised his wheels were on top of Lewis Hamilton's head and that the halo didn't quite work in that freak accident and then he tried to use the throttle to harm him instead of getting back on track?

By the way, when he pressed the throttle the wheels had already cleared his head.