DataJoy is shutting down
getdatajoy.com
DataJoy is shutting down
1–10 of 47 posts
Re: DataJoy is shutting down
#2Why don't companies feel comfortably "code dumping"? Just throw everything online as a tarball, and say "we aren't supporting this and we don't want to have anything to do wit h this, but here's the source."
Re: DataJoy is shutting down
#3Why don't companies feel comfortably "code dumping"? Just throw everything online as a tarball, and say "we aren't supporting this and we don't want to have anything to do wit h this, but here's the source."
I would be interested in hearing the opinions of people who've been in this situation, too. Seems like it could be beneficial to the community.
Re: DataJoy is shutting down
#4Why don't companies feel comfortably "code dumping"? Just throw everything online as a tarball, and say "we aren't supporting this and we don't want to have anything to do wit h this, but here's the source."
Often they don't own the copyright for everything they own. Also, wouldn't code be an asset to be sold in the event of liquidation?
Re: DataJoy is shutting down
#5Why don't companies feel comfortably "code dumping"? Just throw everything online as a tarball, and say "we aren't supporting this and we don't want to have anything to do wit h this, but here's the source."
I would be interested in hearing the opinions of people who've been in this situation, too. Seems like it could be beneficial to the community.
If my current company went under, I don't see who would put in the effort to sift through all 3rd party items we use for licenses to see if we're even allowed to do it.
Someone also owns the code, I guess, and they might want to use it for something else at some point.
Some products might have been hack-jobs form the beginning that ballooned, they might work but they could be total hack jobs that would either A) be worthless on their own or B) slightly embarrassing to show.
I've not been in the situation from a company perspective, but I have taken a product I've made off from the shelves and the factors above came into play. I am sure there are more as well.
Re: DataJoy is shutting down
#6Why don't companies feel comfortably "code dumping"? Just throw everything online as a tarball, and say "we aren't supporting this and we don't want to have anything to do wit h this, but here's the source."
Even if they wanted to open source or just share the source, there could be some real effort involved in reviewing the code to ensure that nothing sensitive will be exposed.
Re the other comment about owning copyright on everything (eg. Due to components being licensed from other vendors), they could rip that out. Thinking about this triggered a memory of when Descent 1 source was published, they excluded the sound library for this reason. Could be tough to excise something more integral though I guess.
Re: DataJoy is shutting down
#7Why don't companies feel comfortably "code dumping"? Just throw everything online as a tarball, and say "we aren't supporting this and we don't want to have anything to do wit h this, but here's the source."
I know this isn't a general rule, but based on my experiences with proprietary projects, even with the best of intentions most became a jenga-esque pile of hacks and shortcuts that few developers would want to show off in public even if the overall system works well.
Re: DataJoy is shutting down
#8Why don't companies feel comfortably "code dumping"? Just throw everything online as a tarball, and say "we aren't supporting this and we don't want to have anything to do wit h this, but here's the source."
DataJoy Co-founder here. A lot of the DataJoy code IS available (https://github.com/sharelatex/web-sharelatex/tree/datajoy). Our other product ShareLaTeX has an open-source version that you can run locally and is very similar to the version we host at sharelatex.com. DataJoy naturally shares a lot of code with ShareLaTeX (if you look at the two products, you'll see they're very similar). However, with DataJoy, we never got the product to a stage where we felt it made sense to invest time into 'good open source' (documentation, installation guides, etc), but the 'code dump open source' version has always been there.
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.
Re: DataJoy is shutting down
#9[deleted]
Re: DataJoy is shutting down
#10They have a wonderful example library https://www.getdatajoy.com/examples/ that would be too bad to lose if they eventually shut down their site.