Wow RPI-based QMK-enabled input modules. That is something else.

QMK sounds like the keyboard thing. What things can you do with an arm chip sending input to a laptop? Imagination failure here.

Programmable per-key remapping, layered modifiers that you can toggle per app or workflow (ie. quick language layout swaps, temporary low-level remaps for games that don't support remapping, Blender/Photoshop/editor-specific remaps for personal ergonomics, etc.). Tap-hold functions to send different keycodes or modifiers when you tap vs. hold down a key, often used for home-row mods that move modifier keys into the home row when you hold, say, an HJKL key.

Just curious why they chose RPi instead of cheaper AVR. Maybe because it's more hackable thanks to overkill resources.

I'm saddened to inform you that no scientific research being done these days holds up to these standards.

It's starting to be done in some cases. Look up registered reports.

I'd add that even without registered reports (which are necessary), meta-analyses attempt to cut back on some of the selection bias by scouring the entire literature instead of cherry picking the results that get the most likes on social media.

Actually just today I asked if for the density of silicon nitrite and to cite a source. It cave a citation that seemed correct (reference book on materials) but with completely made up authors.

Yup, works well enough in ST4

I'd imagine distributing tarballs is also an important use case.

Actually zstd makes that worse too, somewhat paradoxically. At least in this case, because Zig uses xz for their tarballs. (If they used gzip, it would be the other way around.)

The reason is that compression algorithms usually can't make further reductions when re-compressing already-compressed files. And xz has a higher compression ratio than zstd, so when you stick zig1.wasm.zst into a tar.xz file, xz is deprived of the opportunity to work its more powerful magic.

As a test, I got zig-0.11.0-dev.638+5c67f9ce7.tar.xz from https://ziglang.org/download/ , extracted it, and rebuilt the tar.xz myself. Then I replaced stage1/zig1.wasm.zst with stage/zig1.wasm and rebuilt the tar.xz again.

Results:

    $ du -sk *tar*
    168136  zig.new.tar
    14500   zig.new.tar.xz
    166416  zig.orig.tar
    14568   zig.orig.tar.xz

So, zig.orig.tar is the uncompressed tarball that contains zig1.wasm.zst, and it is indeed smaller than zig.new.tar. But the .tar.xz files are the other way around.

Not using zstd saves 68K.

=-=-=

Also, in the process, I accidentally discovered something else that makes a bigger difference.

Since I knew the order of files within a tar archive can affect the compression ratio (due to data locality), while doing my test, I used "tar tf" to list my tar file's contents and compare it with what I downloaded. It didn't match, so I knew I wasn't doing an apples to apples comparison.

So I added "--sort=name" to my tar commands. And both of my tar files ended up smaller than the one I downloaded:

    $ du -sk zig-0.11.0-dev.638+5c67f9ce7.tar.xz 
    15152   zig-0.11.0-dev.638+5c67f9ce7.tar.xz

Just adding the "--sort=name" option to tar saves 584K! That's around 4% of the entire tar file. Locality matters more than I thought.

> legal nonsense that allows Elon to call himself a co-founder of Tesla[0]

Wow, I had no idea.

just fyi, you can still write all the Java/Kotlin you want to stay relevant.

this post have nothing to do with writing apps for android. They are talking about developing the android system itself. They are writing new system code in Rust instead of C++. Userspace code is still enoraged to be written in Kotlin.

Good job about asking about concrete pieces of advice, keep doing that and don't shy away from reaching out to people who expressed interest to help. I wasted tons of time trying to figure things out alone from the internet.

I can't directly help you but there were there 2 relevant threads recently.

https://news.ycombinator.com/item?id=33671264

https://news.ycombinator.com/item?id=31577376

FWIW I don't think the macOS + Kafka (professional) userbase needs the shareware model. (I'm in neither groups)

> I think you may need to enforce it once or twice to have teeth

I really don't think that is the point. This seem to be targeted at scaring legal departments to ease over the process of having corps fork over the money for something they might think could be obtained for free.