20 ms·
Chuck Moore, Extreme Programmer
- orf 9y ago> If you have read any of Chuck Moore's work, you know that he is an extreme programmer in the literal sense of the word: a unique philosophy that embraces small, fast, self-contained programs in a spare language and an impressive development environment I haven't read any of his work, what is impressive about his development environment?
- DonbunEf7 9y agoHe designed CPUs from scratch using a bare-bones minimal Forth (ColorForth) as his preferred way of writing code. The resulting chipset is utterly fascinating: http://www.greenarraychips.com/ http://www.greenarraychips.com/
- andrewla 9y ago> from scratch This is even understating it -- it's not like he used existing software to lay out the chip, and then ran tests using PSPICE to verify the functionality. He wrote his own chip design software and analog simulator, and designed the chip in his own environment, and created the CPU, the GA144: a working 144-core processor designed to run "ArrayForth", a parallel version of Forth that he designed and authored, just as he designed ColorForth, and just as he designed, once upon a time, the language known as Forth. Any of the tasks above seem like it would be a reasonable accomplishment for a good programmer. Combined, they make me question whether I even qualify as a developer by this standard, and make me wonder whether I should take a year off of development and just really learn Forth.
- stefantheard 9y agoYour ending summary was exactly my thought process as I read the first paragraph. I essentially went through the 5 stages of grief as I realized I am no longer a developer.
- Cyph0n 9y ago> He wrote his own chip design software and analog simulator I'm going to need a citation for that. I browsed through the website and wasn't able to find anything at all mentioning the development of a full EDA software suite. There are only a handful of companies in the world that can build and maintain a full HDL + synthesis + P&R + layout + verification toolchain... Also, I would be interested to know what kind of process the GA144 is fabbed with.
- Avshalom 9y agoI don't know how much of the usual stack it accounts for or if it specifically was used for the GA144 but they're referring to OKAD, often talked about as in hundreds/thousands of lines of colorforth https://duckduckgo.com/?q=Moore+okad+forth&t=fpas&ia=web https://duckduckgo.com/?q=Moore+okad+forth&t=fpas&ia=web
- Cyph0n 9y agoBefore I put on my cynical hat, I'd like to say that it's pretty impressive stuff for a one-man shop in the 90s. ----- So it seems like OKAD is basically a layout editor, simulator, DRC checker, and GDSII compiler. The simulator uses a very simplistic transistor model that would only work at very old process nodes (>350nm?) due to the low impact of parsitics and leakage. Not even a moderately complex digital chip from the mid-90s could be designed and verified using such a simplistic toolchain. To provide a software analogy, Chuck wrote an assembler for a custom assembly dialect targeting e.g. x86, and then directly used that assembler to build an operating system kernel. Given the absence of "higher-level" constructs, the resulting OS will never be as complex as something like an NT kernel, especially due to the difficulty of testing and verification. Going back to circuit design, OKAD will never be able to design a complex digital chip on a state-of-the-art process. It's really nothing more than a simplistic EDA toolchain that would only work on simplistic circuits and fabrication processes. A modern EDA toolchain from e.g. Cadence is many orders of magnitude more complex.
- nortiero 9y agoAnd ?
- pmoriarty 9y agoI've heard of the wonders of Forth for many years -- about how it was just as good at metaprogramming as Lisp, how it was very powerful and yet extremely light-weight, about how you could run it on bare metal, and write your own OS and utilities in a fraction of the time it would take in other, more well-established languages, and so on. I got really excited about it, and when I finally started learning it, I had very high expectations and really wanted to love it. Unfortunately, overall those expectations were not met. I did find the experience enlightening, as it was a pretty different way of programming, and I love to gain new perspectives. That said, I was disappointed to find Forth was mostly an obfuscated, write-only language. Many in the Forth community preach that one should write only very short, well-documented "words" (ie. functions) that are clear and easy to understand. But the reality in the Forth code that I've seen was a lot of long, poorly documented, convoluted words which were a nightmare to read or debug. Granted, this was in the open source community. I've heard that the code in commercial Forths is in a much better state, but I don't have any experience with that. One also seemed to have to write a lot of one's own code in Forth, because there just really weren't that many libraries you could lean on. I guess I prefer the more batteries included approach. I've also heard even Forth fans admit to me that writing Forth was painful and that the point of using Forth was to write yourself a higher level language as quickly as possible, so you don't have to work in Forth. Well, I'm personally not all that interested in writing languages myself, and am quite content to use a pre-written language where all the hard and boring work was already done for me by someone else, and I can just use the nice higher-level features that already exist in these high level languages. I guess if you're on a resource-starved system like some tiny microcontroller, using Forth over assembly might make sense. But as I usually work on relatively powerful desktops or servers, I don't really see the point of using Forth there at all. I'd just rather save myself the pain and hassle, and use any of number of existing high level languages to begin with. As for Moore's work, I kind of see it like the work of someone building the Eiffel Tower out of toothpicks. It's certainly an impressive accomplishment. But how practical is it? I'm also not sure how much Moore subscribes to what have become well-accepted software engineering practices such as having good documentation, clarity of code, and testing. It seems like he prefers to sacrifice all at the altar of size and performance. That's great as far as it goes -- if that's all that's important to you and you can make it work for you (and he certainly made it work for him). But looking around at the mountains of poorly documented hacky spaghetti code in the rest of the world, it just seems like following that path leads to an unmaintainable, buggy mess.. unless maybe you are Chuck Moore and can make it work anyway.
- derefr 9y agoI feel like a desire to program in Forth is more the consequence of being a crazy-in-the-good-way programmer, rather than something that aids in becoming that sort of programmer. Moore, from my perspective, decided to bootstrap a computing architecture from as primitive and restrictive of a starting place as he could come up with. Forth makes sense as a language if you imagine yourself as a time-traveller stranded in the 1970s (or even earlier!), trying to get a "foothold" into your futuristic programming environment using the wimpy computers of the era, so that you could design and build the hardware on which would run the software that you actually wanted to write. (Which would, in turn, fix your time machine or whatever.) Learning Forth isn't really a step on that path. Rather, designing your own minimalistic language under the constraint that it'd have to 1. run on the wimpiest hardware you can imagine, but 2. allow you to be productive in the rest of the bootstrapping process — that's the first step on the path to being Chuck Moore.
- hoosieree 9y agoThe "stranded time traveler" explanation explains a lot, actually. Including motive.
- throwaway7645 9y agoI also really liked that analogy.
- jackhack 9y ago>Any of the tasks above seem like it would be a reasonable accomplishment for a good programmer. I think that's understating it. I would consider any of those accomplishments to be a monumental undertaking. Combined, it is legendary. If there is ever any doubt as to the existence of the 100x programmer - I would think this guy is proof. Somebody who creates their own chip design software as a means to creating their own multicore processor to run their own language, faster, is a motivated genius.
- e12e 9y agoYou're still underselling it; Colorforth is a traditional forth: it's the OS as well as the application[1] - it comes with drivers to write your progress to floppy disk. One of my favourite blog post by Moore is where he builds up to generate the vga signal needed to drive his monitor from the ga-144. Sadly the code links are dead, even at archive.org - but the text remains: https://colorforth.github.io/video.htm https://colorforth.github.io/video.htm https://web.archive.org/web/20160310112830/http://colorforth.com/video.htm https://web.archive.org/web/20160310112830/http://colorforth... [1] https://colorforth.github.io/install.htm https://colorforth.github.io/install.htm
- frou_dh 9y agoIs Moore okay? His charming homepage (http://www.colorforth.com/ http://www.colorforth.com/) has been down for a while now.
- agumonkey 9y agoThis thread worried me. I hope he's fine.
- teddyh 9y agoLast working archive on archive.org is here: https://web.archive.org/web/20160414102635/http://colorforth.com/ https://web.archive.org/web/20160414102635/http://colorforth...
- deleted 9y ago[deleted]
- jcl 9y agoPer another comment, he's scheduled to be at an upcoming Forth meeting: https://www.meetup.com/SV-FIG/events/243613446/ https://www.meetup.com/SV-FIG/events/243613446/
- carapace 9y agoLegend has it Chuck Moore had a 3D wire-frame CAD program he used to carry around as a punch-card deck in his shirt pocket.
- teddyh 9y agoQuote from (http://www.ultratechnology.com/1xforth.htm http://www.ultratechnology.com/1xforth.htm): “I wish I knew what to tell you that would lead you to write good Forth. I can demonstrate. I have demonstrated in the past, ad nauseam, applications where I can reduce the amount of code by 90% percent and in some cases 99%. It can be done, but in a case by case basis. The general principle still eludes me.”
- derefr 9y agoI'm not surprised that the general principle that helps Moore reduce his code size eludes him. Authoring something blinds you to your own style—both to your mistakes, and to your brilliances. It's why prose writers can't be their own editors: you need someone who wasn't in your head during the writing process to actually be able to see what's ended up on the page, rather than just seeing reminders that immerse you back into your own implicit context. I would expect that, if you took five of these rewrite projects of Moore's, and compare-and-contrasted their source with the source of the originals, principles would leap out at you. (Why don't we programmers, as a culture, read code this way? It really seems like the only way to deduce novel facts about programming for yourself. Is it just that a rewrite where both the old and new codebases are shared-source is rare?)
- tailrecursion 9y agoTo clarify a little Chuck's projects were not rewrites in the usual sense, but they can still be read that way, as derefr suggests. His famous BASIC compiler for example was an implementation of BASIC, something that's been done a thousand times before but Chuck's was not a rewrite of any particular program. Much of Chuck's code reduction comes from simply not implementing parts of the problem that most people would not think of eliminating. Other parts he will eliminate that most people would think inconceivable to eliminate. Other "secrets" of Chuck's ways are that he uses the CLI as a front end, or, spends a great deal of time working on an algorithm and finds a simpler way that is good enough in the application he's working on today. So instead of spending time optimizing for speed or modularity he's willing to specialize his subroutines per application to optimize for concision or simplicity. Somewhat like Woz's optimization to save chips. I bet most people who investigate Chuck's methods will feel disappointed that the methods don't seem as clever as the end product. What I think most people can take away from Chuck is skepticism about the utility of most programming technologies, which do automate tedium but tend to substitute their own architecture and complexity, for a net loss.
- CarlHansen 9y agoBased on the Silicon Valley Forth Interest Group email list, Chuck Moore has declared that he has retired from social media, he has not retired from Forth. He is scheduled to speak at Forth Day, November 18, 2017, as he has for years. https://svfig.github.io/ https://svfig.github.io/ http://www.forth.org/svfig/next.html http://www.forth.org/svfig/next.html
- wyattk 9y agoI want to take a moment to reflect on what a great community HN has. It never ceases to amaze me. The link is from the CS department at the University of Northern Iowa in Cedar Falls, IA. It sounds obscure, but that's my hometown. I grew up a couple blocks away from it. I sat in on classes there. I even know the author's family. That's small town Iowa, for ya. I never thought I would see anything related to that on here. This is truly a place for all.
- jjuel 9y agoIt is always cool to see UNI and Cedar Falls on HN. Also from CF and got my MIS degree at UNI.
- Roodgorf 9y agoDr. Wallingford's blog is one of the few that I make sure to never miss an entry of, it's definitely cool to see him get some recognition on here.
- lobf 9y ago> References middle-class suburban Iowa > This is truly a place for all. Edit- sorry I reminded you guys that there are other life experiences again.
- RingwormOne 9y agoSmall town Iowa is probably not very well represented on most internet forums, so the commenter was happy to see that it was being referenced... That's all. Not sure where your negativity is coming from
- lobf 9y agoWhite middle class suburbanites aren't well represented on internet forums? Don't mean to be negative, it's just insane how insular and specific this community is and how little recognition that is given here.
- 9y ago
- feelin_googley 9y agoThe "Do Not Speculate!" idea reminds me of the practice of delivering "the kitchen sink" when only a small program that does one thing would suffice. It reminds me of when, e.g., a 1990s-2000s Windows user needed a small program that does one thing, and in order to get it, the download from Microsoft was an installer with hundreds of megabytes of unneeded binary files. It was not possible to download only the single program, which was no more than 1-2MB in size. It reminds me of this quote: "The problem with object-oriented languages is they've got all this implicit environment that they carry around with them. You wanted a banana but what you got was a gorilla holding the banana and the entire jungle." - Joe Armstrong It reminds me of bloat, of giving users things they do not need. A problem that continues to this day. Instead of bloated, complex UEFI, I wish something like OpenBIOS/OpenFirmware/SmartFirmware/OpenBOOT would be available for today's hardware. I have played around with fgen on i386 and read some of the history. They even provided courses on how to write drivers. Besides OLPC, why did this not catch on? IMO, Forth is the most elegant and flexible language for initializing hardware.
- com2kid 9y ago> It reminds me of when, e.g., a 1990s-2000s Windows user needed a small program that does one thing, and in order to get it, the download from Microsoft was an installer with hundreds of megabytes of unneeded binary files. It was not possible to download only the single program, which was no more than 1-2MB in size. That might have been more to do with how hard publishing code to the web was back then, an internal process problem, which discouraged tiny stand alone exes from being put online.
- woodrowbarlow 9y agoi don't buy it. dpkg was released in 1994, and that was designed to tame the nest of people passing around small executables on the internet.
- com2kid 9y ago> i don't buy it. dpkg was released in 1994, and that was designed to tame the nest of people passing around small executables on the internet. The problem is corporate policy. In the yee old days, publishing content to MSDN was not easy. Bill Gate's rant[0] on this topic gives some insight. Grabbing small EXEs is now a lot easier. See: https://docs.microsoft.com/en-us/sysinternals/ https://docs.microsoft.com/en-us/sysinternals/ [0]http://blog.seattlepi.com/microsoft/2008/06/24/full-text-an-epic-bill-gates-e-mail-rant/ http://blog.seattlepi.com/microsoft/2008/06/24/full-text-an-...
- protomyth 9y agoForth was always fun for me because it really was fun to build up a dictionary of words that solved your problem. It practically forced coming at the problem from the bottom. I do admit that I liked some aspects of Postscript better than Forth, but both are experiences. Thinking Forth is a pretty good starting point and in general a great programming book http://thinking-forth.sourceforge.net/ http://thinking-forth.sourceforge.net/
- dewster 9y agoIt's called factoring with subroutines, and Forth hasn't cornered the market on anything by calling them words.
- protomyth 9y agoNo, but Forth provided one of the nicest, most immediate, and interactive environments to explore a problem. Instead of multiple files in a text editor, you build and test your app live and then dump it all to a text file. I have rarely had that experience with any other language except Smalltalk. I understand some Lisp environments act that way, but Forth was available places Lisp and Smalltalk were not.
- dmux 9y ago>you build and test your app live and then dump it all to a text file The Tcl shell is really great for doing this. Since everything can be represented as a string-type, you're able to introspect your defined procedures and dump them to disk.
- dewster 9y agoDeveloping on the target is just so last century. Now that programmers have developed the IDE you'll have to pull them from their cold dead hands.
- protomyth 9y agoI don't think I've used any IDE (other than Smalltalk) that was vaguely in the class of using Forth for interactivity and building of programs from the bottom up. Whats up with mocking everyone you reply to on this thread?
- atotic 9y agoI've worked with another Forth disciple in the late 80s. He was on a PC, and thought that my Mac GUI was neat. So he wrote a portable GUI framework from scratch in Forth that had dialogs, buttons, pull down menus, text inputs, graphics, mini Mac clone. It was magic. I think it was way under 100K. After that, I really wanted to become a Forth wizard. I tried, but it never clicked, my code was very clumsy, write only. I admired my coworker as an almost alien intelligence. I think it really works well for coders spiritually close to hardware.
- Chiba-City 9y agoFWIW, I wrote a graphing menuing system with primitive scalable fonts (for Arabic) in Turbo Pascal in '89 on US taxpayer dimes for live variable twiddling graphing of demographic simulations. It was all roll our own back then on 512K PC's. I implemented a Common Lisp compiler packaged in a DLL for Windows before the net took off. Some kind of "hardware and syscalls up" exercise should be part of more CS programs. It is a great experience to engineer truly reusable (and reused) code before the mosh pits of corporate labors. Good times make for useful memories.
- Chiba-City 9y agoI used to go to the NASA Forth User Group meetings in the early 90's to hang with compiler and language nerds. Chuck Moore is a genius problem solver. His Starting Forth is one great example of an introductory language text.
- SonOfLilit 9y agoStarting Forth by Leo Brodie is an excellent book, considered one of the best programming books ever written. https://www.forth.com/starting-forth/ https://www.forth.com/starting-forth/
- Chiba-City 9y agoSorry I recalled the author wrong. I'll leave your correction. Thanks.
- deleted 9y ago[deleted]
- dewster 9y agoTHE central problem with pure stack machines and stack languages: The programmer knows in their heart that moves, swaps, dupes, drops, etc. - any stack manipulation that doesn't involve a functional change to the data itself - is an inefficiency to be minimized, but this effort isn't in any way related to the problem at hand (writing a program to do something) so it's unwelcome mental overhead. I like puzzles as much as the next person, but not so much when they seriously impede the solving of a bigger more serious puzzle, nor when the sub puzzle solving is an exercise in the minimization of something bad rather than the elimination of it.
- coliveira 9y agoTraditional languages are pushing and dropping data from the stack every time a function or procedure is called, they just give it another name: parameter passing. Making it explicit, at least Forth tries to reduce the need of copying things from the stack to local variables.
- dewster 9y agoI don't think the stack in a traditional languages is the same as stacks in stack machines and languages. It's a lump of memory that gets allocated to a thread for stuff, and the allocation is indeed done in LIFO fashion, but I believe access to individual memory locations in the allocation is random. Name is the same, LIFO and all, but the mechanism granularity makes it quite different.
- coliveira 9y agoIt is true that traditional languages lump local variables and return information in the same stack. But the difference is only in the way this is handled by the program. In traditional languages the programmer has no idea how parameters are passed in the stack and the compiler does everything. In Forth this is made explicit, but on the other hand there are no formal parameters to worry about (notice that Forth can use local variables if you want, it is just not the idiomatic way).
- 9y ago
- primeblue 9y agoIt’s not trendy to be real and simple, most people love drama and complications
- Nokinside 9y agoIf our technological civilization collapses and we need to recreate it from scratch, Chuck Moore could do significant part of that.
- buckminster 9y agoOff topic, but we can't. All the readily available sources of energy have been used. As someone else said, this is literally the last great civilization. Best not screw it up!
- kbenson 9y agoThat's a note on whether a future civilization without access to our knowledge attempted it, no? I imagine some good physics and engineering texts from now might help a future civilization bootstrap itself technologically, even you have to slowly and painfully jump a few steps that would be easier with readily available oil.
- patrickg_zill 9y agoI haven't been on line much these last few days. Did we max out the Sun?
- acjohnson55 9y ago> Moore also has a corollary called Do It Yourself!, which encourages you, in general, to write your own subroutines rather than import one a canned subroutine from a library. The other side of this coin is NIH Syndrome. I've seen that go wrong in all sorts of ways. One of the key skills of being a great engineer in the real world is exercising good judgment whether to "build or buy".
- erikb 9y agoThe steps of learning <anything>. Beginner: Learn the basics, be proud of getting something done that works, even though it might not be a useful result. Experienced: Learn the systems. Figure out which system is more helpful than others. But don't worry too much before you start learning a new system. Even a "bad" system will teach you something valuable. In the end you need to learn far more than one system anyways to progress. Expert: Learn that no system is perfect and use them freely according to context, maybe create a few yourself. See that even these "bad" systems come in handy once in a while. Master: Don't bother to get here. Even most freaks won't get here and from those who do most will tell you that they had no choice to do something else and they were just lucky that at least in this area they had talent. You're probably better off than them in general terms. If you want, learn here that <anything> is just one system. Welcome to the next abstraction level as Experienced. (This system about learning is developed by yours truly.)
- swyx 9y agohow many levels of abstraction can you name? i think that would be a useful exercise.
- logfromblammo 9y agoIn the real world, anecdotally, my employers have always preferred to buy 160 hours of my time rather than share 480 hours of someone else's time with 1000 other customers. It may have been because that person is then 1/1000th as responsive to their specific needs. It also may have been because that person wasn't cleared, and paranoia requires their code to be vetted before allowing it within breathing distance of our network. Or it may have been because buying a third-party tool requires approval of the manager's manager's manager, while rolling your own is the manager's call. I have never seen a company that makes it easy to buy a third-party license, and never a company that makes it easier to use a gratis licensed software than a paid one. They're all afraid that GPL will infect the code, and it will dance out of our source control onto the Internet like children following the Pied Piper. And on the other side of that coin, I have also seen licensed third-party software become vastly more trouble than it was worth, especially when it came time to upgrade it to a newer version. In general, though, if a third-party tool already does exactly what you need it to do, and you never need it to do anything else, it is always better to license it, configure it correctly once, and then never touch it again (aside from security-related patches).
- sitkack 9y agoCharles' extreme minimalism philosophy aligns well with Forth, but it can work in many compact environments. Scheme and Lua come to mind. It is difficult at first but powerful and liberating to realize that one has full agency over their program. With other runtimes, there is no possible way to either understand the whole thing, or effectively fork it and fix what you want. Not so with Lua, Forth or a small Scheme. I really like that Lua doesn't ship much in the standard lib, but what it does ship can be used to build the world.
- ansible 9y agoThe economy of Lua's design has impressed me. You've got just one data structure, the table, and from that you can implement just about anything else... efficiently.
- astrix_pre 9y agoReally, Is Moore okay? His charming homepage (http://www.colorforth.com/ http://www.colorforth.com/) has been down for a while now.
- mmel 9y agoI found this video of Chuck speaking in 2011 just awe inspiring https://www.youtube.com/watch?v=odBjuSCX8jE https://www.youtube.com/watch?v=odBjuSCX8jE
- eadmund 9y agoI really worry for what we'll lose when he dies and no-one carries on his work. Reading about his systems is like peering into an alternate universe of engineers and technicians making the world go 'round.