Or even extending SaaS applications on the backend, like in Shopify's functions: shopify.dev/docs/apps/bu...
08.04.2025 05:37
👍 0
🔁 0
💬 0
📌 0
Or even extending SaaS applications on the backend, like in Shopify's functions: shopify.dev/docs/apps/bu...
> usually that role tends to be as supporting libraries to JavaScript applications
In the browser, yes, outside of the browser, I'd say no. There are a lot of solutions using WASM that could potentially benefit from scripting capabilities. spacetimedb.com, www.fluvio.io, github.com/drogus/crows
Yes, it's a very similar concept. The biggest difference between the two is that porffor aims to achieve the goal without WASM GC. It will be definitely interesting to compare the projects once both are close to passing the full spec.
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.
There are a lot of scenarios where WASM makes sense even if it's slower than a native implementation, mainly in context of safe execution of third party code and easy integration of components written in different languages - think extensions, embedded functions etc.
It’s too early to do any meaningful benchmarks in my opinion. Once it’s mostly compatible with the spec, it might make sense to look into it. It will definitely be slower than advanced engines like V8, especially with JIT enabled
If you like the project and you would like to support the development, please consider sponsoring me on GitHub: https://github.com/sponsors/drogus
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 😆
Me: "I'm sure not going through the entire thing"
Also me: goes through the entire thing
It looks like there were more comments complaining about "Why not Rust?" comments or making fun of "Rust's community outrage", than the actual "Why not Rust?" comments 😆
If anything this is something I've seen much more often
I've skimmed through the thread and other than an occasional "better write it in Rust" from some complete randos, I have seen mostly balanced takes. I would love some links if you come by anything, cause I'm sure not going through the entire thing lol
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"
Since I posted this I learned it's in fact a law in some EU countries. Hopefully it will be more widespread at some point
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...
you want to use half your salary for rent. And that all happens when there are calls for austerity measures and public services are getting worse. No wonder AfD got 20%. And I worry they will get more if the situation worsens. It's not the first time a struggling society turns to extremes
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_...
underrated take 😁
In the capitalist hellscape we live in I guess 😭
Sounds like a good purchas! Also feel free to ask me about impulse buying a forklift this one time 😆
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).
For more context - "fewer defects" is not in the article, but it's mentioned in the talk: https://www.youtube.com/watch?v=QrrH2lcl9ew
