903 karma · joined November 25, 2010
I want to keep it all open though so you still 'own' your website, with the option to host at academic.bio (simple s3 static site), download the compiled html/CSS to host yourself, or use the Jekyll theme directly (github.com/academicbio/academic-minima) depending on the level you're comfortable at.
Thoughts and feedback welcome!
PS the next step is allowing quick import of publications. Where would people like to import from? Bibtex? ResearchGate?
If anyone else wants to feel at the cutting edge of science, you can write your LaTeX paper collaboratively at https://www.sharelatex.com :P
I can't pretend we've got any original algorithms (we lean on ShareJS a lot, which is operational transform based), but we've got a few years and billions of key strokes of experience in making it robust and practical.
The exception to that is in teaching. It did fill a big need there, but we never managed to make the business model work (long high touch sales cycles, but universities only willing to pay very low prices per class). We also never found a growth model for this.
(Also, HN is not really a good target audience for us, so if you get news from here, it makes sense you'd see this but not the product itself).
The main thing that isn't open source with DataJoy is our backend for running code. At the moment this is so tied into Docker, S3, and how we deploy it in our infrastructure, that I don't think it would be much use to anyone else. The innovations here have been in how we deploy and provision it, not in the code itself.
Our working hypothesis is that people fall into one of two categories (possibly both, but only one at a time):
a) Those who just want a simple to use LaTeX environment that just works for their task at hand.
b) Those who are more interested in the tech, and happy to install software locally, happy to explore things like git for collaboration and really refine their own personal workflows with the tools they like.
The paid plans are used by people in category (a) and would never be of much interest to those in category (b). But the self-hosted option is great for some people in category (b).
We also have a paid version of self-hosted ShareLaTeX, with direct support from us, and enterprise features like LDAP, admin controls for managing thousands of users, etc. The open-source version forms a natural part of this, (see GitLab, etc)
As for the installation, I know, this bit kind of sucks, sorry :( How long ago did you last install/upgrade? My co-founder is working pretty much full time on improving the ease of installation and configuration. One of the difficulties is that we use a lot of small services, which is great for large scale deployment, but a bit of a nightmare for producing a single standalone installable service with a unified config system. We're getting there though, and it's a priority at the moment. If you've got any feedback or problems you hit, please reach out at team@sharelatex.com. Thanks!
With it being a new rule, there was very little info about the penalties for not complying. The penalties for normal UK VAT are only proportional to revenue, so not much risk for small companies getting it wrong. It wasn't clear that this was true for VATMOSS and so there was fear amongst even tiny company of big penalties for getting it wrong.
We went through the same worries last Nov/Dev, but were lucky that our billing provider dealt with adding in all the required logic. (Shout out to Recurly!)
One of the big wins for us has been using Docker to isolate projects. Sure, each project is resource heavy when run/compiled/executed, but if you have lots of users, they're probably not all resource heavy at the same time. The more lightweight the virtualisation/containers, the more they can share resources. It sounds like maybe each user is getting to hold on to too many resources that they aren't using, and so it's costing an order of magnitude more than if they could share all the resources perfectly?
I'd be happy to chat more about this stuff (almost all of the ShareLaTeX code is open source as well, except for the enterprisy stuff). We've also got a new project called DataJoy for Python and R (https://www.getdatajoy.com) which has similar scaling challenges that we've been working on.
- DataJoy co-founder
The 'reproducible' part that we mentioned was meant to refer to the fact that it's easily reproducible on DataJoy. I.e. if you share you work with a collaborator, you're not going to have any headaches around getting the scripts working on their system, installing the right packages again, etc.
Edit: Nevermind, I found it (https://github.com/docker/docker/blob/master/experimental/pl...)! Three clicks in, through various blog articles with lots of other links. Maybe consider making this more obvious?
Help us empower scientists by building usable open-source research tools.
We're looking for a remote full-time developer to join our team at ShareLaTeX (https://www.sharelatex.com) and DataJoy (https://www.getdatajoy.com). ShareLaTeX is an online LaTeX editor with over 400,000 registered users, and DataJoy is our new app for online data analysis with Python and R. We're aiming to make these technologies more accessible and easy to use for academics doing data analysis, numerical modelling and statistical analysis.
You should be comfortable quickly learning new technologies and enthusiastic about improving the efficiency of scientists and their tools. Our current technology stack involves Node.js, MongoDB, Redis, Coffeescript, Angular.js, and Docker, so experience in these is useful but not required. We’d rather see that you have demonstrable interest in the problems we are solving, and that you’ve created some great stuff in the past. We would love someone with front-end experience and a good sense of usability design, but we won't discount people with more of a backend focus.
Some reasons you'd enjoy working for us:
* Around 80% of our codebase is open-source and we’re big fans of free software.
* We’re agile (with a lower case a). We test everything (unit and acceptance), we have a CI build process, a full staging environment to play with, and we automate as much as possible.
* We don’t expect you to have to fill up a 9-5, 40 hour work week. A work/life balance is important and we don’t think programming is an activity that can be neatly time boxed.
* You can work fully remotely (in fact, you probably will). All founders and employees work remotely at the moment.
* We’re a bootstrapped company with no outside investors.
Send us an email: team@sharelatex.com
sin(time * 0.2) * cos(time * 0.1) * (125+125*sin(0.01*(2 + sin(0.6*time)*cos(0.4*time))*((- 50 + x + 20 * cos(0.5*time))^2 + (- 50 + y + 20 * sin(0.3*time))^2)))