> Less immediately visible to someone working at the assembly language level instead of the machine code one is that relative addressing is much more common on the 6809, meaning that it’s significantly more viable to write position-independent code on it than any of the other chips we’ve looked at here. Only the 8086 comes close, and it achieves it by using its segment registers as a de facto relocation base.
I would love to learn more about this. Does more "position-independent code" mean the linker has much less to do [0], or is there an actual difference in the code base for similar tasks?
In terms of "safety" this leak is a drop in the bucket. The greater concern would be that election systems are involved. If election information is unintentionally readable, it is also therefore potentially alterable.
Agreed, how HolyC serves as an inspiration could be clarified. Was it an aspect of HolyC? The background/context of the author's life, meaning Terry Davis was inspirational? Impossible to tell. Other resources [0] [1] don't mention this aspect.
> Be welcome to the exciting world of graphical C applications using SDL (Simple DirectMedia Layer). SDL, originally developed by Sam Lantinga in 1998...
This is what I've been wondering after only a cursory glance ("It...generates optimized C code" from the OP). Interesting that mruby itself got a major version update around the same time (in just the past few days) https://github.com/mruby/mruby/blob/master/doc/mruby4.0.md
It looks like magic because it works like magic. Surprisingly it is also possible to believe in the magic of "government intervention" though it looks less like magic and more like unintended consequences.
> The farm equipment industry spent 20 years adding complexity and cost. Ursa Ag is wagering that a significant number of farmers never wanted any of it.
Nice tag line but not a complete picture. The "significant number of farmers" in terms of actual market spend driving the equipment industry is not mom-and-pop outfits but rather agri-industrial complexes with machines to match. What they want is (1) availability and (2) ROI. For (1), that is first and foremost subject to legal stipulations like EPA etc, then secondly subject to production availability. For (2), electronics are the name of the game if you are looking to turn a profit with farming because counting every seed, measuring every drop of chem, and tracking every inch of plotted ground leads to better ROI.
> Interest per Second - General - The U.S. pays $31,688/second in debt interest — $1,901,285 every minute. Your share of that: $3893.33 [plugged in "normal" amount], gone before it bought anything.
...I thought I was already sufficiently terrified by the debt numbers...
By the way, the 1040 instructions have a pie chart like this (ref https://www.irs.gov/pub/irs-pdf/i1040gi.pdf, page 122). Not that most people do taxes themselves, or have a reason to read to page 122 of instructions for a single form. But still it's there and perhaps a nice gesture by the IRS.
Breaking it out into pie charts etc like this can be really helpful. In my view the real kicker with taxes is the opaqueness. Kinda like a meal card versus paying for every meal, or like using a credit card versus paying with cash, it's hard for humans to really grasp what's going on unless they're involved.
Of course it would be impractical to pay taxes separately to every waiting hand in government bureaucracy. But on the other hand maybe the number one goal shouldn't be ease of use, either. Maybe a little friction when paying for public services could be a good thing for citizens who are interested in a healthy country - my opinion.
https://www.openbsd.org/
https://en.wikipedia.org/wiki/OpenBSD#Security_record