Where does Linux keep `graphical-read-eval-print-loop` stuff?
It worked fine on Windows.
$ mred
path->complete-path: second argument is not a complete path: "./"
exception raised by exception handler: standard-module-name-resolver: collection not found: "mzlib" in any of: (); original exception raised: path->complete-path: second argument is not a complete path: "./"
reference to undefined identifier: graphical-read-eval-print-loop
Name:
Anonymous2011-10-31 13:46
$ sudo apt-get install mzlib
sudo: cannot get working directory
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package mzlib
$
it's completely missing.
Name:
Anonymous2011-10-31 13:54
And /usr/bin/mred is an ELF executable without source code. Cant even debug it ;_;
What I'm saying here is not ``Platform X is better than Y'', but that there should be more synergy between the developers and the platform distributors in order to deliver a stable, bleeding-edge and enterprise-ready product while reducing development and deployment time and cost, improving the overall quality of the user experience.
>>15
There should be well defined and consistent environment, that doesnt change every year. The `mred` from OP-post fails to run, because "working directory" isn't present. Windows has no such problem, because every program has it's "c:\program files" directory.
Name:
Anonymous2011-10-31 15:20
>>17
The sole fact, Linux allows absence of working directory is a big hint to its inconsistency.
Windows: designed from the ground up just to make your life suck.
That sounds a bit too close to the truth, now doesn't it lads?
Name:
Anonymous2011-10-31 15:59
>>21
At least Windows doesn't rip program into "bin shared home include lib man" bits. To install a Windows prog it's enough to unzip it and import *.reg file.
>>23
At least Unix doesn't rip program into "HKEY_LOCAL_MACHINE HKEY_CURRENT_USER HKEY_CLASSES_ROOT HKEY_USERS HKEY_CURRENT_CONFIG" bits. To install an Unix prog it's enough to untar it and make the Makefile.
Name:
Anonymous2011-10-31 16:06
>>24
Agreed. Registry sucks, like any other centralised data store. DOS didnt used it and everything worked well.
Name:
Anonymous2011-10-31 16:09
>>24 To install an Unix prog it's enough to untar it and make the Makefile.
Nope. You need to have compatible compiler and libraries + bunch of flex, bison, python interpreters.
>>25
Except it didn't. In DOS like in Windows, a program can install itself wherever it wants. It doesn't work, unless what you want is a messy (yes, even messier than Unix's /*, /usr/*, /usr/local/*, /usr/local/local/local/*) filesystem.
Name:
Anonymous2011-10-31 16:14
>>27 In DOS like in Windows, a program can install itself wherever it wants.
I used pirated cracked software. Everything was distributed in RAR archives, which could be unpacked where you want.
>>23-24
Using the registry isn't mandatory in most cases. It tends to be used in case you don't want to keep a localized configuration file for each application.