You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Linux all of the Omega project deliverables MIGHT be downloaded with a
command line program "lftp"
mkdir ./the_copy
cd ./the_copy
lftp ftp://ftp.cs.umd.edu/pub/omega/
# at lftp console please type
mirror ./
# and after the download is complete, please type
exit
As of 2022_01_06 I haven't studied the Omega project yet, but I found it from
and my motivation is to assemble myself a collection of local copies of
various software projects. The idea is that in a chemistry lab there is a
storage area with a huge amount of different reagents. in electronics lab
there are storage containers with a huge variety of different electronic components
and in a software_laboratory there should be a "local storage" with
software components and their documentation. Basically, a classical paper-book-library
analogue of software components, a "private GitHub" with a personally assembled selection
of components that one has personally tested and has extra notes about how to
use/build them, preferably with custom build scripts, custom packaging.
One may call it an arms race between software developers and there have been
many fine projects that have gone offline and that are useful for interfacing with
legacy systems. Academics do not need to deal with legacy systems, but IRL the
newest and greatest oftentimes has to use something from the giants before us, specially
if it has something to do with hardware, because hardware costs and even if it were for free,
its installation costs. An example: mountains can be for free, but the builders, who crave caves/statues
into the mountains do ask/need some sort of payment. The same with hardware installation and setup.
Thank You for reading my comment.
The text was updated successfully, but these errors were encountered:
An idea:
As of 2022_01_06 I haven't studied the Omega project yet, but I found it from
http://www.cs.cmu.edu/~scandal/research-groups.html
and my motivation is to assemble myself a collection of local copies of
various software projects. The idea is that in a chemistry lab there is a
storage area with a huge amount of different reagents. in electronics lab
there are storage containers with a huge variety of different electronic components
and in a software_laboratory there should be a "local storage" with
software components and their documentation. Basically, a classical paper-book-library
analogue of software components, a "private GitHub" with a personally assembled selection
of components that one has personally tested and has extra notes about how to
use/build them, preferably with custom build scripts, custom packaging.
One may call it an arms race between software developers and there have been
many fine projects that have gone offline and that are useful for interfacing with
legacy systems. Academics do not need to deal with legacy systems, but IRL the
newest and greatest oftentimes has to use something from the giants before us, specially
if it has something to do with hardware, because hardware costs and even if it were for free,
its installation costs. An example: mountains can be for free, but the builders, who crave caves/statues
into the mountains do ask/need some sort of payment. The same with hardware installation and setup.
Thank You for reading my comment.
The text was updated successfully, but these errors were encountered: