5 ms·
The problem with having your code all in a software image is that the second you do this you lose a large existing toolset that people have invested a lot in ma
by btilly 14y ago
The problem with having your code all in a software image is that the second you do this you lose a large existing toolset that people have invested a lot in mastering.
Just think of everything that you know how to do which involves a filesystem. I regularly use editors, grep -r, cd, edit in one directory and run unit tests in another, revision control systems, etc. People have invested a lot of energy into these tools, and have strong opinions about which ones they prefer and why. (Perhaps you prefer an integrated IDE. Doesn't matter, my point remains.)
As soon as you move to an image based system, your entire toolset no longer works within the inside of that image. It is, of course, a programmatic environment and replacements for every filesystem manipulation you are familiar with are available. Sometimes those replacements are better (though better is often just in the eye of the beholder). But they are guaranteed to be different. And as you move from one image based language (say, a Lisp dialect) to another (eg Smalltalk), they will be different again.
By contrast if you move from one filesystem based language to another, you will still have a learning curve, but there is a large toolset that you do not have to relearn.
- ibdknox 14y agoJust to be clear, I'm not advocating giving up the filesystem :) I wholeheartedly agree that too much work has been done there to just forsake the toolchain, but that doesn't mean you can't creatively compromise to get the best of both worlds. Exactly how that will play out will be really interesting to see I think. We've been working on some big changes to the architecture of Light Table that should set us up for figuring that out in the future. A blog post is probably coming next week about some of that.
- groby_b 14y ago"The problem with driving a car is that you lose almost all the skills you obtained by driving a horse carriage". Yes, the image interop part is a bit more difficult to solve. I'm not saying it's exactly like the switch from carriage to car, but I'm saying that some changes are worth losing existing skills
- btilly 14y agoConsider that image-based environments have been losing ground to file-system based ones for years. Consider also that core ideas that make image-based environments good can be separated from the image-based system and moved into non-image based systems. Two examples that I would give for Smalltalk are Ruby's borrowing of Smalltalks OO model, and various IDEs borrowing the idea of a refactoring browser. Borrowing the other way is much harder. For instance consider the distributed version control patterns that git enables. Image-based software development communities are sufficiently small and fragmented that they are unlikely to all duplicate the functionality of git. And because of the internal differences, they each would have to reinvent it. By contrast once git became available, it was immediately available for use with C++, Java, Python, JavaScript, Haskell... There are advantages to image-based environments, but do they outweigh the disadvantages? Before concluding that they do, you might want to re-read Worse Is Better.
- hermanhermitage 14y agoGood points. A possible approach is to consider the file system the image - consider a UI for managing a VM image and processes within that image. The difference is then essentially deciding what is the center of the system. The older image based language systems assume they are the center and all must pass through them - like a monolithic kernel. Perhaps what could be explored is more transparent integration between language runtimes and file system objects.
- DeepDuh 14y agoI think you hit the nail on the head. Build systems like GNU Make pull information about the file system to find out what has been updated. All we basically have to do is to 1) move from an information pull to a push. (Sidenote: This is something that 'kind of' works in OSX GUI, although it seems to me that 10.7 has broken this functionality for certain usecases. E.g. I'm connected to my host mac with my linux vm through SSH and when I've updated a file from within that VM, the host Finder windows get updated automatically and Preview.app windows get updated when I click into them). 2) Extend the functionality to runtimes as well, i.e. enable hotloading like in the new Unreal engine.
- twelvechairs 14y agoSurely it is possible to have an 'image-based system' where can also work with 'the existing filesystem toolset' as required. Its a bit of complexity in bridging the gap, but I don't think necessarily a show-stopper (you might disagree with me here - happy to discuss if you are interested). I agree its a big issue, but not necessarily that its a binary choice as you describe it.
- quink 14y ago> The problem with having your code all in a software image is that the second you do this you lose a large existing toolset that people have invested a lot in mastering. Intersystems Caché. There's a CACHE.DAT, which sits on the filesystem as a giant monolithic file. It's just a big block device containing a B-tree. In some nodes of that B-tree you'll find binary code. There are specialised tools to manage all this. In other nodes you will find data. There are specialised different tools to manage all this. There is the one virtual machine and it only runs one language fairly well, called MUMPS. There is an object-oriented addition to it. It's basically a huge bunch of macros that compiles down to... MUMPS. You can, in a hackish way, sometimes call specific functions from a DLL but that's as far as it gets. However, effectively... No libraries. At all. And that's the biggest pain. No libraries. I want you to let that sink in. All those things on Github and SourceForge and everywhere you, simply put, can't use. No libraries. Except the few that the vendor, Intersystems, chooses to eventually let you have... with often broken functionality. There will never be any UI toolkit or Javascript interpreter or HTML engine or nice XML parser or any of those things. There is a crappy JSON parser, but that's about it in terms of recent niceties, and it's only there because some other customer would have paid for it. No libraries. And that's the biggest problem with these software image things. No libraries. The biggest advance that we managed to get in was installing hooks in the proprietary source code editor (no vim or choice of text editor here) to export and import the code from disk. On save and load. It helped a lot to be able to get all the classes into actual files that we could use SVN with and made things so so much easier. Software images might be a good idea in theory. But in practice, you are throwing out your file browser, your text editor, your libraries and everything, everything, else.