I've had to interact with too many people who say this with a straight face.
Not bad overall, although I don't know where they got that "Atari 2600 Pitfall" screenshot. Not only is that not taken from the actual game, the 2600 couldn't display that image. It looks like someone who mostly remembered the game drew it from memory in MS Paint.
If you might be interested but don't want to click a random link without knowing what it's for, this is a video about the history of a Mario 64 speedrun category, 120 stars, which involves collecting every star in the game.
I think it depends a lot on a person's individual knowledge. If you keep studying far enough away from your main area of expertise, there'll still be some point where you stop and have to blindly accept that something "just works", but it will no longer feel like that's what your main field is based upon.
Imagine a chef. You can be an OK chef just by memorizing facts and getting a "feel" for how recipes work. Many chefs study chemistry to better understand how various cooking/baking processes work. A few might even get into the physics underlying the chemical reactions just to satisfy curiosity. But you don't need to keep going into subatomic particles to have lost the feeling that cooking is based on mysterious unknowns.
For my personal interest, I've learned about compilers, machine code, microcode and CPU design, down to transistor-based logic. Most of this isn't directly applicable to modern programming, and my knowledge still ends at a certain point, but programming itself no longer feels like it's built on a mystery.
I don't recommend that every programmer go to this extreme, but we don't have to feel that our work is based on "magic smoke" if we really don't want to.
ADDED: If anyone's curious, I highly recommend Ben Eater's YouTube videos about "Building an 8-bit breadboard computer!" It's a playlist/course that covers pretty much everything starting from an overview of oscillators and logic gates, and ending with a simple but functional computer, including a CPU core built out of discrete components. He uses a lot of ICs, but he usually explains what circuits they contain, in isolation, before he adds them to the CPU. He does a great job of covering the important points, and tying them together well.
AI coding is an improvement on infinite monkey Shakespeare in the sense that it only types whole words from a dictionary. Although that dictionary has been built from a mix of classic literature and SNS posts.
So this is a list of responses given by AI when you correct it? My guess was "Things you will never hear from a client when you politely point out a logical inconsistency, an incorrect assumption, or a wild over/underestimation in their project plan." 'Cause in my experience the response you will get, 99% of the time, is "That won't happen."
Ha! I was a Mega Drive fan as a teen, and I got really angered by this... until I realized that you were speaking about the Mega CD and 32x specifically. Yep, there really weren't many good games for either of them.
I think the DC had the technical strength to go up against the PS2, not just early on, but for quite a while. The PS2 is incredibly flexible in theory, but looking at its library it seems like most developers just used Sony's default rendering setups. If you ignore the quickie PS1-to-DC ports and only compare titles which got equal effort from developers, it can be hard to tell the difference, and in some cases I'd even say the DC version looks a little nicer.
In this alternate universe where the DC didn't get killed off prematurely, what might've eventually turned the tide for the PS2 would be having between 1.5 and 2 times as much RAM (depending on how you account for different distribution), although that advantage may not have existed if it weren't for the large gap between their release dates.
But Sony could afford to delay for two years; consumers waited for them. Sega couldn't sustain launch-pitch marketing for that long, especially with an actual console on store shelves that people could experience firsthand, as opposed to teaser videos of what the console "might" be capable of. Few publishers or consumers wanted to invest in a console before the clear winner of the previous generation had entered the market.
All that being said, I don't know that the DC was really under-utilized, in technical terms. I feel like a good proportion of the games in its library are using almost all of the power it had under the hood. Perhaps Sega's management and engineers had learned their lesson from the Saturn, because the DC seems very straightforward from a programming perspective. It's almost ironic that it lost to the PS2, which took flexibility and parallelism to heart at least as much as the Saturn did, if not more.
Also, the battery life was hideously short. It would suck down a set of 6 AAs in less than 3 hours. I suspect that the CCFL backlight on the LCD screen was the culprit. And the console was huge. I have the official belt pouch and as a teen it reached most of the way down to my knee. The redesign was a bit smaller, but not much.
A lot of the games sucked, but there were some pretty good ones too. Just not enough games overall, I think.
How do you think your A.R.S.E. compares to Microsoft's planned Binary Universal Technology Translation System, and Sony's upcoming Original Software Heuristic Inter-platform Real-time Interpreter?
I like the big offering from MS, I cannot lie. Sony's outline looks well-rounded, too. I searched online, but I haven't seen any real details about your system. Even after I put down my phone and got on my desktop to type on a proper keyboard, I couldn't find A.R.S.E. with both hands.
ASM doesn't care about your variable types, because it doesn't care about your variables. What's a variable, anyway? There is only address space.
I had an OG nGage when they were still (as close as they would ever be to) relevant; I won it as a prize in a competition. And while I really liked it, I wouldn't have bought one with my own money unless the price had dropped by at least 50%, and even that's only given my personal positive experience with using one. As a regular consumer paying full price, it would certainly have been a hard pass for me.
The design seems to have been created by a group of mobile phone designers who once saw some pictures of a Gameboy Advance. I presume that the astounding decision to put the single game/SD card slot under the removable battery came from thinking that it would still be a phone first, and users would either install an SD card as a semi-permanent upgrade, or keep one game in the device until they finished it. I've only played one nGage game on mine (Tomb Raider), and the performance wasn't awful but it definitely left something to be desired. They were probably leaning hard on realtime 3D as a way to differentiate it from the GBA, but I don't think the CPU had quite enough power to make it responsive enough.
That being said, I used it happily for years as my main phone, and it generally outperformed all of my friends' phones by a wide margin. The only problem I ever had with "side talking" was having occasional random idiots on the street pointing and laughing. Now we all hold big, flat slices of bread up to our heads, but everyone does it so it's OK I guess. The phone call quality itself was crystal clear both ways. The speaker call mode was also miles ahead of any other mobile phone I saw at the time (or even any phone I've had since). I did get used to using it from my pocket with a microphone headset, though.
The nGage was a high-end Symbian Series 60 device with features much closer to modern smartphones than the more traditional, dedicated mobile phones that formed most of its competition. When it came out, BlackBerry was only just starting to expand beyond the enterprise space into the regular consumer market, and Apple's original iPhone (which don't forget was nowhere near as smooth and polished as they are now) was still 4 years away. Using the nGage with a headset actually worked out well since I often used it to listen to mp3s, a feature that many mobile phones still lacked at the time.
I could (and frequently did) surf regular, unfiltered, uncompressed websites on my nGage at a time when very few portable devices had that capability. And while I didn't play nGage games with it, it was fantastic for playing J2ME and Symbian games, many of which offered a GBA-like experience (albeit on a smaller screen) thanks to the relatively powerful CPU. That's not hyperbole; I was often also carrying a (frontlight modded) GBA around during that period, and switched my on-the-go gaming between them depending on my mood and what games I'd got recently. It also had surprisingly good battery life, although this may have been shortened when playing nGage games.
The nGage gets a lot of flak as a handheld gaming system going up against the GBA, and that definitely wasn't any kind of fight at all. But it was an extremely capable phone for the time, and even as "just" a phone, it still had useful gaming leanings. I think that there was a lot of knee-jerk reaction about "side talking" at the time, and despite there also being some legitimate complaints (like the card slot placement), I feel that it's doing a disservice to Nokia's engineers to have it go down in history as a total, unmitigated disaster.
Only Winsocks.
What's the word? I started looking but realized I have better things to do. Before I stopped I did find "nips" and "chow", both of which have completely unrelated, normal meanings. Hell, I didn't even know "chow" could mean anything other than food until I read the definition in the dictionary file.
There are several other racist, sexist, and generally rude words in there too. There is even a slur which has been used against me, and it's defined as such (one meaning among many), but I say leave them. Well, maybe "cunt" could go without being missed.
I don't think that even C++ is that bad. Like a lot of shows and music acts, I think it's more the toxic fan base than the thing itself that really sucks. I've had the same feeling with a certain kind of JavaScript programmer.
*Edit for clarity: I'm not saying that the entire C++ community is toxic, just a vocal segment of it, in line with the other examples I gave.
The added difficulty with this in programming is that it can be much harder simply to ignore them, because you may be forced to work with them, or stuck needing to learn something from them (shudder).
I wouldn't be surprised if book readers spend 92% of their time on older books. Or if music listeners spend 92% of their time on older pieces.