3,032 karma · joined September 30, 2016
If you've heard music from the Sega Genesis, that's the same Yamaha FM Synthesis technology (details differ, of course).
So, games would often support different audio hardware. Here's a favorite:
https://www.youtube.com/watch?v=1IOL4q5tDDQ (Secret of Monkey Island theme, PC Speaker)
https://www.youtube.com/watch?v=8qpB-HAZsRs (Secret of Monkey Island theme, Adlib/OPL2/FM synthesis, common option for PC sound hardware)
https://www.youtube.com/watch?v=i3dB0qEcG20 (Secret of Monkey Island theme, Roland MT-32/Linear Arithmetic synthesis, premium hardware, likely what the music was originally composed for)
I'm about 20 minutes away (each) from 3 different theaters, so watching a 30-minute chunk of movie is 70 minutes of my time (ignoring parking, unusual traffic, ticketing, etc). I'm not going to commit to doing that 3 times.
> IRC and AIM in the 90s/00s were the big drivers for fast typing.
Those are how I developed my touch typing; the incentive was to see everything happening in the chatroom full of friends without missing anything, and being able to react quickly.
> The tactile response and feel of an electric typewriter is pretty cool.
Granddad was a retired IBM employee, and had a Selectric typewriter (either II or III, not sure). That thing felt (and sounded) awesome. The whir of the flywheel, the amazing feedback of the "thunk" of the ball hitting the ribbon. I used to type random crap that didn't need to be typed just to use that thing for a few minutes.
So, yep, ancient version of Linux.
One example: https://www.technologyreview.com/2023/05/01/1072478/deep-lea...
> And more generally, doesn't AI allow more people to never retire?
I don't understand what you mean. It's arguably forcing some people out of work. And I'm not sure what about "AI" (I'm supposing you mean specific techs like LLMs?) would help people not retire...or why that would be a good thing.
That's a great description of literally the only use I have for streaming services.
I think for a lot of the people who "just want to make a game" (often engaging with programming only as a barrier to their goal), a pre-built engine is limiting...but it also lowers the barrier for entry. The game-making community increases in size as a result, but a lot of the increase is the population of developers who really look at building your own engine as some kind of black magic, rather than something that's in their power to design and write.
I don't know how common that is anymore; as you've noted, a lot of companies de-emphasize the need for a dedicated QA team.
I think it's more like saying that I enjoy playing those games with zero mods (which is true).
> what makes the game appealing.
To you. I see it as a big Lego bin that you explore for parts, and build creatively within the limitations. When I play it, honestly I play it a lot like I did 15 years ago, just with more variety and options added to the base game since then. Build a fun base, explore around, dig a crazy-looking mine, build a railroad to a few villages, build some redstone-controlled automatic doors or something...
I'm rarely on the Java version anymore though; most of the appeal now is playing with my kid, who primarily has access to Bedrock, via tablet.
> I would guess that Microsoft discontinuing support for VR [...]
Could be. I just bought a used PSVR a few months ago, and VR Minecraft on PS4 was a mix between pretty cool, slightly janky, and slightly nauseating. I'm glad I got to try it for a bit before it disappeared, but I can see why it wouldn't be that popular.
All of the code that I've generated by LLM has backed itself into a corner very early on, so I tend to use that as a starting point, then fix and refactor. I've made some toy-sized programs that way (but hours quicker than I would've looking up library documentation on my own).
I've had good luck refining my understanding of some concepts, talking through design of pieces of code, and basically generating snippets of example code on demand. Even in those limited cases, I end up relying on my own experience to determine what's helpful and what's crap. They're usually intertwined.
It's a piece of art, both aesthetically and technologically. Beautiful how it fits together. Getting this kind of behavior out of so little code always amazes me.
And then, after working like that for a couple hours, my brain flips and I need as close to perfect silence as I can get, so I pause the music.
And in 2004, didn't have a published specification, or much use outside of webdev (which hadn't eaten the world yet).
> and SAX parsers are 22
And, especially at the time, pretty much exclusive to Java, right?
Put another way, which are the high-quality open-source implementations of those formats that the developers should've considered while working on SA in 2003 and 2004? Or for that matter, in the 2001-2002 timeframe, when the parsing code was probably actually written for use in VC?
I don't see what "AI" has to do with the situation.