• 0 Posts
  • 31 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
  • I really appreciate your response. It’s incredibly helpful and deeply thoughtful. Thank you.

    What comes next is not directed at you but rather provides some other color based on a few things you touched on.

    I worked for the guy. He gets no slack from me. He changed my life in many ways both wonderful and not. And while it’s unlikely I’d work with or for him again he was a net positive in my life.

    I don’t see product the way he sees product which is exactly as you note: it’s for him. Some of that “for him” approach has resonated deeply with the OSS community and still does. He changed Cloud Computing in the best of ways. He’s a giant. And we’re lucky he’s around.

    This small ghostty issue (and some others I can’t recall now) was emblematic of our core disagreement about how we build systems for a broader user base. That’s why I said I get their PoV but disagree with it. I think it would be fair to say using the product reminded me a lot about this particular tension. Reading the GitHub issues even more so. That’s wholly on me.

    I am thankful to ghostty for helping me explore many more options. I had been using iterm2 on my laptop and struggling to find something I liked on my Linux workstation. Checking out the new hotness after all the hype still resulted in a net positive.

    Nevertheless I am genuinely happy it’s working for you and, again, thanks for your kind and calm response.







  • As per my other comment - the algorithm is only part of it.

    A big aspect however is the slickness and ease-of-onboarding for mega-Corp apps. It’s a thing that would relatively easy to begin work on.

    I’ve seen first hand the amount of time and money even growth-stage startups spend on onboarding and have lots of first-hand reports from peers at the big girls - it’s a critical part of success. Make it easy to get started and easy to stay using.

    It’s missing from most fediverse experiences. Pixelfed being a serious contender for an on-boarding rethink.

    “time-to-value” - we want that as low as possible.






  • Never used your project but don’t let this thread get you down.

    Clearly OP loves it - don’t let those who don’t know it or don’t like it be the voices that ring loudest in your ears even if they hurt the most.

    I worked professionally in open source at a company with lots of funding. The tools I worked on were used by millions and millions.

    Every negative comment hurt so much. Every angry user I wanted to talk to. Most of them wanted to TALK AT me. It all hurt. And I was being paid. The engineers on my teams were burnt by the community time and time again.

    If you love what you’re doing and you have a growing or happy audience - stay the course. Listen to criticism, decide if you agree (and maybe take some time when it hurts because the criticism might be valid), make a decision and move on.

    Also, and this is going to be tough, maybe think about expanding or modifying what you mean when you say making Lemmy accessible for everyone.

    Do you mean making a UI that will become the majority default or making a UI that brings some features (or perspective) for users who see value in those features? Trying to make something for everyone in a pond as small as the fediverse, where there are already a plethora of options is a big lift.

    Above all, do you. And that includes this comment which I encourage you to promptly ignore. ;)


  • Garuda.

    I’d never used Arch or Arch derivatives but if this is the experience I understand the memes a little more.

    The package management is easy and very up to date. I like the BTRFS snapshots, and it had everything game-related available right out of the box. My Nvidia graphics card, which was the thing I couldn’t get working on Ubuntu, performed as well or better than under windows.

    The only thing that didn’t work for me was ZFS - but because everything else was working well, I just went another route.


  • Longtime every OS user. But have been using Linux since the days of Mandrake in ‘96. Switched to Debian shortly thereafter though mostly as a server/SDN device. Then a long spell on Ubuntu starting with 8.something. While I don’t use Linux on the desktop as my primary work OS, I do use it daily.

    Recently, annoyed with windows, which I only used/booted up for gaming, I gave gaming on Linux a try. It’s been mostly flawless even when the games aren’t Linux-native. Hilariously Ubuntu was awful and I couldn’t get it working so I’ve switched to something more gaming specific and couldn’t happier.






  • Good enough? I mean it’s allowed. But it’s only good enough if a licensee decides your their goal is to make using the code they changed or added as hard as possible.

    Usually, the code was obtained through a VCS like GitHub or Gitlab and could easily be re-contributed with comments and documentation in an easy-to-process manner (like a merge or pull request). I’d argue not completing the loop the same way the code was obtained is hostile. A code equivalent of taking the time (or not) to put their shopping carts in the designated spots.

    Imagine the owner (original source code) making the source code available only via zip file, with no code comments or READMEs or developer documentation. When the tables are turned - very few would actually use the product or software.

    It’s a spirit vs. letter of the law thing. Unfortunately we don’t exist in a social construct that rewards good faith actors over bad ones at the moment.


  • As someone who worked at a business that transitioned to AGPL from a more permissive license, this is exactly right. Our software was almost always used in a SaaS setting, and so GPL provided little to no protection.

    To take it further, even under the AGPL, businesses can simply zip up their code and send it to the AGPL’ed software owner, so companies are free to be as hostile as possible (and some are) while staying within the legal framework of the license.