As Nextcloud advanced with progresses making it competitive in fully integrated government and corporate workflows, OpenCloud is getting more and more attention.

The fact, that both are collaborative cloud plattforms, designed to be selfhosted and mainly developed in/around Berlin from FOSS-Community-Surroundings, makes one ask about the differences.

The main difference I see, is the software stack

  • Nextcloud, as a fork of ownCloud, kept the PHP code base and is still mainly developing in PHP
  • OpenCloud, also a fork of ownCloud, did a complete rewrite in Go

Until know, Nextcloud is far more feature complete (yes I know, people complain, they should fix more bugs instead of bringing new features) than OpenCloud, if we compair it with comercial cometitors like MS Teams.

I like Nextcloud!

I deploy it for various groups, teams, associations, when ever they need something where they want to have fileshare, calendar, contacts and tasks in one place. Almost every time, when I show them the functionality of Nextcloud Groups an the sharing-possibilities, people are thrilled about it, because they didn’t expect such a feature rich tool. Although I sometimes wish it would be more performant and easier to maintain, so non-tech-people could care for their hosting themselves.

Why OpenCloud?

Now, with OpenCloud, I am asking my self, why not just contribute to the existing colab-cloud project Nextcloud. Why do your own thing?

Questions

So here I expect the Go as a somewhat game-changer (?). As you may have noticed, that I am not a developer or programmer, so maybe there are obvious advantages of that.

  • Will OpenCloud, at some point, outreach Nextclouds feature completeness and performance, thanks to a more modern approach with Go?
  • Will Nextcloud with their huge php stack run into problems in the future, because they cant compete with more modern architectures?
  • If you would have to deploy a selfhosted cloud environment for a ~500 people organization lasting long term: Would you stick to the goo old working php stack or see possible advantages in the future of the OpenCloud approach?

Thanks :)

    • boonhet@lemm.eeEnglish
      2·
      21 hours ago

      Supposedly the team left OwnCloud and forked it. So the value is that the OCIS team will be working on OpenCloud in the future.

      • sugar_in_your_tea@sh.itjust.worksEnglish
        1·
        19 hours ago

        Wow. Here’s an article that discusses it:

        After the takeover, the management style changed, former ownCloud employees told heise online in confidence. And there was a lack of concrete commitments from Kiteworks regarding the long-term development of oCIS. They had worked on oCIS out of conviction, believed in its future as an open source product and also valued the joint team. For this reason, the decision was made to gradually make a new start with OpenCloud, according to several employees.

        …

        This is now the second time that the ownCloud code has been forked: In spring 2016, co-founder Frank Karlitschek left the company together with a dozen developers and founded Nextcloud. There, they further developed the PHP code and incorporated many additional functions.