Yes, that contributes to the "if it actually worked" sentiment.
It doesn't have to be slow, if the browser exposed C-like ABI for DOM access and web APIs like LocalStorage, the FileSystem API, ServiceWorker, etc - Rust bindings can be made and that boundary could be well optimised.
I'm blanking on the exact models I used; I'm fairly certain they were tds700s or tds71xx, but a lab I ran had about a dozen units and we had nothing "fry" in the 4 years I worked there. What applications would result in these catastrophic failures?
We had some "ghosting" on the displays on a few now that you mentioned it, but they were still 100% usable. I guess my expectations were lower since I never had to foot the bill for the lot of em (which at 20k/unit I guess I'd be upset about when one was faulty)
I recently performed this exact exercise of converting a complex library set from one language into an intermediate state machine representation and then translated into N other languages. It worked well but there's a lot of caveats. I'd highly recommend a direct "port" in most cases tbh, as many bugs are "load bearing" and may not survive the intermediate translation. I speak from experience.
Are you implying a direct bug for bug port is more expensive than converting to an intermediate representation and then converting via generators? Depending on the "fidelity" of the representation I'd figure the costs are about the same.
My understanding is, direct port is more expensive besides toy projects of course, looking at Bun and also listening to people who've done a few language conversions, they extract something first.
If not an intermediate representation, my first question would be: how to split the work. You cannot just prompt full rewrite of 60K LoC, you cannot do it module by module — modules do translate 1:1, like in my case golang packages did not matched Rust crates. Bun did file by file.
With hierarchical state machines in the middle, I did it almost in one shot.
As an avid dog owner I ensure my pets have a rich home life. However, at this point in my life I've seen countless pet owners callously fall short of providing even basic pet needs: walks, enrichment activities, etc. (I've fostered and adopted multiple rescue dogs)
I welcome a humane substitute for those without the time or understanding to properly care for another living creature. Mostly people should not be allowed to have a living pet.
I maintain(ed) node bindings[1] for the old Roomba din OI serial protocol. Although it's targeting the old "create" educational series, it actually works on all Roombas predating the 900 series!
I've been keeping bees for well over a decade now, and Varroa mite management and prevention of downstream disease vectors like deformed wing virus are consuming ever greater amounts of our time and concern in the community.
Personally, I've tried a number of mitigations with varying levels of success--most all resulting in requeening due to toxicity of treatment. At this point unless a truly successful new therapy is found it seems like a losing battle tbh. I meet monthly with beekeepers and scientists monthly for a few years now, an 99% of the time discussions involve Varroa destructor. It has that name for a reason...
Analog to digital converters (components generally built-in to uCs and SoCs but you can make them using simple resistor ladders) have common resolution ranging usually from 8bit to 24bit in most consumer hardware.
Resolution of +/- 500g just means there's not enough "steps" values in your ADCs provided bit depth: for example the 10bits on an attiny85 gives you 1024 discreet values you can map to weight values etc.
reply