If you or anyone else is interested in playing more, I recommend:

• Silent Hill 2: Restless Dreams (aka Director's Cut). Not a continuation of the story of the first game, but a separate story in the same universe. Generally agreed to take everything good from the first game and improve upon it. The "Restless Dreams" version has a substantial extra scenario which adds some backstory and lore, but should probably be played only after completing the main game.
• Silent Hill 3. This one does continue the story of the first game, somewhat. To be honest I remember enjoying it but not much in terms of particulars.
• Silent Hill 4: The Room. Started out as a separate game unrelated to the Silent Hill mythos, but was rewritten to become an SH game during development. This sounds like it might be a terrible cash-in, but it really is a perfect fit for the SH universe. IMO almost as strong as SH2.
• Silent Hill: 0rigins. A PSP game set as a prequel to the first game. A little light on story, and with some odd combat mechanics, but I still found it very enjoyable. I played the later PS2 port.
• Silent Hill: Shattered Memories. A "reimagining" of the story from the first game. It plays and feels very different to the previous games, but I still enjoyed it quite a lot.
• Silent Hill: Orphan. A series of point-and-click adventures for Java-enabled mobile phones from the 2000s. Totally different mechanics from the mainline games, but they do the atmosphere and story well if you don't mind the slower pace of point-and-click. They run on some J2ME emulators.
• Silent Hill: Alchemilla. A free fan-game centered on the Alchemilla Hospital, but also including several other locations. First-person view with many puzzles and no combat. Very polished and really nails the atmosphere.

I played a little of Silent Hill: Homecoming but got tired of it about 1/3 of the way through (I guess). I also bought Silent Hill: Downpour but gave up on that even more quickly. I don't recommend either of them. Things introduced in the earlier games for specific psychological reasons related to the plot - especially sexy monster nurses and Pyramid Head - tend to be regurgitated in the later games for no real reason other than "Silent Hill", which removes their impact completely.

There's nothing wrong with wanting to stick to original hardware, if you already have it or can afford to buy it.

Setting up a Pi or other single-board system as a dedicated retro game emulator is also an absolutely valid choice IMO. It's a fun, generally affordable little project that you can tinker with forever, e.g. changing cases and controllers, UI tweaks, ROM file organization, per-game settings optimization. But I don't think that it's ever been the "best" emulation option for anyone who didn't already have their heart set on "doing something fun and interesting with a Pi".

The smartphone you already have, dedicated retro gaming handhelds, Android TV boxes or sticks, and cheap/secondhand/already-owned PCs (desktop, notebook, or kiosk) all arguably match or exceed the performance and value-for-money of any Pi-based system.

Yet in any thread where someone new to emulation is asking for advice, there's always a flock of folks who suggest getting a Pi like it's the only game in town. It honestly baffles me a little. Especially because almost all of them are just running a pretty frontend over Retroarch, and Retroarch is available for virtually every modern consumer computing platform (and so are a lot of pretty frontends, if that's a selling point).

For context, I've got a dozen or so retro systems, but I prefer to emulate as much as possible.

Yeah, I'm sure that almost all of us have felt this way at one time or another. But the thing is, every team behind every moronic, bone-headed interface "update" that you've ever hated also sees themselves in the programmer's position in this meme.

Let me know if you find one that uses AI to find groupings of my search terms in its catalogues instead of using AI to reduce my search to the nearest common searches made by others, over some arbitrary popularity threshold.

Theoretical search: "slip banana peel 1980s comedy movie"
Expected results in 2010: Pages about people slipping on banana peels, mostly in comedy movies, mostly from the 80s.
Expected results in 2024: More than I ever wanted to know about buying bananas online, the health impacts of eating too many or not enough bananas, and whatever "celebrities" have recently said something about them. Nothing about movies from the 80s.

Unfortunately we all know what happens when you tell hackers that something's going to be very hard to break into.

I understand that they were excited about the idea and wanted to share it with gamers, but if they actually wanted to give the system the best chance of success, they should've kept their mouth shut.

Thr34dN3cr0 wrote (14:12 5/17/2019):

Does anyone have a way to fix this in the latest version? I've been looking all day but none of the answers I've found work.

Thr34dN3cr0 wrote (14:48 5/17/2019):

nvm figured it out.

"If you wish to be a writer, write."

Epictetus delivered this burn over 1900 years ago.

Re: the Acceptance stage.

Years ago I worked at a family-run business with a good working environment. The staff were once told a story of how, earlier in the company's history, a manager made a mistake that caused the company a substantial monetary loss.

The manager immediately offered their resignation, but the owner said to them, "Why would I let you go now? I've just spent all this money so you could learn a valuable lesson!"

So yeah, generally, most managers' reaction to accidentally deleting vital data from production is going to be to fire the developer as a knee-jerk "retaliation", but if you think about it, the best response is to keep that developer; your data isn't coming back either way, but this developer has just learned to be a lot more careful in the future. Why would you send them to a potential competitor?

It's a persistent dynamic memory allocation that's accessed by multiple processes! :)

This is a short, interesting video, but there's really nothing here for any competent programmer, even a fresh graduate. It turns out they they update the software by sending the update by radio (/s). The video hardly goes any deeper than that, and also makes a couple of very minor layman-level flubs.

There is a preservation effort for the old NASA computing hardware from the missions in the 50s and 60s, and you can find videos about it on YouTube. They go into much more detail without requiring much prior knowledge about specific technologies from the period. Here's one I watched recently about the ROM and RAM used in some Apollo missions: https://youtu.be/hckwxq8rnr0?si=EKiLO-ZpQnJa-TQn

One thing that struck me about the video was how the writers expressed surprise that it was still working and also so adaptable. And my thought was, "Well, yeah, it was designed by people who knew what they were doing, with a good budget, lead by managers whose goal was to make excellent equipment, rather than maximize short-term profits."

I once had a manager hand me a project brief and ask me how quickly I thought I could complete it. I was managing my own workload (it was a bad situation), but it was a very small project and I felt that I had time to put everything else on hold and focus on it. So, I said that I might be able to get it done in four days, but I wouldn't commit to less than a week just to be sure.

The manger started off on this half-threatening, half-disappointed rant about how the project had a deadline set in stone (in four days' time), and how the head of the company had committed to it in public (which in hindsight was absolute rot). I was young and nervous, but fortunately for me every project brief had a timeline of who had seen it, and more importantly, when they had received it. I noticed that this brief had originated over three months prior, and had been sitting on this manager's desk for almost a month. I was the first developer in the chain. That gave me the guts to say that my estimate was firm, and that if anyone actually came down the ladder looking for heads to set rolling (one of the manager's threats), they could come to me and I would explain.

In the end nothing ever came of it because I managed to get the job done in three days. They tried to put the screws to me over that small of a project.

Yes, refuse to federate from the get-go. By the time the hostilities become open, it'll be far too late not only to attempt to repair any existing damage, but even to avoid further damage coming down the line like a juggernaut.

Plenty of large corporations have shown time and again that SOP is to take over and kill any potential threats before they can develop. When a corporation finds another corporation using their resources for gain, even while still following terms and conditions, the lawyers come out and the fur flies. Why should we be pushovers just because we're not rich and don't have a legal fiction to hide behind?

The Fediverse is a direct competitor to monolithic social networks. That's definitely how they see us, and it's how we should see them. I know that there's a "share and share alike" ethos behind all of this, and that blocking any entity arbitrarily feels wrong and unfair, but it really isn't. I also know that, assuming that things go well, one day there will be successful business ventures that evolve naturally from the Fediverse, and the community is going to have to decide how to respond to those situations in time. But right now we're a group of little pigs playing in a somewhat secure pen, and a huge, voracious wolf is asking us to open the gate so it can join in our game. By the time we realize that we haven't seen Jerry or Louise for a while, the wolf will have changed the lock on the gate and spread rumors about us to the other animals.

If people still feel uncomfortable with refusing a large corporation "just because", then make a policy: "Due to the dangers inherent in unequal business relationships, it is our general policy to refuse federation with any entity with an average annual turnover in excess of US$200,000." You can always make exceptions, and even change the policy later, but it can ease your conscience that you aren't unfairly targeting one entity without justification; you're sticking to a sensible policy.