Yes - the idea is that it takes quite a bit of work to create a Meshtastic node on an ESP32 with Arduino. If you just want a basic node that can do things - think about a sensor reading temperature, humidity, etc., maybe accepting incoming traffic for configuration and actuation - it takes a while to do it on an Arduino. With this, you can get up and running in an afternoon.
BTW, looking at the code, I don't think it would take much to bring it over to a different architecture. There are just a few "#if defined(ARDUINO_ARCH_ESP32)" and they seem to be used for RNG and little more. It uses Expressif's mbedtls, but you can use the vendored copy instead (at the monent the vendored version is just used for unit testing). So I suspect that any board supported by arduino-lora should work more or less out of the box.
Reminds me of a quote attributed to Frank Lloyd Wright: "If the roof doesn't leak, the architect hasn't been creative enough." (and he allegedly said to a client unhappy with the leaks in his roof, "That’s how you can tell it’s a roof.")
My point was that, as Martha Gellhorn once said about post-war Germany "No one is a nazi, no one ever was. There may have been some nazis in the next village". Even one's own pictures might get distorted by self exculpation.
Some crow experts discourage feeding them because they can be a bit too much.
OTOH the Swiss Department of Agriculture says that there is nothing that actually works against corvids. You can scare them and you can make their life difficult, but they learn, and show others how to bypass issues (possibly on "Corvid News"), so they might lose some battle but will win the war.
Code that has been tested and hardened for years? Code that is now being audited and patched quickly with the help of LLMs? Why would I worry more about such a code base than something new and not time tested?
New code bases tend to be less secure than old ones regardless of language.
PHP having a security vulnerability related to uploads isn't too shocking and it isn't a sign that C is unsuitable for language implementation. Are you willing to say the same of every other language implemented in C? Are you willing to toss out your OS?
While a safer tool is often a better tool, there are occasions in which the more hazardous tool is the correct tool for the job. If a person is cutting some flooring he/she will probably want to use a miter saw, but for some cuts, a jigsaw is more appropriate. For some applications, Ada, Rust, or Python may be appropriate, but in some situations, a developer needs to reach for ASM or C.
There is a formally proven compiler for a large subset of C, so I don't see why formalizing (a large subset of) rust and making a formally proven compiler shouldn't be possible
Also unlike C, it should be possible to formalize all of Rust, not just a subset. For two reasons: Rust evolution (not initially but today) is strongly tied with formalizing it and the language team consults with formalization experts (which are part of the Rust project themselves) all the time (and formalization or semi-formalization projects are ongoing), and also the mathematical understanding of system languages itself has advanced.
You got my reference. But the original comment stands at -1 points now, even mock criticism of C and Rust seems to be totally unappreciated by the bigots.
There is a severe misunderstanding here. Beside being only a subset, CompCert definitely has UB. It just formalizes codegen for codebases not containing UB, which obviously won't be enough for Rust.
I wouldn't say so. The gap between GCC and Clang/LLVM is bigger than that on some benchmarks, [0] although the gap between their overall performance (using geometric mean) is much less. [1]
It's a very impressive result considering how much effort has gone into GCC. It highlights how compiler optimisation work can face diminishing returns.
> the norm for releases being O2 if I understand correctly
Agreed, but the difference isn't that great. From the article:
> CompCert code is 7% slower than gcc-01 and 12% slower than gcc-02 on average.
Reminds me of how the cproc/qbe C compiler gets very roughly 50% of the performance of Clang/LLVM in 0.1% the lines-of-code. [2]
Maybe we just have different experiences, but I've experienced a huge amount of friction trying to enable features that cost something resembling 0.5% of fleet performance, even when they provide massive benefits. 12% loss would be laughed out of the room.
I agree that this is an impressive feat. I also don't see why an equivalent for rust would be adopted.
> I've experienced a huge amount of friction trying to enable features that cost something resembling 0.5% of fleet performance, even when they provide massive benefits. 12% loss would be laughed out of the room.
A 12% difference in performance between two compilers, for some given application, is possible even between two of the best optimising compilers available. A 12% performance lag does not necessarily relegate a compiler to obscurity.
The long-entrenched MSVC compiler is still a major player despite that, for at least some applications and for at least some compiler versions, Clang outperforms it by far more than 12%. [0][1]
If a new Rust compiler really could offer significantly fewer compiler bugs, that would of course need to be weighed against any performance penalty, and the proper tradeoff would of course depend on the project.
> I agree that this is an impressive feat. I also don't see why an equivalent for rust would be adopted.
I imagine it wouldn't be widely adopted for most applications. CompCert itself is pretty niche. It's not Free and Open Source software, which I suspect is a factor, alongside its technical drawbacks.
Unless you're working on ultra-low-defect software, such as in a safety-critical domain, compiler bugs are unlikely to be a major factor in your software's quality. If the compiler lacks support for interesting language features, it becomes an even harder sell for 'ordinary' projects that are able to tolerate an ordinary number of compiler bugs.
Web apps work on input text and generate text, and C is not the most text-friendly language there is. There is a reason why early CGI-BINs were usually written in Perl.
(I won't even get started on the issues of creating new software in a language that is unsafe by design, and where any performance advantage will be dwarfed by the cost of forking. Whatever floats your boat, dude.)
Really? I didn’t seem to have too many issues with it, especially compared to my experience with the Oculus Quest (where I can get headaches after 10 or so minutes).
After longer sessions with it, sure, but I don’t remember 5 (or even 20-30) minutes giving me issues.
BTW, looking at the code, I don't think it would take much to bring it over to a different architecture. There are just a few "#if defined(ARDUINO_ARCH_ESP32)" and they seem to be used for RNG and little more. It uses Expressif's mbedtls, but you can use the vendored copy instead (at the monent the vendored version is just used for unit testing). So I suspect that any board supported by arduino-lora should work more or less out of the box.
reply