Its weird to read about Schneider Electric not bothering with brand awareness. They aren't a household brand, sure, but they are well up there with Siemens and the like in industrial/b2b sector and their marketing budget is allocated accordingly.
This superloop pattern can also appear in more abstract scenarios as well.
The wildly popular ESPHome is also driven by a superloop. On every iteration the main loop will call an update handler for each component which then is supposed to check if the timers have elapsed, if there is some data coming from a sensor, etc before doing actual work.
This pattern brings with it loads of pitfalls. No component ought to do more than a "tick" worth of work or they can start interfering with other components who expect to be updated at some baseline frequency. Taking too long in any one component can result in serial buffers overrunning in another component, for example.
In my homelab I've been using very barebones options (the one built into systemd-networkd as well as the dhcp server built into RouterOS) and never found myself needing a web interface, a database or anything… really. It has been sufficient to add the couple dozen static allocations to the configuration files and forget DHCP exists. Even HA is not something I found myself wanting as nodes will retain their lease well over the period of downtime incurred during botched upgrades.
How fancy does a network needs to be before this starts making sense? Who are the target audience for this project?
I’ve hit twice over the last year where it was needed. Though in one case, it’s because a server that was physically old enough to vote happened to be handling dhcp and dns. I set the other, only slightly less old, server to be primary on both but left the original functioning just in case with failed.
The main need I had was for a bank. Network functionality is obviously highly important there. Windows updates impacted the dhcp service on one server, which wasn’t an obvious thing till leases started running out the following morning. Multiple DC’s, so set up for HA to avoid issues in the future. It’s almost never needed but great to have when total uptime is key to operations.
The title qualifies "Android TV" with a "Streaming Box" right after. Lots of service providers supply such a box to subscribers (similarly to how ISPs provide all-in-one firewall-router-modems.) Even then these are extremely cheaply made, underpowered and largely unmaintained internet connected devices. And indeed you can purchase one such box yourself (including with piracy features as described here,) but I'd be surprised if the vast majority of these devices aren't supplied by the service providers.
I would say that npm likely has easier solutions here compared to Cargo.
Well before the npm attacks were a thing, we within the Rust project, have discussed a lot of using wasm sandboxing for build-time code execution (and also precompiled wasm for procedural macros, but that's its own thing.) However the way build scripts are used in the Rust ecosystem makes it quite difficult enforce sandbox while also enabling packages to build foreign code (C, C++ invoke make, cmake, etc.) The sandbox could still expose methods to e.g. "run the C compiler" to the build scripts, but once that's done they have an arbitrary access to a very non-trivial piece of code running in a privileged environment.
Whereas for Javascript rarely does a package invoke anything but other javascript code during the build time. Introduce a stringent sandbox for that code (kinda deno style perhaps?) and a large majority of the packages are suddenly safe by default.
The options in the '70s were much different from those of today. And for France specifically what they have underground (lots of uranium, no oil, no gas & no coal) strongly suggested exactly one way forward.
They’re at ~60% total power from renewables in 2025, and increasing every quarter. I’d say they’re doing pretty well! The coal is unfortunate, but was due to the Ukraine war and gas situation.
This is basically nonsense to the extent that it is becoming difficult to extend the presumption of good faith to you. In the 70s solar panels cost US$25+ per peak watt, in 02021-adjusted dollars: https://en.wikipedia.org/wiki/Solar_energy#/media/File:Solar...
Installing a gigawatt of solar power generation capacity for US$25 billion is in no way comparable to installing a gigawatt of solar power generation capacity for US$59 million.
Wind power has experienced a similar but less extreme cost decline.
Doing a thing involves doing it, but it's very unlikely that doing a thing will involve exactly one atomic movement. So you have cutpoints at doing the thing.
So to do the thing you first have to decide to do the thing. You have to decide what the thing is, or at least have enough of a vision of the thing to take the first step at doing a thing that might look like the thing.
So "doing the thing" involves a lot of doing things that aren't the thing, but without which you won't get towards the thing.
In other words: sitting down and writing down what the thing is _can very well_ be part of doing the thing.
There's a sort of philosophical point too, about whether the thing is what you think it is. Plenty of people have had the "I thought this feature was going to do X, you thought it was going to do Y, and we all realised the mismatch very late in the process".
I think both visions of the world are valid, and things you can keep in your mind at the same time to deploy as needed.
Or you could try and learn by experience. Software is an example, but so could be drawing or composing music. All of those things have been taken to extreme highs by people who had no idea what they were doing.
Becoming someone who can do the thing is how you get to do a lot of things
Not what your boss and your bosses’ boss wants you to do, instead of doing other things you can do to maximize value for shareholders in some arbitrarily chosen amount of time
But thinking of how you wouldn’t have permission to get ready to do the thing in a business context, also, isn’t doing the thing
Back when I had my own Xmonad config – during student years with too much time than I knew what to do with – the biggest benefit to Xmonad being a haskell program that I myself wrote was that it was a program that I myself wrote.
This meant that instead of e.g. spawning some utility on a media key input, the compositor could directly stay connected to the dbus and control mpdris clients directly.
The way I see xmonad in retrospective today is that it is/was a "make your own compositor" library much like wlroots, smithay, etc, but it came with enough of the batteries included in the package that spinning up a nice and productive environment took barely any code. Something you can't really do with wlroots or similar.
They already charge that and more if you have to check-in at the airport for any reason. And you cannot check-in online without making an account with them. Ryanair is grift squared.
That said I never had problems boarding with a PDF displayed on the phone screen. Unfortunate that they're going away.
reply