couchand

35 ms·

481.
by couchand 5y ago
Promised?
482.
by couchand 5y ago
I started contracting at about the same point in my career. I'd been at four different companies, two of them pretty big places where I took on mentorship roles. Over time I'd built up a list of colleagues (a rolodex, if you wil
483.
by couchand 5y ago
I would suggest it's just as rare to read a math book from start to finish...
484.
by couchand 5y ago
You also aren't directly editing the observable runtime behavior of the system, yet programmers seem to be able to handle that jump regularly.
485.
by couchand 5y ago
As the linked article points out, it's bracken ferns that have been linked to cancer. If the ostrich fern suggested in the OP is also a carcinogen, the Smithsonian article doesn't mention it.
486.
by couchand 5y ago
This is a good point to bring up but kind of lands in a different place than the GP's argument. Cars aren't boosted because a rational analysis has determined that the negative externalities are worth it; rather, cars are boosted
487.
by couchand 5y ago
Go is also known for treating developers like cattle, so, I'll take Rust's trade-off, thanks.
488.
by couchand 5y ago
Yes, the third party we should use to evaluate is definitely the one the manufacturer wants you to pay attention to.
489.
by couchand 5y ago
Good point. Though you can always link to .S for that last bit, right? I don't mean to tell you your business, I know you folks are doing much more intense stuff than I am. It doesn't surprise me that you'd know exactly what
490.
by couchand 5y ago
For AVR specifically, no. The Embedded Book [0] (which uses the ARM-based Discovery board) is a great introduction. I can envision a future where clean abstractions are written that can provide an Arduino-like experience in Rust, but we ar
491.
by couchand 5y ago
Depends on the architecture: ARM for instance is a tier 1 target and you can use stable.
492.
by couchand 5y ago
Do you have experience with AVR assembly and calling conventions? There are only a handful of us looking at this issue, none of us have much bandwidth and we could definitely use your help!
493.
by couchand 5y ago
> will rust be viable on a puny AVR There's still plenty of lingering issues (to name just the most glaring, you can't use a compiler since nightly-2021-01-07), but you certainly can use Rust for AVR. I've been writing al
494.
by couchand 5y ago
Sounds like the premise of David Macaulay's Motel of the Mysteries.
495.
by couchand 5y ago
Then you might appreciate this line of shirts from Iowa's biggest little t-shirt company: https://www.raygunsite.com/products/ohio-1
496.
by couchand 5y ago
That's a style of silly complaint that The Simpsons already addressed: "Stop besmirching the house!"
497.
by couchand 5y ago
I do like the sound of "jazz cabbage", but I think you're using it derisively and possibly with a tinge of racism. And that makes me sad.
498.
by couchand 5y ago
I spend a lot of time thinking through problems with pen and paper, and also highlighter and printer, and whiteboard. I've found this class of tools often lets me focus on a problem with less distraction. It's not always the righ
499.
by couchand 5y ago
For what it's worth, I think of Rust as simply encoding modern C++ best practices in the compiler and dropping all the old cruft.
500.
by couchand 5y ago
Intuitively I feel there's a big difference between my glasses and your ligatures, but I'm having a hard time putting my finger on it...
501.
by couchand 5y ago
> Should we all just be programming on pen and paper because that’s lower down the progression stack and has less chance of failing? Yes. Not because of the resiliency (it's hard to imagine a failure mode where pen-and-paper progra
502.
by couchand 5y ago
The best programmers I know are able to see through the abstraction and are comfortable getting into the lowest-level details. They have those skills because they've actually used them. I'm not saying we'd be better off with
503.
by couchand 5y ago
Also see https://docs.rs/dtolnay/0.0.9/dtolnay/macro._02__reference_t...
504.
by couchand 5y ago
Weirdly, it's already significantly easier to find Rust (or Rust-interested) developers these days than C/C++. If your main concern is being able to hire devs then Rust is a clear win. And don't sleep on Sealed Rust. They&#
505.
by couchand 5y ago
> Of course Rust offers more than mere package management, Cargo is also the build system, it also has support for automated testing and documentation. All of these things are typically afterthoughts at best in many embedded projects. Co
506.
by couchand 5y ago
> the only synchronization issue is between interrupts and main program, a case rust doesn't handle afaik(?) and in 99% of the cases a ring buffer or simple flag variable is enough. I'm not sure what you're expecting it to
507.
by couchand 5y ago
The API generated by svd2rust isn't ideal. There's been lots of discussion about ways to improve it, but unfortunately not all that much experimentation of alternate models. So the ubiquitous option generally wins, in a worse-is
508.
by couchand 5y ago
But the C++ example does indeed make sense in Rust, if implemented appropriately. Sometimes you need an atomic, and the type that contains one should require no further synchronization. In both languages it's an equally useful tool.
509.
by couchand 5y ago
Strange choice of demonstration, then. The C++ example is thread-safe, so you don't demand any further synchronozation from the caller. The Rust example, by contrast, DOES demand additional (superfluous) sychronization by the caller
510.
by couchand 5y ago
The author seems to have missed that operations on atomics in Rust don't need &mut references.

More ›