Ricky Munroe
rimunroe.bsky.social
Ricky Munroe
@rimunroe.bsky.social
I should clarify that the brand’s name is WaterFurnace
December 13, 2025 at 3:48 AM
This is the app for controlling our heat pump
December 13, 2025 at 3:47 AM
Karl Marx’s contributions to the culinary landscape are often overlooked
December 11, 2025 at 3:59 AM
We have three 300’ vertical wells in a closed loop. There was an impressive amount of water which came up from the aquifer during drilling
December 4, 2025 at 8:42 PM
Yep. We disconnected about 90’ of radiator for this project
December 4, 2025 at 8:10 PM
Anyway watch @techconnectify.bsky.social’s series on heat pumps. It’s very good: youtube.com/playlist?lis...
Heat Pumps - YouTube
youtube.com
December 4, 2025 at 7:19 PM
It looks like heating the house is drawing 700 watts right now. I don’t know how much we would have used on a similar day in the past, but we would always have at least a couple of the electric heating circuits running at any given time to heat rooms to a lower temp. Those things draw a LOT of power
December 4, 2025 at 7:17 PM
So long 11 independent programmable thermostats. You will not be missed, especially when changing between standard and daylight saving time
December 4, 2025 at 6:58 PM
I wish they’d kept adding to the titles as things went on. We could have had Dark Forces 2: Jedi Knight 2: Jedi Outcast 2: Jedi Academy
November 1, 2025 at 3:04 AM
A build not breaking when an unrecognized directive is encountered does feel like a bit of a problem, but it’s a familiar one. Every project I’ve worked on has had a linter which would catch unused expressions
October 30, 2025 at 1:12 PM
I’m concerned about namespace collisions, but that has nothing to do with these things being represented as string literals
October 30, 2025 at 1:06 PM
In a relatively “normal” module import, you can’t know what version of something you’re pulling in is without inspecting something like package.json. Module aliases and bundler configs make this even more complicated
October 30, 2025 at 1:06 PM
Other than not being sure if it’s a native browser feature, I’m not sure that this is much different from the rest of the story of modern JS given heavy use of bundles and pre-processing tools
October 30, 2025 at 1:06 PM
I don’t understand people who think that it’s safer to write some characters if they don’t have quotes around them. The quotation marks are not the problem! If you were able to manipulate the strings that would be a problem, but you can’t. They’re extremely easily statically analyzable
October 29, 2025 at 10:46 PM
answer: it's rust! by a lot. on my machine, haskell took ~8.8μs, ocaml took ~10μs and rust needed a whole *108μs*.

the interesting question is *why* rust is so slow though and it has a really nice, simple answer: with rust's iterators, this code is quadratic.
pop quiz: you are consing 1000 elements to an iterator. which language's iterator implementation is the *SLOWEST*?

1️⃣ <a href="https://poll.blue/p/HGXg5v/1" class="hover:underline text-blue-600 dark:text-sky-400 no-card-link" target="_blank" rel="noopener" data-link="bsky">Rust (with Iterator::chain)
2️⃣ <a href="https://poll.blue/p/HGXg5v/2" class="hover:underline text-blue-600 dark:text-sky-400 no-card-link" target="_blank" rel="noopener" data-link="bsky">Haskell (lists)
3️⃣ <a href="https://poll.blue/p/HGXg5v/3" class="hover:underline text-blue-600 dark:text-sky-400 no-card-link" target="_blank" rel="noopener" data-link="bsky">OCaml (Seq.t)

📊 Show results
October 20, 2025 at 6:54 PM
If it helps they don’t say “duh”. That would be insane. They say “bah”/“buh” as god intended
October 14, 2025 at 4:59 PM
Right, which is what I was talking about here, except iOS additionally blocks iBeacon protocol stuff behind fine-grained location permissions separately from Bluetooth as a whole, which I think is a strict improvement bsky.app/profile/rimu...
All that said, I much prefer what I understand to be iOS’s approach, which is that iBeacons are locked behind the location service permission which is separate from the general Bluetooth permission
October 3, 2025 at 3:03 PM
One certainly could follow that logic that far, but I don’t think that would be a pragmatic decision.
October 3, 2025 at 2:56 PM
A) I don’t think much expertise is needed to do that 😛, and B) I didn’t say I liked it. Like I said, from my understanding I believe iOS’s more restrictive permissions are clearly better when it comes to this
October 3, 2025 at 2:56 PM
All that said, I much prefer what I understand to be iOS’s approach, which is that iBeacons are locked behind the location service permission which is separate from the general Bluetooth permission
October 3, 2025 at 2:29 PM
I gotchu, I just meant that Bluetooth devices are used as location trackers quite frequently. It’s easy to see why they’d lump those things together since a lot of people don’t seem to know that Bluetooth devices can be used for that (as this thread demonstrates 😉)
October 3, 2025 at 2:25 PM
Presumably that’s about iBeacons, which are BLE devices used so apps can track location even when location services are unavailable or not precise enough
October 3, 2025 at 8:00 AM
Looks like there was a lawsuit where Burton’s company was sued by the original production station and lost the rights to Reading Rainbow as part of a settlement
September 29, 2025 at 6:24 PM
I genuinely don’t know how they managed that because it seems like one of those bugs which would actually be significantly trickier to implement architecturally than not
September 29, 2025 at 3:30 AM