-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Abandoned? #168
Comments
Good question. Does it worth to invest time to exploring it or trying to bring back to life? avoid reinventing the wheel in life sciences
-- from https://edu.biojs.net/101/what_is_biojs/ How can we avoid "reinventing the wheel"?Based on https://www.open-bio.org/projects/
Apart from the list above - many projects have similar mission statements:
But finally we can find buried, abandoned stuffs. (Respect to exceptions - that are probably independent from a specific industry or domain and have huge number of developers and users.) I do not know the answers. I am just an disappointed developer... |
Hey folks - if anyone wants help getting rights to take this over I'm happy
to help with that as far as I can.
…On Fri, Oct 8, 2021 at 4:43 PM Csongor T. G. ***@***.***> wrote:
Good question. Does it worth to invest time to exploring it or trying to
bring back to life?
avoid reinventing the wheel in life sciences
BioJS is far more than just a registry for components - we aim to build an
infrastructure, with guidelines and tools to avoid reinventing the wheel in
life sciences – think “Docker for Bio web components”.
Easy to discover : BioJS sums up over 130 components in the BioJS Registry
<http://biojs.io/>
-- from https://edu.biojs.net/101/what_is_biojs/
But the registry link does not work:
How can we avoid "reinventing the wheel"?
Based on https://www.open-bio.org/projects/
- BioJS
- BioJava
- BioPerl
- BioRuby
- biopython
- BioPHP
- bionode
- BioHaskell
- Biocaml
- BioSmallTalk
- biolib (C/C++)
Apart from the list above - many projects have similar mission statements:
- our aim to build reusable components
- our goal is to avoid reinventing the wheel
But finally we can find buried, abandoned stuffs. (Respect to exceptions -
that are probably independent from a specific industry or domain and have
huge number of developers and users.)
It is not just reinventing the wheel. It is wasting resources of mankind:
time, money, brain capacity, energy (including electricity and efforts of
dev guys, users), food, water etc...
How can we determine the optimum of diversity, proper balance of racing of
concurrent projects? How to avoid something being monopolistic and
hindering development, adaptation to new challenges?
I do not know the answers. I am just an disappointed developer...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#168 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACGXRDTD2RD3AA2OYNJVKXDUF4GSBANCNFSM42CDD5FA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
@yochannah Do you mean this GitHub repo or the http://biojs.net repository ownership? What are your estimations?
|
What's the minimum that would need to happen to get the website back up? |
hmmm, so looking at what used to be part of biojs:
the homepage is possibly still paid for (maybe by @rajido?) and could be redirected to a new host - I can try to dig out the cloudflare credentials for it 🙈 The most recent registry front and backend repos are here:
they can be recovered from the archive if needed. I'm also happy to sign over admin rights to someone who is willing to make clear what their plans are with it. @cycle20 from my side - I don't have a bunch of knowledge to transfer beyond what's already documented in the repos as it is (I think lol). You're right that front-end moves ridiculously fast and whatever is written will be radically out of date three years later. Beyond using libraries sparingly I don't think there's much to do to avoid this. |
Update - I'm going to try to get the website back up and running in the next week or so. I will update this issue when there is some progress. |
The registry (or what I believe to be the latest version of it) is back up and running at http://biojs.net. Unfortunately as @yochannah mentioned it seems http://biojs.io is gone forever. I have un-archived the following repositories: The frontend in particular looks like it could do with some TLC. I am happy to review and accept PRs. |
Was this project abandoned? Is there a replacement?
The text was updated successfully, but these errors were encountered: