4 ms·
"There's a loud minority of developers out there who are nostalgic for something they never actually experienced." Having actually experienced it, all the way
by Animats 4y ago
"There's a loud minority of developers out there who are nostalgic for something they never actually experienced."
Having actually experienced it, all the way back to writing business applications in mainframe assembler, I am not nostalgic for it. Today I write mostly in Rust.
- mwcampbell 4y agoLikewise, as a child born in the early 80s, my family's first computer was an Apple IIGS, and I routinely used Apple IIe computers in school from 1st through 7th grade. I wrote Apple II assembler during that time (albeit heavily relying on routines copied from books and magazines). And while occasionally fooling around with an Apple II emulator with an Echo speech synthesizer, or even just listening to one [1], makes me nostalgic for my childhood, I don't miss the experience of actually using or programming those computers. Things are so much better now, even (or perhaps especially) for disabled folks like me. [1]: https://mwcampbell.us/a11y-history/echo.mp3 https://mwcampbell.us/a11y-history/echo.mp3 This file has a real Echo followed by an emulator. Unfortunately, I forgot where I got it, so I can't provide proper attribution.
- dgb23 4y agoI’m from the modern web dev generation so to speak, but just yesterday had an amazing conversation with my dad, who did what you describe. He explained to me what a “patch” actually means, or meant back then. He was talking about debugging and implementing loaders for new hardware and such, then he mentioned a “patching area”, I asked wtf that means and apparently the release cycles then where so slow, that a binary left some dedicated space for you to directly hack in a patch. He then would change the machine code directly to jump to the patched area so he could fix a bug or extend the behavior. Contrast this to the arguably wasteful CI/CD setups we have now.
- mwcampbell 4y ago> Contrast this to the arguably wasteful CI/CD setups we have now. To clarify, are you arguing that modern build and release processes should patch binaries in-place, or something else?
- benreesman 4y agoAs a kind of middle-ground: CI/CD burns our abundant cycles out of band. That’s a good place to spend extravagantly. I’m all for burning more cycles on tests and static analysis and formal verification etc. before the software goes on the user’s machine. But we all live every day with “good enough” on our machines every day. I think there’s a general consensus that too much software spends my CPU cycles like a drunken sailor.
- int_19h 4y agoIt's also the question of what the burned CPU cycles actually buy. Cycles burned on testing buy us less buggy programs. Cycles burned on your CPU that do stuff like out-of-bounds checks or garbage collection also do that. But most of them are burned on layers upon layers of abstraction that do not actually do anything useful safety- or correctness-wise; they're there solely because we've turned code reuse into a religion. Which wouldn't be bad by itself, if that religion had a firm commandment to not reuse bad solutions - yet that is exactly what we keep doing, again and again, patching it all with the software engineering equivalents of duck tape and glue to keep it all from falling apart. Why is C still at the bottom of virtually every software stack we run? Why do we keep writing desktop apps in HTML/JS? Does a simple app really need 20 dependencies of uncertain quality? JavaScript is a good example. It's not a bad language because it's high-level - to the contrary, that's the best part of it! It's a bad language because, despite being high-level, it still gives any user ample opportunities to mess things up by accident. We need something just as (if not more) high level but better for general-purpose software development.
- benreesman 4y agoI like bitching about JS as much as the next guy, and as someone who has implemented ECMA-262 I guess I’m more entitled than most. But let’s not get carried away with it. Eich had 9 days from unreasonable manager to shipping physical media. To do kind of a cool Scheme/Self thing from scratch in 9 days? I’ve been on some high-G burns, but that’s fucking nuts. But since there’s no scientific way to quantify any of this, I’ll throw my anecdote on the scale in favor of my opinion and note that Brendan Eich was a hard-ass Irix hacker at SGI before he followed Jim Clark to Netscape.
- zozbot234 4y agoRust can also be used to write business applications that will compile cleanly to mainframe assembler (at least if your mainframe is 64-bit and runs Linux).
- pjmlp 4y agoThat is better served with mainframe languages, thankfully C wasn't never a relevant language on mainframes.
- dmitriid 4y agoThere were other moments in time between mainframes and today. For example, when I scroll a two-page document in Google Docs my CPU usage on an M1 Mac spikes to 20%. For an app with overall functionality that is probably less than that of a Word 95.