jkercher

joined 3 months ago
[–] jkercher@programming.dev 37 points 2 days ago (2 children)

60k rows of anything will be pulled into the file cache and do very little work on the drive. Possibly none after the first read.

[–] jkercher@programming.dev 7 points 1 week ago

Meh. I had a bash job for 6 years. I couldn't forget it if I wanted to. I imagine most people don't use it enough for it to stick. You get good enough at it, and there's no need to reach for python.

[–] jkercher@programming.dev 7 points 2 weeks ago* (last edited 2 weeks ago)

Heh, the red alert readme says it currently requires borland for the asm and watcom compiler for the c/c++.

[–] jkercher@programming.dev 2 points 1 month ago

I'm on your side dude. Comments rot. Some are useless. Don't even get me started on doxygen comments.

[–] jkercher@programming.dev 3 points 1 month ago (1 children)

She already exists! I swear!

[–] jkercher@programming.dev 13 points 1 month ago (2 children)

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.

[–] jkercher@programming.dev 3 points 2 months ago

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@programming.dev 1 points 2 months ago* (last edited 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!"

[–] jkercher@programming.dev 4 points 2 months ago (2 children)

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!

[–] jkercher@programming.dev 11 points 2 months ago

I'll give you my vim when you pry it from my cold, dead hands.

[–] jkercher@programming.dev 1 points 2 months ago

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.

[–] jkercher@programming.dev 2 points 3 months ago* (last edited 3 months ago) (1 children)

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.

6
submitted 3 months ago* (last edited 3 months ago) by jkercher@programming.dev to c/embedded@programming.dev
 

Hello all, I'm an embedded software guy struggling with Yocto. I'm not asking for assistance as I cannot be saved. Rather, I'd like to make my own. How hard it would be to put a Linux distro onto a device without it? For example, if I were to get a perfectly good distro (let's just say Debian) with the right architecture going in a container. Is there a simple way to combine that with u-Boot, and other crap from a SoC manufacturer to build an image? If that is oversimplifying, I've done Linux from scratch before, and I'd be willing to go that route as well. I guess the issue boils down to the specifics like building the image and anything else that I'm not aware of.

So, what part of this idea is going to be a lot harder than I'm giving it credit for?

By the way, I'm aware of Buildroot. This is more for learning purposes, and who knows... maybe I will actually make something out of it.

view more: next ›