• 7 Posts
  • 25 Comments
Joined 1 year ago
cake
Cake day: July 26th, 2024

help-circle









  • The best path forward is that developers make their linux drivers before they release their hardware to the market. You know, like what they do for windows.

    There’s no silver bullet here. You have to wait for someone to reverse engineer the drivers if the developers of the hardware don’t care enough to supply even basic linux driver support. Either that or linux becomes so popular that it becomes senseless to ignore it (let’s be real though, MacOS is popular enough for this to be true and yet there’s still new hardware made that ignores that platform too.)








  • MoogleMaestro@lemmy.ziptoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    49
    arrow-down
    6
    ·
    8 months ago

    It’s very strange that you’ve made a post about bugs but chose not to list any of the bugs.

    Like, how can we make a recommendation if we don’t know what types of issues you’re running into? What type of hardware you have? What expectations you have?

    It just kind of screams of disgruntled user syndrome. These are community lead projects so, yes, they’ll have bugs. But if people never say what they are or what issues they had with what they used, the best the rest of us can do is just guess!







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