• 4 Posts
  • 27 Comments
Joined 5 months ago
cake
Cake day: July 26th, 2024

help-circle





  • This is a double-whammy PR nightmare.

    Are we going to do what happened with Jack in the Box in the naughts and start associating E Coli with McDonalds? I remember hearing that FUD so much back then and now that the shoe is on the other foot, I wonder what will happen. 🤔 Not to engage in the fast food wars or anything, but also fuck McDonalds for helping this fat ass at all.


  • I’m still very curious what consumer segment ends up picking this up. It’s $250, and I would assume you can just get an actually N64 for like $30, no?

    Sure, but you’re not factoring in all of the price factors that come associated with playing that on a new TV or complicated AV system. This comes with HDMI output built in, and will have scalers and other amenities for QoL usage in 2024. The sad truth is that it’s actually pretty expensive to have an AV setup that is designed to handle old consoles, especially with how TVs have not properly supported lower-res content for a long time.

    Fact of the matter is some of the best scalers with low latency that you can buy are nearly $2k US, and even the cheaper or more budget options are more expensive than the $250 price tag that this targets (the OSSC, for example). I wish this wasn’t the case, but the Analogue 3D and equivalent reimplementations are actually super important for people who are still interested on playing the closest to “real hardware” in 2024.













  • I do agree that developers should use their own software, but doing so on a smaller instance with strict active user limits is probably the right call – at least until you are certain the software has a “stable” version, but even then you probably will want to run a master branch instance that is much less stable and prone to errors. Until you can afford it, it’s probably not a good idea for developers to be spending a huge amount of time debugging in-progress features (which IIRC, firefish had a lot of those.)





  • I was on firefish’s previous instance, known as calckey, before I migrated back to Mastodon.

    There were definitely warning signs that the project was facing maintenance issues in those days as well, and it felt that the Firefish rebrand was an attempt to “start a new”.

    But just like my post on KBin’s demise, it should be a warning to those who want to make the software and host a “big” instance: Don’t do it. I think it’s smart to host your own mini instance for testing, but you should probably solely focus on the code development side of things to make sure that you aren’t over burdening yourself with managerial tasks. If your software is good, people will make spins inevitably. If people use it, then you will probably have enough people contributing that you can scale up your mini-instance if needed. But don’t jump in without the finances in place, because you’re essentially taking on two jobs.