Optimizing a 6502 image decoder, from 70 minutes to 1 minute

Re:Optimizing a 6502 image decoder, from 70 minutes to 1 minute by inopinatus on Monday September 29, 2025 @01:46PM (#45416641)

The painful thing is when someone describes themselves as a “full stack developer” but lack any mechanical sympathy for what the processor, memory, and I/O buses are actually doing.

This doesn’t require a formal education. I was self-taught long before studying CS institutionally. And per the article I am super grateful to the 6502 for being the platform that I learned from.

[ Parent | on HN ]

Re:Optimizing a 6502 image decoder, from 70 minutes to 1 minute by pixl97 on Monday September 29, 2025 @03:16PM (#45417626)

I mean, no, that's mostly not what I'd consider a full stack developer myself and I've been around a long time. You can be full stack grabbing everyone else's libraries and making an app spit data from the db to the UI.

Simply put the vast majority of developers will never need this information nor be resource constrained that they'll need to use their time to understand the issue deeper.

[ Parent | on HN ]

Re:Optimizing a 6502 image decoder, from 70 minutes to 1 minute by inopinatus on Monday September 29, 2025 @04:16PM (#45418228)

That anyone felt the need to justify mediocrity merely confirms the extent of the problem.

[ Parent | on HN ]