Ruby, Rust, and electronics
Leeds, UK - he/him
Mastodon: @aaronc81@ruby.social
You can't do something like this in OpenSCAD unless you also pass a separately-calculated size for the children.
You can't do something like this in OpenSCAD unless you also pass a separately-calculated size for the children.
On the software side, it only needed some little tweaks to support the extra three keys, and swap to active-low because it made the wiring easier.
On the software side, it only needed some little tweaks to support the extra three keys, and swap to active-low because it made the wiring easier.
So I remade the plate to have the Pico integrated, which made the wiring much easier!
The blank space doesn't look too great, but I can always vinyl-cut something to go there
So I remade the plate to have the Pico integrated, which made the wiring much easier!
The blank space doesn't look too great, but I can always vinyl-cut something to go there
Embassy makes USB device implementation pretty straightforward 🦀
Embassy makes USB device implementation pretty straightforward 🦀
First steps - a 3D-printed plate with hardwired Gateron Browns (with jumpers I now realise I’ve made far too long)…
First steps - a 3D-printed plate with hardwired Gateron Browns (with jumpers I now realise I’ve made far too long)…
I mocked up Cura for Windows 95
I mocked up Cura for Windows 95
…and it just got an entire second map as a free update. Time to 100% complete this too 😁
…and it just got an entire second map as a free update. Time to 100% complete this too 😁
An example in Swift - variables named “of” and “with” would be unintuitive inside the function body, but read naturally when calling
An example in Swift - variables named “of” and “with” would be unintuitive inside the function body, but read naturally when calling
Gleam doesn't have early returns, so you don't need to worry about that skipping your clean-up.
Gleam doesn't have early returns, so you don't need to worry about that skipping your clean-up.
For example, error propagation through the `Result` type, which replaces a dedicated "try" operator:
For example, error propagation through the `Result` type, which replaces a dedicated "try" operator:
I like a lot of its ideas, it's the closest I've felt to writing "garbage-collected Rust". My favourite trick is the `use` keyword, which is like a generalisation of JS' async/await transform:
I like a lot of its ideas, it's the closest I've felt to writing "garbage-collected Rust". My favourite trick is the `use` keyword, which is like a generalisation of JS' async/await transform: