@bob @tsu Just to interject, the concept of kibbutzim in Israel seems very close to communism in certain ways - collectivism, common ownership, equality. At least it was till the 1970s - though mixing Zionism and socialism may seem strange now.
@delores At least once you make a mistake like that you're less likely to do it again. I reversed a large electrolytic capacitor building a linear power supply once. Bang! Always triple checked after that.
@delores A big issue you may run into is lack of memory. On a machine with 32K RAM, I sometimes ran out of memory when writing documents and had to split them into several files as a consequence. And 5.25" floppys only had around 160k capacity per side, so for a big document you're looking at dividing across several disks. Not impossible to deal with (best that was available at the time and certainly better than the alternative, which was manual typewriting or longhand) but could be frustrating.
I too yearn for the Good Ole Days and wish you well, but I'd plump for an Amiga or Acorn Archimedes for as about as far back as I'd like to go and still be practical for getting work done.
@delores You'd need a C compiler that runs on an 8-bit system and can fit into memory. Might be looking at multiple passes, or a cross-compiler. Back in Ye Olde Days I used assembler when BASIC couldn't hack it. But that was a Z80, which was comparatively rich in registers and instructions. 6502 is basically RISC and quite minimal
@bob Of course it's not just about the language but the entire process of software development. FYI this is interesting about Toyota's ETCS (throttle control) and other software:
- 256.6k non-comment lines of C source code - 67 functions with Cyclomatic Complexity > 50 (considered untestable) - Toyota software had between 9,273-11,538 global variables - recursion prohibited in safety-critical systems due to possibility of stack overflow. ETCS uses recursion. - "technology such as failsafe is not part of Toyota's engineering division's DNA" - internal company mail
You can write safe software in C/C++ (or PHP or whatever) if you avoid the hairy bits _and_ have appropriate processes and discipline. Better languages of course do help you not to shoot yourself in the foot, but without processes and discipline then no amount of language safety will save you.
@bob Admit I did not watch (I hate video) but people like Les Hatton were promoting safer C through avoiding undefined behavior etc. (and there is a surprising amount of this) decades ago. One result was MISRA C, developed by and for the automotive industry in the late 1990s, and still you get shit like Toyota's crappy killer firmware. Unless you're going to change C radically (in which case it is no longer C), writing safer C requires tools and discipline, both of which take time and cost money, so tend to get adopted by aerospace users and ignored by everyone else. https://shitposter.club/url/2320598
@njoseph@dbuntinx@aral As always, it depends on the threat model or your judging criteria. Firefox is open source, but if you read the source you'll find that it's sending a lot of detailed telemetry data back to a central collection point. You can of course disable that, but 99% of Firefox users will be unaware and are being farmed for data in a way that's arguably worse than what Goodle or Facebook does.
@nerthos @hector I use Android's "priority mode", which makes the phone completely silent unless there's a call from a whitelisted contact. Notifications for e-mails and instant messages are completely turned off - I check them when I feel like it.
I really hate the expectation of constant availability and immediate responses that many seem to have. People have been really rude to me on several occasions just because I don't answer to their messages within seconds.