• 96 Posts
  • 4.51K Comments
Joined 5 years ago
cake
Cake day: May 31st, 2020

help-circle
  • OpenOffice has seen essentially no development since 2011, when the trademark got transferred to Oracle after they bought Sun Microsystems.

    The project got forked into LibreOffice to dodge the trademark issue, but it’s the same devs, practically the same project, but now under a non-profit organization. Well, and with 14 more years of development.

    So, use LibreOffice instead of OpenOffice. It will most likely come pre-installed on whichever Linux distro you go with. But you can also try it out on Windows beforehand, if you have concerns.





  • Ephera@lemmy.mltolinuxmemes@lemmy.worldDesktop PTSD
    link
    fedilink
    English
    arrow-up
    3
    ·
    9 hours ago

    On KDE, I’d recommend getting a KWin Script for tiling. Krohnkite is what people use currently.

    It’s not as buttery smooth as dedicated tiling window managers and it can be a bit glitchy at times, but it is better than one might expect and significantly easier (and likely less glitchy) than trying to get bspwm to work in Plasma.



  • For what it’s worth, being a professional software engineer, I expected that list to be at least a magnitude longer. I guess, it doesn’t include all their internal projects. But yeah, you would not believe how much shit we throw at the wall and how little of it sticks, particularly not for more than a few years.

    I once heard the figure that IT investors expect 1 out of 20 investments to pay out, which feels about right to me…




  • Yeah, after writing that comment, I was thinking, if I do promote it, that means there’s a certain expectation that I’ll integrate or implement functionality that others want. At that point, it becomes less of an egoistic thing. And I’ll be doing more communication and whatnot, therefore less programming.

    Maybe that’s the puzzle piece that OP is missing? If you don’t promote it, you have practically no extra work compared to developing it under a proprietary license. In fact, it often reduces the workload, if you can just post it publicly without having to secure the repo.
    And you don’t incur costs from giving it away either. So, if you make sure to only put in the work that you want to put in in the first place, you have no disadvantage from publishing it with an open-source license.





  • I mean, it sounds like it’s gonna be a fairly large codebase. Rust is definitely better equipped for large codebases than Python…

    I do agree that Python could give them more outside contributors, but from my experience, I don’t think it’s worth swaying from your preferred tooling for that. Outside contributions will make up barely a fraction of code changes either way, so you should rather ensure that your core team is productive.