> Programming 6502 seems simpler than learning lets say JS framework or to learn just about anything modern.
Vast, complex, changing APIs make programming unfun. Retro machines were fun because the things to learn were concise; the rest was up to your thinking.
> if we had forced the peaches to be grown and canned (as many comments are suggesting) then that would be a different kind of waste as they'd sit in warehouses while the land, resources, and labor were used to produce something people weren't buying instead of being used to produce foods they were buying.
Worse, the price would have to be lowered to bring up sales, which could put the other peach farmers into bankruptcy as well.
If you try to force production and sale hard enough, the sale price can even go negative.
If your warehouse is full of peaches nobody wants, you might be forced to sell them for negative dollars to take them away. It's either that, or you pay to have the waste management company dispose of them. So the price effectively goes negative from trying too hard to force something to happen.
Similarly, in 1790s America, farmers west of the Appalachians were growing plenty of corn, but because of bad roads the only feasible way to transport it to the much larger markets east of the mountains was as whiskey. When Alexander Hamilton imposed a tax on distilled spirits, the result was a "Whiskey Rebellion" in which George Washington himself rode out at the head of an army against other American citizens.
This type of trivia is why I found Bill Bryson’s “At Home” so entertaining. Tariff on windows? People cover them with bricks. Tariff on glass? Windows made of other materials. Tariff on… well, maybe stop designing tariffs if you can’t predict the outcome!
The price of oil going below zero during the pandemic was one of the most astounding economic events in my life. I wonder if anybody did try to instantly create some storage to take advantage of it.
>Worse, the price would have to be lowered to bring up sales, which could put the other peach farmers into bankruptcy as well.
We run into something similar every year here in India. One recent example [1]
This year it is the Middle East crisis. Last year it was probably a glut because there was shortage the year previously.
I also found the 6502 far more enjoyable. It feels like a refined, minimal design, since the Z-80 does bolt things on to the 8080 (which I've also coded a lot for, also not as enjoyable). There tends to be one straight-forward way to code things, that's also the most efficient, barring changing the algorithm or twisting the design. Instructions tend to use one cycle per memory access, and memory accesses are mostly as expected, e.g. load A from 16-bit address is four cycles: the LDA opcode, two-byte address, and byte loaded. The Z-80 suffers in this regard because like the x86, it uses 1-2 bytes for the bolted-on instructions and modes, so some seemingly similar instructions can use a different number of cycles (e.g. ld hl,nn and ld ix,nn take different times, even though they both load a 16-bit value into a register).
If any program I used moved my mouse pointer regularly, I'd quit using it. This is right up there with programs that move UI elements around or pop them up as I'm trying to interact, causing the wrong actions to occur.
> This is the actual Notepad++ codebase ported to run natively on macOS. It is not a knockoff, a Wine wrapper, or a new editor that imitates Notepad++.
Why not just say "No, this is not Notepad++ for Mac. It's my own port of the code from Notepad++." It still sounds like he's trying to pass it off as the actual Notepad++.
Apparently he agreed with me because he's eliminated that question and wording, with no trace I can find of what I quoted. The other language is irrelevant to what I quoted.
More simply, most interesting operations will involve "mixing up" of data. There's only so much you can do by applying a bunch of operations in series with a single input value.
reply