jkercher

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

They are also dev friendly too,

Not saying you're wrong because I don't use it, but from the outside, they appear actively hostile toward developers.

[–] jkercher@programming.dev 5 points 1 week ago (1 children)

We are eventually going to stop writing code and focus more on writing specifications.

I don't think this will happen in my lifetime.

[–] jkercher@programming.dev 5 points 1 week ago (4 children)

100%. In my opinion, the whole "build your program around your model of the world" mantra has caused more harm than good. Lots of "best practices" seem to be accepted without any qualitative measurement to prove it's actually better. I want to think it's just the growing pains of a young field.

[–] jkercher@programming.dev 18 points 1 week ago (1 children)

You shouldn't have any warnings. They can be totally benign, but when you get used to seeing warnings, you will not see the one that does matter.

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

And, you can have pointers to bits!

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

Algorithms + Data Structures = Programs

Niklaus Wirth

[–] jkercher@programming.dev 36 points 4 months 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 5 months 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 5 months ago* (last edited 5 months 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 5 months 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 5 months ago (1 children)

She already exists! I swear!

[–] jkercher@programming.dev 13 points 6 months 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.

6
submitted 7 months ago* (last edited 7 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 ›