8 ms·
- Smallest unit of code is the function. - Able to get instant feedback on code changes. - Multiple editors with just one function in it. Show code
by stcredzero 15y ago
- Smallest unit of code is the function.
- Able to get instant feedback on code changes.
- Multiple editors with just one function in it. Show code
in an "area of concern" not just in a file.
- The coding environment can show also results, app
windows, graphics, other tools.
- Can save the configuration of the above.
Smalltalkers have been doing this in commercial projects since the 80's. If only we could have communicated about this as well as Mr. Granger.
EDIT - Also:
- You should never have to look for documentation
- Files are not the best representation of code,
just a convenient serialization.
- Editors can be anywhere and show you anything - not just text.
- Trying is encouraged - changes produce instaneous results
- We can shine some light on related bits of code
Things like this were happening in Smalltalk environments since the 80's. The first and the last points above were satisfied by lightning fast "senders" and "implementers" searches.
- gecko 15y agoYes, but our code was entirely in these utterly unusable changeset files that couldn't work nicely with the version control that everyone else in the entire world was using; his version still uses files under the hood. There's a team that's trying to back Monticello with Git, I believe by saving each method into its own file in part of a Git source tree; that looks promising as a compromise.
- fstephany 15y agohttps://github.com/CampSmalltalk/Cypress https://github.com/CampSmalltalk/Cypress Hopefully this project will take off :) Smalltalk vendors will probably add a layer of Envy/Store/Monticello on top of it but that would be a giant step forward.
- jfno67 15y agoI immediately thought of Visual Age for Smalltalk when I saw this, but having been done is no reason to not try again.
- bsg75 15y agoVisualAge for Java was my thought. Unfortunately, as with many of IBM's good ideas - before its time, poorly marketed/placed, etc.
- super_mario 15y agoVisual Age for Java Micro Edition (re-written in Java) became Eclipse framework.
- bsg75 15y agoI did not know this. History even in software is interesting (http://en.wikipedia.org/wiki/IBM_VisualAge http://en.wikipedia.org/wiki/IBM_VisualAge , http://en.wikipedia.org/wiki/Eclipse_(computing) http://en.wikipedia.org/wiki/Eclipse_(computing)) I wonder why the built in code repo did not become a feature - unless this another part of the project history I am unaware of.
- roguecoder 15y agoWe also had Virtual Machines with snapshots and rollbacks doing the things VMWare is now pushing so very hard. I have missed those tools for the past 13 years, since I left the language. The idea that I might get those tools back, in a language that also supports all the emacs-or-gtfo coders, is like promising me a perpetual motion machine. I will believe it when I see it, and until then it will taunt me in my dreams.
- bitops 15y agoThere is a Gemstone group at VMware. Send your resume.
- gfodor 15y agoOf course this comment was inevitable. If Smalltalkers really believe their environment is the right way to code, their attitude should not be one of "we did this first, meh" but instead be "here's what we did right, here's what we did wrong. heed the lessons of history and good luck, you are on a mission from God." I think with the proper care and nurturing, we could be at the beginning of a renaissance where many of the great ideas of the 60s and 70s that have been isolated to a small group of people (who are aging rapidly) are being rediscovered and reimagined by this generation. This is happening in no small part due to Rich Hickey and the Clojure community's unbelievable foresight in developing Clojure and ClojureScript in just the right way that it balances these pure, beautiful ideas with pragmatism in a way that makes them irresistible. Those who lived through the heyday of Xerox PARC, the AI lab, the lisp machines and Smalltalk should see this as an opportunity to help make sure things don't go off the rails this time. Otherwise, we may end up back here again in 25 years with the C++ and MySQL of the future installed in our cybernetic implants. I can already point to projects that are invisibly pushing us towards another deep, sticky, next-generation tarpit, and people are diving in because it's not yet recognizable as such. (I won't name names!) Lets try to make it so this time around we truly realize the dreams of computation by encouraging people who are building elegant, beautiful things for the modern era, no matter how much the ideas therein have been tried before.
- jessep 15y agowhy not name names? seems like it could be informative.
- gfodor 15y agoNot in this thread. This is Light Table's moment to shine, don't want to clog it up with such a derail.
- mmc 15y agoThen do it somewhere else and point here, please? Another comment mentioned version control, which is a very important thing to get right, and I don't know how I'd diff two Self workspaces, for example... What other sticking points are there?
- deleted 15y ago[deleted]
- michaelfeathers 15y agoTrue, Smalltalkers were there first. The thing I like.. the further enhancement here.. is the UI. No more tiles and windows.
- mgunes 15y agoField (http://openendedgroup.com/field http://openendedgroup.com/field) is a modern programming environment that embraces most (if not all) of these principles.
- msutherl 15y agoAs always, the multi-media programming environments are miles ahead and nobody knows about them. Field is amazing. Max/MSP, Pd, et al. are a different paradigm altogether, but have had live editing, documentation a click away, etc. and have been in heavy use for 20+ years.
- dkersten 15y agoI've been using Max/MSP lately and while I find the language itself lacking (one example of something I wish I could do is nested lists), the editor is amazing. The live programming is ahead of any normal REPL I've used and the debugger is pretty cool too. If it had a few extra features it would make it pretty close to my ideal programming environment: a way of (temporarily) disabling selected code; a unit testing mechanism and a way of extracting selected code to a unit test; a visual code diff tool; git integration (especially branches)
- mushly 15y agoWhere can I find a list of these amazing multi-media programming environments that I've never heard of before, but which look so awesome?
- mgunes 15y agoI was unable to find anything close to a definitive list, but http://en.wikipedia.org/wiki/Visual_programming_language http://en.wikipedia.org/wiki/Visual_programming_language is a start.
- msutherl 15y agoMax/MSP, Pure Data, vvvv, QuartzComposer, SuperCollider, ChucK, Processing, openFrameworks, Cinder, and Field are the big names. But there are many more smaller projects such as Lubyk, Overtone, LuaAV, Faust, Plask, Impromptu and Fluxus. I also want to plug NoFlo, which is a 'flow-based programming' library for node.js, which integrates with a visual editor.
- scottjad 15y agoIn the Table view it might be nice to color the cards based on their namespace like Whisker browser: http://www.maartensz.org/computing/squeak/Helps/Programming/WhiskerBrowser.gif http://www.maartensz.org/computing/squeak/Helps/Programming/...
- kristianp 15y agowhat smalltalk didn't quite do is the instantaneous view of the results of your code changes. Seeing the result of your changes in Light Table is like updating a cell in a spreadsheet. Smalltalk (I'm guessing), would involve switching to the executing window or hitting a play/continue button. A subtle difference, but it takes the immediacy to the next level.
- blake_ 15y agoNo, it was, is or at least can be, instantaneous where that makes sense.
- fusiongyro 15y agoAutotest, which is now built-in to Pharo, will automatically run unit tests relevant to the method you're editing when you save the method, so you can get pretty close. http://magaloma.blogspot.com/2010/06/autotest-for-pharo.html http://magaloma.blogspot.com/2010/06/autotest-for-pharo.html