Difference between revisions of "General software issues"
m |
m (→CAD software) |
||
| Line 50: | Line 50: | ||
== CAD software == | == CAD software == | ||
| − | [Todo ...] | + | [Todo ...] <br> |
| + | Nanoengineer-1 example: [http://machine-phase.blogspot.co.at/2008/04/afm-images-of-ne1-designed-origami.html] | ||
Revision as of 15:53, 21 April 2014
In a world where the digital and physical realm starts to blend that is physical products become metworked live acutateable and reconfigurable software architecture / organisation / design or however one may call it becomes even more important than it is already today.
Key issues are:
- stability (at best error-proofness) correctness; research in Haskell
- maintainambility
- extendability
- modularity
- diversity (as options for unexpected dead end routes)
- optimized-specialisation conserving functionality-expanding-generalisation and vice versa
- highly complex version management (dependency hell)
- ...
File systems
Currently used tree based and machine local file systems have their limits. Sorting the same data after multiple hierarchical criteria is impossible. To give an example: Assume one owns a lot of image-file text-file sets. The small text files are of high importance (e.g. source code) while the huge images are of relatively low importance (e.g. rendered from source). Archiving different backup levels (location, redundancy level) for file types of different importance isn't possible with the basic functionalities of tree based file systems.
File system indexing usage of meta-data and file tagging only mend but do not solve the problem. Some kind of graph based file systems are needed. Graph databases (like Neo4j?) are interesting but are only crutches if implemented on top of tree based file systems.
The limitation to serial access to mass storage disk space (now changing with random access SD drives) led to the fact that current systems are still hardware near programmed and suffer from a lack of abstraction. Data must be manually serialized for persistent storage. Net based services like Google drive and Facebook already emulate this behavior. Another interesting "on top" approach is yesod with its integrated persistence.
- A good writeup about the problem and solution approaches can be found here: file system alternatives
Dependency hell
Current packet management systems suffer from the dreaded problem of dependency hell. Especially developers who install a lot of software packages in parallel are affected. Solution approaches include:
- Packet manager of experimental NixOS - review
- multi-platform reversible java package management system
Avoiding hidden state (a potential source of errors) can be compatible with interactive environments:
- Wikipedia: Functional reactive programming; research of Conal Elliott
- House - functional operating system
CAD software
[Todo ...]
Nanoengineer-1 example: [1]
