729 karma · joined January 22, 2014
Additionally we invested a lot in a unparalleled test-suite in this space which runs against the old and new codebase.
How could we innovate further?
There are multiple open-source file sync and share platforms. The reason is quite simple: There are multiple ways to implement a digitally sovereign file platform, and different needs call for different feature sets. ownCloud focuses on code quality, reliability and features that security conscious companies and institutions have come to expect. You do not have to like ownCloud, you do you. To your open standards point: I posted here because we use go-micro in our current rewrite, which is by the way under the Apache 2.0 licence. We cherish and embrace open standards and open source, so I don’t exactly get what you mean by “more open standards”. But to answer your first question: we did not die because we were and are in good health, still had and have work to do and, most importantly, have oodles of happy users and customers to serve.
Disclaimer: I work for ownCloud.
As a backend dev you get your data from web-services which are written by the web-services team (or another company) which in turn receives optimized database queries/procedures from the database team. You pass the data after processing to the template/fronted which is is the domain of the fronted-guys.
Deployment is done by the ops team to servers which are administered by the infrastructure department in the data center.
My first job as junior-developer was in such organization and it is quite enjoyable to have experts for every domain to learn from instead a lot of "Jack of all trades, master of none" people. The other benefit is that you can put all your effort in to mastering your particular domain.
The drawback is obviously that you are isolated in your tier and don`t learn as much as if you would do a project "full stack".
In my experience you acquire those by working with the language every day for a year or so... and then you are still far away from "master".
Code does not have to be written in a certain way most of the time because hhvm is 98% compatible to all major PHP-Frameworks[1]. It also features a built-in webserver alltough static performance is lower than nginx.
[1] http://www.hhvm.com/blog/2813/we-are-the-98-5-and-the-16