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

help-circle
  • 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.







  • Without a doubt, Patents and Software are a bad mix.

    But there’s definitely a truth to the idea that Palworld in particular were aiming for a legal battle against Nintendo from the beginning with provocative action. There’s a reason why Nintendo has rarely gone after Pokemon-likes but have decided that this particular company is worth pursuing.

    This is kind of a lose-lose situation. Palworld was clearly kit-bashing existing Pokemon models and were engaging in creative bankruptcy, but software/game patents serve only to hurt creatives and developers around the world and Japan in particular is poor around SLAP suits.

    So, I agree, grab the popcorn. But I hope that whatever patents they’re choosing to enforce here don’t have a major ripple in game development as a whole. There’s a world with the brazen IP theft of palworld actually does us all a disservice by making it an easier case for Nintendo to enforce Patents that would otherwise be unenforceable or difficult purely out of optics.







  • 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.


  • MoogleMaestro@lemmy.ziptoLinux@lemmy.mlIs Linux (dumb)user friendly yet?
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    3
    ·
    2 months ago

    I mean, yes. But also no, it sort of depends.

    If you have very low bar of needs (needing a web browser and some utility apps, without specific apps in mind) then it’s actually never been easier. If you use a Silverblue based system, all updates are done in a transactional way and old versions can be booted into at any time in case something breaks (which basically never happens with silverblue, with some exceptions.) Read only systems means you can’t muck around with the root files and can’t accidentally “break” your system in the way you used to be able to on older OS designs. I would say that “Linux with Guardrails” is effectively invincible, and I would like to recommend that new users try OSTree based systems. For example, Fedora Silverblue, Ublue’s Aurora / Bluefin, Bazzite (Steam OS clone), etc etc.

    If you have more specific needs, it can be a crapshoot depending on whether or not the hobby in question has a strong linux presence. Particularly, bespoke non-game windows apps are still a bit tricky to get working and require some Wine (Windows process wrapper for compatibility) knowledge. There are edge cases where running certain applications in flatpak (Steam, Bitwig) can mean that, while it’s impossible for these applications to break your system, you’ll be very limited in options for these programs. For Steam, this can mean more difficulty with out-of-steam application management. For Bitwig, this can mean no choice in VST. These are all programs that have work arounds, but on a read-only system like Silverblue (which I would like to recommend for new users due to the indestructibility) those are all a little more difficult to implement and require you to know a thing or two about virtual desktops. (Thus, not new user friendly.)

    I would still say that it’s never been easier, but as you get more famililar with any system, you generally demand more and more from it. Thankfully, with linux, its always been a case of “if there’s a will there’s a way” and the UX utility applications being made by other people have been getting better and better.

    My recommendation to you would be to try UBlue Aurora. It’s familiar to Windows, it’s being managed in a way that makes gaming relatively simple, and it has an active discord community to help new users. It also has that indestructability that I was talking about before, but has a lot of the “work arounds” pre-setup for new users.