Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DataJoy is shutting down

getdatajoy.com

Post reply on HN
Print view View original

11–20 of 47 posts

Re: DataJoy is shutting down

#11

Post by timthelion »

wingerlang wrote: post #5
mroll wrote: post #3

Earlier quoted context omitted.

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 w…

Was this 3rd party code that you bought or stuff you found on github? In the latter case, basically, you're saying that you didn't know and didn't care about compliance because no one could have found out?

Re: DataJoy is shutting down

#12

Post by mootothemax »

timthelion wrote: post #11
wingerlang wrote: post #5

Earlier quoted context omitted.

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 w…

Was this 3rd party code that you bought or stuff you found on github? In the latter case, basically, you're saying that you didn't know and didn't care about compliance because no one could have found out?

>Was this 3rd party code that you bought or stuff you found on github? In the latter case, basically, you're saying that you didn't know and didn't care about compliance because no one could have found out?

That's a rather uncharitable interpretation.

I think it's more likely that they don't know if they're licensed to publish the code in question.

Re: DataJoy is shutting down

#13

Post by cderwin »

timthelion wrote: post #2

Why 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."

As a part of a startup that just went under (by "just", I mean literally yesterday) they either can't release the code due to fiduciary responsibility to investors (it could be worth something, particularly if someone decides to dump more money in or the company somehow miraculously recovers) or because of contracts into which they have already entered with investors.

Re: DataJoy is shutting down

#15

Post by wingerlang »

timthelion wrote: post #11
wingerlang wrote: post #5

Earlier quoted context omitted.

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 w…

Was this 3rd party code that you bought or stuff you found on github? In the latter case, basically, you're saying that you didn't know and didn't care about compliance because no one could have found out?

- Libraries included even before my arrival.

- Libraries licensed for usage but not for open sourcing unless X, Y and Z.

Etc.

Re: DataJoy is shutting down

#16

Post by _pmf_ »

timthelion wrote: post #2

Why 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."

> Why 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."

  - It may contain configuration information.
  - It may contain private keys or passwords.
  - It may contain customer specific code (if you maintain customer specific features either via feature toggles or branches), which may leak information of your paying customers.
  - It may have unintended copyright violations.
  - It may contain software that is licensed in a way that makes it a copyright violation to distribute your software outside or your company (publishing it is distributing it). This may also apply if you distribute your sources without any (source or binary) parts of the proprietary dependency.
  - It may fall under the export restrictions for cryptographic software (these have been mainly dropped, but not completely).
  - It may directly or indirectly make your patent violations public (oh, you have them already, but nobody knows about them).
  - It's of embarrassing quality.
  - It may make it public that your company has defrauded its customers / and or users.
  - It may make it public that your company has supported its customers to commit fraud and/or other crimes (the RICO act makes this more easier to follow up on for law enforcement).
I have never worked on any non-trivial project where not almost all issues were present.

Re: DataJoy is shutting down

#18

Post by mooreds »

petercooper wrote: post #7
timthelion wrote: post #2

Why 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.

> most became a jenga-esque pile of hacks and shortcuts that few developers would want to show off in public

Not just that they don't want to "show off", but even more that they don't think it will be useful.

It takes a non zero amount of work to document a project such that it can be used and extended by someone who didn't write it.

Re: DataJoy is shutting down

#19

Post by chii »

jpallen wrote: post #8
timthelion wrote: post #2

Why 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 n…

if it's innovative, putting it up is still useful as a case study on how to perform said innovation. It's not bringing you any revenue anyway, so it's not like you'd lose anything. Just take out all of the keys and passwords etc from the repo!

Re: DataJoy is shutting down

#20

Post by ianleeclark »

jpallen wrote: post #8
timthelion wrote: post #2

Why 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 n…

I'm sorry to hear y'all are shutting down, I've been a big fan of Sharelatex for going on two years now and have always used it to build my resumes.
Post reply on HN