3 ms·
I'm trying to parse your first paragraph. Isn't Unix entirely about modularity? And I suppose you could argue that emacs is a (os like) substrate that enables
by benj111 8y ago
I'm trying to parse your first paragraph.
Isn't Unix entirely about modularity?
And I suppose you could argue that emacs is a (os like) substrate that enables modularity on top of it. Theres an old joke, emacs is a nice OS, only lacking a decent text editor.
Or are you referring to the actual code itself?
- jrockway 8y agoI think he's just saying that the Unix philosophy of hundreds of different programs that communicate with pipes lost out, for him, to everything in one address space communicating with data structures, which is what Emacs is. Emacs was derided for being the anti-Unix. It's a text editor... but it has a shell, and a calendar, and reads email? CRAZY. WRONG. But in reality, the Unix way is showing its age and Emacs was a solution ahead of its time. Emacs as a computing environment is remarkably consistent across platforms. Say you write code, commit to a git repository, and run shell-like commands. Your Windows computer will look exactly like your Linux box if you use Emacs with magit and eshell for those operations. I personally kind of fell out of using a lot of Emacs's extras, and am constantly cursing the inconsistency between platforms. But, to some extent, Emacs has failed even in that regard by depending a little too much on the host OS. As far as I can tell, there is no binary I can download for Windows that will let Emacs spell check anymore; the last time someone compiled aspell was in the early 2000s and the latest version of Emacs explicitly checks for that binary and tells you you can't use it, providing no alternative. The failure is not in packaging this for Windows, of course, but rather in allowing the OS to provide the spell checker. That should just be a lisp package! But alas, it is not. (You will also find this in other things. M-x rgrep is a favorite of mine on Unix-like systems. But on Windows, find.exe is not quite the "find" that find | grep is looking for, and it's kind of a pain to get your path setup to find the Unix version of find while in Emacs, and still let native windows programs get find.exe included with Windows.) However, for those ambitious enough to decide to implement the functionality in pure Lisp... you get "write once run anywhere" which is quite enjoyable. (And was a thing before anyone ever coined the phrase "write once, run anywhere".)
- xte 8y agoWell... Unix bring the idea of being a "base platform" for third party software using simple IPC as a way to integrate any different kind of software. This work well in many case, but can't really scale so I consider UNIX model as a good model for "embedded devices" nothing more. Today's unix, only with X prove that unix model does not exists anymore. Emacs bring the idea that there is no real distinction between application, OS, data whatever, we need a completely integrated computing environment that act "uno animo" easy bent and build for anyone by anyone. This works really well, but in academia, so in a super-slowly evolving environment because the level of complexity needed to realize such idea in practice is so high that's demand decades only to create a desktop... That's why Emacs while keep evolving and even after decades it's still on the scene, it shine or better as someone say it outshine other software like the sun outshine night stars, but it suffer it's own architecture being nearly unable to really radically evolve... I hope for a distant future with a GuixSD OS, perhaps based on Plan9 (more interest IMO than Hurd), that boot directly into Emacs instead of a shell and anything is done with Guile Scheme so I can really see and use a LispMachine in the present (future) but it's a dream I do not really think it can ever arrive...
- anthk 8y ago- GuixSD is writting a Bash replecement shell based on Scheme =) - About Unix and Emacs, I like both approach, but Emacs tends to locks itself pretty often. Now, if there was an Acme-like editor without mouse chord and Vi keys, it would blast anything. Emacs has google-translate-at-point, I, myself, just use xsel on the clipboard and pipe it automatically to translate-shell. A cwm keybinding, and I get a translated text on a popup.
- sedachv 8y ago> I, myself, just use xsel on the clipboard and pipe it automatically to translate-shell You can do SHELL-COMMAND-ON-REGION (M-|) and get the output in the echo area.
- xte 8y agoSorry for my English, I'll try to be clear... > Isn't Unix entirely about modularity? No, unix goal is to provide a minimal "platform" that third party software may use as a "detached" base and interoperate via a simple, small and common IPC mechanism. Unix is essentially like a wagon to support any kind of boxes/pallets. LispM, Alto workstations, ITS, Emacs do the opposite: the OS must not be for them a platform with a very basic set of API/IPC any software can use but a sole, single, integrated environment in witch any software live inside like a complex machine. Unix was a success being simple because at that time using "unix-hater's OSes" was expensive, hard, to a point that you are totally tied to specific hw and you have to know many things to develop even a super-simple software. After however unix prove to be unable to evolve. Third party "giant frameworks" became a common thing, X with it libs etc is the most common example. Basic subset of functions and IPC can't compensate. We do not develop ANYTHING serious anymore after that, Plan9 was probably the last tentative but never get completed enough... I consider actual Emacs such as a small way to keep LispM alive, that suffer enormous limitation of not having hardware, bootloader a kernel to be a real OS however in today's tech status it offer the best way to operate on a desktop: everything is integrated through the most common things we know, text. It's status prove that idea is valid but so complex to accomplish completely that's practically failed. We simply can't sustain economically a LispMachine today. Hope to be more clear now...
- benj111 8y agoI think what you're saying is, is that modularity at the level of the library is what succeeded? Rather than at the process /syscall level, or in process level. To borrow your analogy. Pallet/shipping containers are modular(they won). Individual boxes and container ships, less so. I can get behind that. I'm not sure that's the absolute best way. Although as I write this, I'm reminded of the web browser I'm writing it in. Is it not more emacs than emacs?
- xte 8y agoHum no, being "platform" for independent communicating software succeed at first (unix), after reach it's limit and it now appear clear that ancient idea pre/against unix of "fully integrated environment" in witch "programs" are only a module/code inside the "big" environment/framework succeed, unfortunately only partially because complexity it's too high to evolve it properly at "modern speed"... So we do not have now nothing that can really work at a scale only various horrid, hard to maintain and future-less hybrid solutions like Windows, GNU/Linux, AiX, HP_UX, True64, ... ... On today's web no it't certainly nothing like Emacs. In Emacs YOU have the full control of your environment, in modern web you only think to have a certain control but in the reality you are a powerless puppet of few giants companies... The sole similarity is the concept of hypertext itself that offer a kind of integration similar to Emacs one, but it's similar at a very superficial level because in Emacs it's integrated anything, not only the presentation level. In Emacs you can modify your software at runtime during normal use, not only link/integrate any text around your documents :-)