Or with Tauri, 5 MB. Which, amazingly, seems tiny.

In this case there are is a custom string library. Functions returned owned heap-allocated strings.

However, I think there's a problem where static strings are used interchangably with heap-allocated strings, such as in the function `string class_simple_name(string full)` ( https://github.com/neocanable/garlic/blob/72357ddbcffdb75641... )

Sometimes it returns a static string like `g_str_int` and sometimes a newly heap-allocated string, such as returned by `class_type_array_name(g_str_int, depth)`.

Callers have no way to properly release the memory allocated by this function.

The Helinox Chair Zero is the standard by which all backpacking chairs are compared https://helinox.com/products/chair-zero - and it is 1 lb 1 oz.

And then some people mod these chairs, like this similar one that was reduced to 13 oz. https://backpackinglight.com/forums/topic/chair-enlightening...

An example of the kind of unit confusion that could crash a Mars orbiter?

I thought we were talking about nanometers and square meters here for a second. But this only makes sense if "m²" means square miles and "nm" means nautical miles. How about at least using "mi" for miles to reduce confusion?

For example, we can go to the Wayback Machine at archive.org to not only see what a website looked like in the past, but prove it to someone (because we implicitly trust The Internet Archive). But the Wayback Machine has deleted sites when a site later changes its robots.txt to exclude it, meaning that old site REALLY disappears from the web forever.

The difficulty for a trusted archive solution is in proving that the archived pages weren't altered, and that the timestamp of the capture was not altered.

It seems like blockchain would be a big help, and would prevent back-dating future snapshots, but there seem to be a lot of missing pieces still.

Thoughts?

On the plus side, it's nostalgic and reminds me of the old MS Word 6 on Windows 95 (or Windows 3.1?) so that's nice.l

Slow and inconsistent refresh rate, limited lifetime cycles that you could wear it out in a year or 2 with frequent use.

I did have a Macbook trackpad fail in a similar way, where the "button" seemed to intermittently fail to click. It turned out my battery was swelling (see /r/spicypillows) and this impacted the trackpad operation.

On topic, I took the Macbook with swollen battery in to the Apple Store and they had to replace the entire keyboard+battery assembly as a unit because the battery was not replaceable.

    let names = ["Peter", "Julia", "Xi"];
    names
        .map(|name| format!("Hello, {name}"))
        .iter()
        .for_each(|greeting| println!("{greeting}! Enjoy your Rust"));

I hope Ladybird and Servo succeed. I tried Servo a couple of years ago and it was quite useless, unable to do anything, so I'll have to check back and see how it's doing sometime and see if it's improved.

UPDATE: just tried the latest Servo build on macOS. About 100 MB download, not bad. Started fast. Kind of works. Fast but not very smooth, lots of repaint flashing etc. And text fields and text selection on the web page work poorly or not at all.

I guess they're focusing on interesting internal stuff rather than the basics of loading a webpage and allow you to highlight text and copy it, or click in a text field and edit the text. I wonder whether it will graduate to a real browser sometime.

You have to replace the "T" separator with a space and also any trailing "Z" UTC suffix (and I think any other timezone/offset as well?) for Excel to be able to parse as a time/date.

I was a little confused because when I think of Ractor, it's the Rust "Ractor" library https://github.com/slawlor/ractor which is an awesome library that brings Erlang/OTP gen_server actors to Rust and is very clean. Worth checking out BTW if you use Rust.

It can be overused, though.

Kind of works like Rust declarative macros (`macro_rules!`) in that it is often used to repeat and expand something common across an axis of things that vary.

It's funny that the simple name X Macros has stuck and is a de facto standard. E.g. https://en.wikipedia.org/wiki/X_macro suggests they date to the 1960s.