I need to finally finish a blog post I started a while ago titled sth like "Zig's comptime is not Rust's macros equivalent". Comptime is very interesting, but it's not the same, and it doesn't allow you to do a lot of the things macros let you do.

I have written a post about JAWSM, my JavaScript to WebAssembly compiler: https://itsallaboutthebit.com/jawsm/. Long story short: I now implemented all of the JS semantics (scopes, prototypal inheritance, async/await, generators) and it passes 25% of Ecma262 spec test suite.

I went through the comments in the "Why Go?" thread github.com/microsoft/ty... and I categorized the relevant comments. It looks like more comments are complaining about "Why not Rust?" comments or making fun of the supposed Rust's community outrage than the actual "Why not Rust?" comments 😆

Regarding the recent "tsc rewrite in Go" debate, I must say that I've seen countless posts complaining about Rust community reacting poorly, and almost zero actual poor reactions. Seems like a total knee-jerk reaction "rewrite in Go, must mean Rust fanbois are angry"

My "hot take" for today is that a yearly raise that would at least cover the rate of inflation should be a norm, rather than an exception; otherwise, the value of people's salaries decreases over time. This really shouldn't be viewed as "hot take", but unfortunately, probably is

I need help. 3 National STEM Festival sponsors pulled funding because of the current climate. Please help. This is a life changing opportunity for kids that have worked so hard! www.gofundme.com/f/support-th...

Recently, I've been thinking quite a lot about taxes in the wake of inflation and the housing crisis. While I fully support progressive taxes, there is something wrong with the notion that, for example, in Germany, a salary in the top 5% of earners will barely get you a two-bedroom apartment unless

Here's a very nice explanation on why Landman's stupid monologue about wind turbines is, well, stupid: www.youtube.com/watch?v=wBC_...

Whenever you hear someone sneer about scientific research that seems useless to them — “they’re studying the spit of lizards?!” — remind them that’s exactly how we got Ozempic. globalnews.ca/news/9793403...

Hey, programmers worried about your roles being replaced by AI, hear me out. I use LLMs almost daily. It's nowhere near being ready to replace anyone, and it's not certain LLMs can get significantly better. Hype is mostly for getting investor money, not because they're that good.

I really like this clip where Mitchell Hashimoto responds to why he chose Zig over Rust: https://www.youtube.com/watch?v=dJ5-41u-e7k. His answer is basically: I have more fun writing Zig. I think it's very often the case with our choices, whether we like to admit it or not, and it's totally fine!

Fully Stuck Software Engineer

I don't like new Ruby3.4 feature to name 1st block arg `it`, which trades a few extra characters `|it|` for readability, eg. `arr.map {|it| it.foo }` vs `arr.map { it.foo }` https://blog.sinjakli.co.uk/2025/01/01/ruby-3-4-highlights/

This might be an unpopular opinion about using AI, but I use AI pretty much only for stuff that I know exactly how to write and how I would like it to look. The suggestion will influence your thinking and you will possibly not think through the problem enough to notice issues

People be like "Rust is too complex" and then expect me to just hold like half of the codebase in my head in order to validate constraints that I would otherwise put into the type system (especially when it comes to memory safety or data races, but not only).

Ok, so this is quite interesting: https://www.ardanlabs.com/news/2024/rust-at-google/. Google a/b tested Go and Rust teams rewrites of Google's services. It turned out the Rust teams were developing at a similar speed as Go teams, but with fewer defects

We have landed on bluesky! 🦋 Give us a follow to keep up with everything embedded Rust 🦀 Join 3.5k+ Rustaceans and subscribe to our bi-monthly newsletter below👇 www.theembeddedrustacean.com/subscribe #rustlang #embedded

I've seen a lot of people saying they'd prefer Zig's comptime in Rust, rather than macros. Comptime is an interesting concept, but it has downsides, and is often used to make up for lack of features that Rust has (like traits).

"why do I feel so busy all the time?" I ask myself, while starting like a fourth new project in the last few months 🙃

For a while now I wanted to create a Rust macro for composing SQL queries by just writing SQL. No DSLs, no tricks to support joins or CTEs or other advanced features. I'm thinking I'll do a stream implementing it, so if you want to learn about writing Rust proc macros stay tuned!

I'm wondering how much "it's still hard to find Rust jobs" is a problem with Rust vs a problem with the job market. I've talked to many people who work for companies either introducing Rust or at least exploring it, but the truth is, the market is just screwed at the moment.

I just open sourced Tarnik - a project providing a Rust macro to generate WASM GC code: https://github.com/drogus/tarnik. The main aim is to use it in my other project https://github.com/drogus/jawsm, but I think it might be useful for others working with WASM GC too!

I am on the third level of yak shaving my distributed stress tests runner. 1st level is the tool itself. 2nd level is a JS to WASM compiler, so I can efficiently run JS code on the tool. 3rd level is a WASM GC code generator, so I don't have to write all the WASM GC code by hand

When you start writing Rust no one prepares you for the size of `target` directories

I added a new feature to JAWSM https://github.com/drogus/jawsm. Tail calls are now automatically optimised, meaning the attached code will work when compiled to WASM with JAWSM, but it will fail on Node.js or in a browser when reaching call stack of 5-10k (depending on the settings)

I'll be streaming adding new features to JAWSM JS to WASM compiler in a few minutes, join me here: https://www.twitch.tv/mrdrogus

I have to reschedule my stream. I'll be streaming programming new features for the JAWSM JS to WASM compiler on Sunday 8pm CET/2pm EST/11am PST - Sunday instead of Saturday. See you there! https://www.twitch.tv/mdrogus/schedule?seriesID=1d0345a2-03e1-4656-b9d9-1dbf44455766

As soon as the "share everything threads" proposal becomes standardised I'm adding a feature to Jawsm that will allow to run multiple Javascript threads all able to do I/O and no one can stop me <evil laugh> 😈

I'll be streaming adding new features to https://github.com/drogus/jawsm on Saturday at 8pm CET / 2pm EST / 11am PST https://www.twitch.tv/mdrogus/schedule?seriesID=1d0345a2-03e1-4656-b9d9-1dbf44455766 #rustlang#wasm#webassembly

According to this paper about 20% of job postings are "ghost jobs": https://arxiv.org/abs/2410.21771. If I ever find out about a company doing this, I'm putting it on my "never want to work with them in any way or capacity ever again" list. That practice is just horrible

One interesting feature that I plan to play with for jawsm https://github.com/drogus/jawsm is tail call optimizations. JavaScript in Node.js and most (all?) browsers can't optimize tail calls, so recursive function calls are limited by the stack size (typically a few thousand)

I'm thinking about streaming coding new features on my hobby projects. Could be something on Jawsm compiler, which would mean Rust + WAT/WASM, like implementing await keywoard. Anyone interested?

For context: I work at a 501c3 nonprofit. We sued the Trump admin to block his rollbacks of environmental rules on average once per week from 2017-2020. We won 90% of those cases. This is why they want to stop us

Today I open sourced an experimental tool I've been working on for the past few weeks: github.com/drogus/jaws. Jaws is a JavaScript to WebAssembly compiler, meaning it's able to generate a WASM binary from a JS file without the need to embed an interpreter.