Rust and Cargo enters the room.

We’ve been using Linear in my latest company and it is actually quite good. No bullshit fast UI, boards, issues linking with Git, a support that can take a feature request that is often implemented in a week or two after asking it.

It kind of fails with certain protocols. I once wrote an async MSSQL client for Rust, and some data doesn’t say its size in the headers. So this kind of forced the business logic to be async too.

Never had one, just partied in the uni and dropped out :D

So basically your typical network protocol is something that converts an async stream of bytes into things like Postgres Row objects. What you do then is you write a synchronous library that does the byte conversion, then you write an asynchronous library that talks with the database with async functions, but most of the business logic is sync for converting the data coming from the async pipe.

Now, this can also be done in a higher level application. You do a server that is by nature async in 2024. Write the server part in async, and implement a sync set of mapping functions which take a request coming in and returns a response. This can be sync. If you need a database, this sync set of functions maps a request to a database query, and your async code can then call the database with the query. Another set of sync functions maps the database result into http response. No need to color everything async.

The good part with this approach is that if you want to make a completely sync version of this library or application, you just rewrite the async IO parts and can reuse all the protocol business logic. And you can provide sync and async versions of your library too!

That’s why you write your protocol as a sync library, then implement the async IO separately and mapping the data over the protocol modules.

dbg!(1) all the time…

It creates a set of symlinks so every program sees exactly the dependencies it needs.

https://nixos.org/guides/nix-pills/09-automatic-runtime-dependencies#automatic-runtime-dependencies

You can also create a container:

https://nixos.wiki/wiki/NixOS_Containers

Or you can create reproducible docker containers with nix:

https://dev.to/anurag_vishwakarma/a-better-way-to-build-reproducible-docker-images-with-nix-2k59

The secret sauce with nix is reproducibility. If it builds once, it will continue building exactly like that forever. Bit by bit.

Nix can build you a bit-to-bit exact environment for your app. It is a superior environment, but is hard to use in the beginning and users can feel snobby sometimes. It is awesome, but YMMV.

Nix user arrives to the room.

I’m coming from the old ages of internet where we didn’t have them. I’m fine with them, but I’m too old to use them comfortably.

It’s fine. Use them if you like, but I don’t really see the value in systems such as Discord where you pay money to have special emojis and so on…

Divide and conquer…

And Finland…

Me too. Although I will not cry if Stubb takes the presidency. Will not vote for him, but it will not be the end of the world either.

Yeah, well we were a month in KC just before and ate the most amazing food. It was so crazy to get that thing from the restaurant when we got back.

Yep. I’m from Europe and of course this is kind of not understanding American culture enough to not compare different qualities of mac&cheese. That reminds me, we came back home from the US and had mac&cheese in a restaurant in Germany. They served us Kraft with fried onions and parmesan flakes on top. At that moment I understood Germans will never understand American cuisine…

What about Annie’s? Or call we even compare them?

T or X series is really good. Just be careful to get an IPS panel, the TN film models are really bad.

If the computer worked that three year span in a corporate environment without breaking, it’ll last for years.

I’ve been in an interview and the hiring manager wanted to have a call in Teams. Didn’t take that job.

It comes with the Office subscription. People who choose it are not the ones using it daily.