I/O and logic for an MCU. The hardest bits, TBH, are already done with the ESP32 series MCUs, thanks to the efforts to get the Rust stdlib and HAL supported. So, the experience, code-wise, isn’t much different from Arduino or Micro/CircuitPython. Mostly, it’s down to syntax, flashing toolchain, and logic.

So, the experience is likely to be similar to development on with a full-fledged CPU/SoC target. I’d suggest that the experience of developing for an MCU, regardless of language, is likely to put one up against constraints that will make them think more about resource management considerations when approaching other target platforms.

Do you think programming an ESP32 is a good project for learning rust?

I’ve only barely scratched the surface there myself but, I absolutely do think so. For several reasons. First, ESP32 is one of the few series of MCUs that support the Rust stdlib. And learning what that entails for Rust is extremely helpful in conceptualizing build targets. Second, MCUs are a very constrained target for software/firmware. Getting comfortable there will likely improve your code efficiency in other code platforms as you are more likely to think about resource usage earlier. And third, there’s some pretty excellent docs and tutorials.

Any suggested place to start? (Tutorials, YouTube Vida etc)

For tutorials, my recommended starting point is with the official docs/books themselves:

• https://doc.rust-lang.org/book/
• https://docs.rust-embedded.org/book/

That’s fair. To be clear, I meant minimal experience with the Rust programming language. I’ve mainly tinkered with ESP32 types of MCUs in Arduino and CircuitPython when it comes to firmware, but have much more software experience. In some ways, I found the little bit of Rust that I tried easier because of the tooling - defaulting to a CLI tool to flash rather than an IDE is much more comfortable for me.

Given the state of fiber, I’m not optimistic.

If the target for the firmware has stdlib already implemented, my experience has been that it is indeed easy with minimal experience in the language.

It’s actually more of an issue of artificial supply and demand caused by a monopoly that controls ticket sales, secondary market, and venues. They’re also very hostile to performing artists, using their monopoly to force them to play more expensive venues and charge higher prices or risk blacklisting at virtually every major venue. It’s the kind of shit that anti-trust laws were created to prevent but, there has been little to no enforcement for near a half of a century.

(with lasers): “How about now?”

Democracy cannot function when people no longer believe that their opponents are acting in good faith. It’s a prelude to secession or civil war.

And, when there’s concrete evidence that a faction has not been acting in good faith for half a century at the least?

This is usually the cause, in my experience.

GUIX is a good example.

Don’t say ansible. It’s barely declarative.

True, but it uses a common language in its Playbooks, which is a significant advantage. I’d like nix if I didn’t need to use nix the language. It’s great concept and the portability is awesome.

To me, 1400 projects is just an insane number, and it’s only possible because they are all so trivial.

Holy shit. I’m going to have to go through my team’s dependencies. I don’t feel confident that someone “maintaining” that many projects is going to be able to keep all bad actors at bay. Not to mention, none of the examples of his libraries that I’ve seen SHOULD be libraries.

And anyone who has been around for a while should remember when left-pad broke node.js. Including unnecessary dependencies, instead of writing trivial code is just bad practice.

I don’t get the concept that depending on 7 lines of code from a third-party package is remotely acceptable. It’s expanding the potential attack surface to save a dev from templating 7 lines of boilerplate. There’s no net benefit or appreciable time saved.

I’m glad I don’t have to deal with this regularly.

ETA: The package is even MIT licensed! There’s no excuse but laziness and not wanting to understand the code to import this rather than inlining or implementing a novel version. If I can spend the time to write:

if err != nil {
  slog.Warn("well shit", "error", err)
  return err
}

after every function call…I just didn’t get it.

In the US, property owners do indeed have some degree of rights over low-altitude airspace. The FAA states that one should have permission before intentionally flying over private property. In addition, a large number of states and municipalities have drone-specific surveillance, harassment, and privacy laws, so, it’s a fair change that those may apply. Any commercial drone operator that violates local laws in course of their flight is likely to run into trouble with the FAA too.

If the drones are flying over private property without explicit authorization, the FAA may be a good place to start.

This is nothing but rent-seeking.

In this case, I think “no distractions” is the goal. It’s running on an ESP32 microcontroller, not even a full-blown SBC computer like a Raspberry Pi. It’s probably a good choice for such a device but I also don’t feel terribly blown away by the price. But, thinking about it, it is a mechanical keyboard with a display that runs about $90, so, not an unfair price, but, certainly not low-cost.

The only reason that I tend to use it is because of the included webserver. It’s not bad but the paywalling of functionality needed for it to be a proper LB left a bad taste in my mouth. That and HAProxy blows out of the water in all tests that I’ve done over the years where availability is at all a concern. HAProxy also is much more useful when routing TCP.

Honestly, from your description, I’d go with Debian, likely with btrfs. Would be better if you had 3 slots so that you can swap a bad drive but, 2 will work.

If you want to get adventurous, you can see about a Fedora Atomic distro.

Previously, I’ve recommended Proxmox but, not sure that I still can at the moment, if they haven’t fixed their kernel funkiness. Right now, I’m back to libvirt.

That’s just called Update Tuesday.