8 ms·
Final “STEPS Toward the Reinvention of Programming” Paper [pdf]
- e12e 11y agoozten[2] wrote: "Last week VPRI[1] published the final "STEPS Toward the Reinvention of Programming" paper[this submssion]. Although it is 2012, it had been unavailable publicly until now. A great way to catch up on how FONC ended. It was worked on by many individuals being cited as part of HARC. [1] http://vpri.org/html/writings.php http://vpri.org/html/writings.php [2] https://news.ycombinator.com/item?id=11680238 https://news.ycombinator.com/item?id=11680238
- NotUsingLinux 11y agoSorry but its 2016, publishing a paper is not enough. Alan kay of all should now we need more , we need: The three/four pillars of reproducible research Often in the discussions around open and reproducible science we focus three main types of research products 1. the paper: the traditional narrative document, often 2. the data: increasingly appreciated as a first-class citizen of scientific record with data repositories providing DOIs 3. the code: recognized as a research product, but the last to be integrated into literature system and given DOI 4. the environment: a critical and under-appreciated ingredient for computational reproducibility THAT should be the minimum for all science projects IMHO. What do you think?
- e12e 11y agoI'd love to see full sources and build system that allowed everyone to play with Frank. I was sure I'd made a comment to that effect somewhere, but I can't find it now, perhaps it was eaten by my outdated smart phone. On the other hand, I believe the paper(s) might very well be more important: exploring the ideas. I think it's a difference between a research project in computer science, and an engineering project. The first lambda calculus was just a project - they thought they'd need years to get the thing running. And then someone just coded up eval() in machine-code and they were bootstrapped. I to want the implementation of eval(), but I'm not unhappy that they've shared their ideas.
- e12e 11y agoOh, yeah there it was: https://news.ycombinator.com/item?id=11686096 https://news.ycombinator.com/item?id=11686096
- wangii 11y agoI can't believe this group of incredibly smart people have produced this not-so-impressive paper. Sure, the size of source codes is a big problem. but is LOC the most cost-effective issue to investigate into? Why none of the existing module approaches work? Is this really a language problem can be magically solved by FPR? Can this 20k app handle Chinese characters? How many corner cases does it handle? Abstraction leaks, and I don't believe in any silver bullet.
- e12e 11y agoIt's not "an app". It's an Operating System that runs on bare hardware, and the applications one would need. It aims to do the useful work that a word processor, DTP program, drawing program, web browser and the file system, drivers, rendering sub-system, networking stack and much more does. All in ~20kLOC. I seem to recall they support full unicode, by the way (which makes sense today, there's not many good reason to not try for full utf-8 compliance unless you want to do some entirely different encoding (like a simpler, prefix-based one) and then do conversion at the edges of your system)).
- NotUsingLinux 11y agoLike in my other reply I make a strong demand for reproduce able science. Where is the integration build of frank? Just one binary with source that work, alan kay did run some demos on a mac. Its too bad that this great software is now starving on some researcher archives :( I call for reproducible science: https://twitter.com/KyleCranmer/status/728644857288372224 https://twitter.com/KyleCranmer/status/728644857288372224 Where is the CI Server of the project? It can't be that hard.
- vajrabum 11y agoYou're looking at the cleaned up final summary report to the funder of a research project. There isn't any CI. This wasn't a project to build a system. This was research to explore the possibility that operating system and application software can be radically simpler than it is today. Over a number of years they investigated many different systems which addressed aspects of the problem, wrote papers about them and yes made source codes and other artifacts available. It's (mostly) all here http://www.vpri.org/html/writings.php http://www.vpri.org/html/writings.php, http://tinlizzie.org http://tinlizzie.org, and http://tinlizzie.org/dbjr/ http://tinlizzie.org/dbjr/. So no, CI is not that hard. It's also not what they were paid to do.
- ozten 11y agoOne of the key issues was that they started STEPS with the premise that they needed NSF funding for running the FONC project on super computers. This strategy is to "time travel" 10 years into the future, like Alan Kay did at Parc to develop the Alto. In this last phase of the STEPS project, sub-systems like the graphics system were close to running fast enough on commodity hardware, that they changed course during this last phase, abandoning time sloted for design iterations and exploration, to focus on optimization instead.
- david927 11y agoFor me, they ran before they could walk. Anything graphics-related could wait (although Nile is awesome, so they're forgiven). It feels like they were focused on trying to sell their findings rather than just focusing on research. But I'm a huge fan of everyone involved in this, so that's not criticism -- just speculation.
- twelvechairs 11y agoIm not usually an advocate of 'you need to hire a UX/UI person' but this really needs a good one. Its trying to show people a lot of different information and theres no graphical clarity to it at all. Worse it looks like the worst kind of interfaces from the early 1990s. Its painfully obvious nobody on the team has any graphic/visual background. I guess its just the difficulty of projects coming from a university/science/research basis where these things arent valued because they are hard to quantify.
- wolfgke 11y ago> I guess its just the difficulty of projects coming from a university/science/research basis where these things arent valued because they are hard to quantify. IMHO rather because in research projects at universities there is no position (in the sense that one can spend money on it) for people who aren't either researcher or administration. UX people surely have their importance but they neither bring research results nor they are a "necessary evil" (adminstration - which is no contradiction that good adminstration personal can be really helpful).
- seanmcdirmid 11y agoWell, there are HCI researchers who do design/UX/UI; more straight up design research in CS would be nice though.
- kennethfriedman 11y agoI'm curious how much of the code base will be publicly available. It would be great to try this stuff out.
- david927 11y agoOne portion, Nile, is available on github: https://github.com/damelang/nile https://github.com/damelang/nile
- e12e 11y agoSee also Ometa: http://tinlizzie.org/ometa-js/ http://tinlizzie.org/ometa-js/ https://en.wikipedia.org/wiki/OMeta https://en.wikipedia.org/wiki/OMeta https://github.com/alexwarth/ometa-js https://github.com/alexwarth/ometa-js And Cola: https://en.wikipedia.org/wiki/COLA_(software_architecture) https://en.wikipedia.org/wiki/COLA_(software_architecture) Some more links on the WP page for VPRI: https://en.wikipedia.org/wiki/Viewpoints_Research_Institute https://en.wikipedia.org/wiki/Viewpoints_Research_Institute And VPRI's own wiki: http://www.vpri.org/vp_wiki/index.php?title=Main_Page http://www.vpri.org/vp_wiki/index.php?title=Main_Page As far as I've been able to gather, the most immediately useful stuff, is the ideas and concepts in OMeta, as well as the various implementations of OMeta.
- joshmarinacci 11y agoOmeta is amazing. Ohm, the successor is even better.
- agumonkey 11y agoI suggest people to walk the fonc mailing list, lots of old threads with smart people discussing interesting ideas.
- Animats 11y agoThis is a strange paper. It reads a lot like "Personal Dynamic Media", Kay's paper from the 1970s, which led to the Alto and Smalltalk. Back then, this was all new. Now, it's not. The big thing here seems to be defining domain-specific languages (they don't use that term) which allow certain classes of problems to be written concisely. The examples given of those language look rather conventional: selectionWatcher <- when DocEditor.selectedDocBox :b then this.textContents(if b then b.printString() else "") ... Their approach to GUI programming: layout ^ KSSimpleLayout new keep: #topLeft of: ’titleBar’ to: 0@0; keep: #right of: ’titleBar’ to: #right offset: 0; keep: #height of: ’titleBar’ to: 25; ... These are constraints for a constraint engine, which is a good idea not original with them. But writing constraints as text is painful. You can do that sort of thing in CAD programs such as Autodesk Inventor from the GUI, and you get useful error messages when you overconstrain or underconstrain. That's how web page layout really ought to work. They created about 100 domain-specific languages, and in each, the demo programs are short, because the languages are well-matched to the specific problem. But they didn't get to the point where they put users on these languages. That's needed to find out if they're as concise as claimed, or the users end up writing complex code to get around limitations of the language. There are widely used domain-specific languages, such as Matlab and Excel. In each of those, stuff the language designer thought of is easy, and hard stuff is really ugly. That's what usually happens. Not seeing the big breakthrough here.
- sp332 11y agoThe big breakthrough is making it easy to create new DSLs for any situation. Every area of the OS has its own language (and you can just add more if you feel the need) so that the whole OS including networking and GUI is very compact, understandable, and hackable. This particular project focused on compactness, just to prove that it is quantitatively more expressive.
- skratlo 11y agoI was studying Racket lately, and it sounds very familiar now. DSLs, or dialects as Racket calls them, is surely way to go and improve productivity, it should however, always be possible to descent down, or escape from that DSL, where needed, to avoid the hacks that work around a certain limitation of this or that DSL. (lisp macros, wink wink)
- kristianp 11y agoOne of the demos of their research was a "A full TCP/IP stack in under 200 LoC" (2008), see https://news.ycombinator.com/item?id=846028 https://news.ycombinator.com/item?id=846028 , Described in http://www.vpri.org/pdf/tr2007008_steps.pdf http://www.vpri.org/pdf/tr2007008_steps.pdf It appears as an example in the cola source: https://github.com/robertpfeiffer/cola/tree/master/function/examples2/tcp https://github.com/robertpfeiffer/cola/tree/master/function/...
- cowardlydragon 11y agoI hear APL is concise.
- cowardlydragon 11y agoYou know what else was concise for UI? HTML. ... but people wanted their rounded corners. ... so now it's not concise.
- mlvljr 11y agoA relevant lecture from Alan Kay: https://www.youtube.com/watch?v=FvmTSpJU-Xc https://www.youtube.com/watch?v=FvmTSpJU-Xc