Yeah, I had a silly hack for that. I don't remember what it was. It's been 3-4 years since I wrote bash for a living. While not perfect, I still need to know if a pipeline command failed. Continuing a script after an invisible error, in many cases, could have been catastrophic.
jkercher
joined 2 months ago
Woah, that ((i++)) triggered a memory I forgot about. I spent hours trying to figure out what fucked up my $? one day.
When I finally figured it out: "You've got to be kidding me."
When i fixed with ((++i)): "SERIOUSLY! WTAF Bash!"
I was never a fan of set -e. I prefer to do my own error handling. But, I never understood why pipefail wasn't the default. A failure is a failure. I would like to know about it!
I'll give you my vim when you pry it from my cold, dead hands.
Yeah. Using yocto, I know what I want and can do it in Linux. But, "how make yocto do it" becomes an entirely different thing. It would be nice to have a simple container->image pipeline.
Right now, the most common target we have at work is variscite imx6,7 and 8. Nxp has leaned heavily into yocto. To be clear, this would be an outside of work thing, but I'll probably yoke one of our dev boards.
Hey! I know the guy working on this. Super cool, detail oriented guy.
Ha. I've never used buildroot, but I think I'm going to have a go at it. I promise not to use python ;]
Thank you for the insight.
To me, Microsoft's entire transition to web technologies is a self inflicted wound. Going native is a massive performance win. They already had that, and went the other way. Just, Why!? Now, Microsoft software is all big, bloated, and slow as fuck. Even the OS. They were literally bragging about a 9 second start up time after some optimizations to Teams. They don't even know what efficiency is anymore. We all essentially have super computers, now, but sure, congrats on your 9 second load time for a fuckin chat program.