3 ms·
The classic problem with inventing your own language is that now you can't understand anyone else. If we're going to have widespread communication then we need
by skybrian 7y ago
The classic problem with inventing your own language is that now you can't understand anyone else. If we're going to have widespread communication then we need widely-understood languages and libraries. The goal should be to replicate understanding. We need to evolve a common vocabulary rather than ending up with nearly as many private dialects as programmers. Publishing libraries and gaining users for them should be a primary goal.
There are Forth words with generally agreed-on definitions but it seems it's not designed to grow a large, common vocabulary in the way that modern package managers enable.
- pavlov 7y agoThe counterpoint is that every software project of reasonable complexity evolves its own language anyway. When that is layered on top of overly generic libraries/frameworks, you may end up using only parts of the underlying vocabulary. Now the project is stuck with two vocabularies. Learning the generic one doesn't get you far and may be actively misleading ("yeah, we never use features X and Y of the framework, instead we've overridden Z with our own implementation that does all this plus W").
- skybrian 7y agoYes, that's a problem with code sharing gone wrong. Another problem is framework churn where popular libraries aren't stable. When good, stable libraries aren't available then it may be better to reimplement than to use a bad one. But these problems are, in their way, a sign of success at the package management level. If you don't have good package management then people probably aren't having much success at sharing code. We should still aim for building and sharing stable, well-understood, high-quality code libraries. Unfortunately, sometimes the way to get there is to go through a period of instability.
- eckza 7y ago> We should still aim for building and sharing stable, well-understood, high-quality code libraries. And I agree with that 100% - but that isn't the solution to every single problem. That's all I'm saying.
- kharak 7y agoI'm also for a common vocabulary, but I wonder why you're getting downvoated for having another opinion.
- eckza 7y ago> Forth is quite "invidualistic", tailored to single persons or small groups of programmers, mostly because it is natural and relatively straightforward to implement a Forth system yourself (and you should) and because the language is inherently malleable and adapts to your needs. Therefore what I write is just one way of seeing Forth, which is both a programming language and a engineering philosophy. Sometimes... you don't need to understand anyone else, or to be understood by anyone else. Sometimes you just want to do what you need to do. The goal of replicating understanding is all well and good, but that shouldn't be the primary goal of programming language development, nor should it be the primary goal of programming. I don't think that anyone is suggesting that we start rebuilding enterprise service frameworks in Forth.
- skybrian 7y agoAs a specific example, I'm dabbling in embedded programming (like Arduino) and switched to Teensy for the audio library. I guess the Forth philosophy would be to figure out how to program real-time audio from the microprocessor's datasheet? I'm not really a fan of C++ but I knew better than to go that deep. Arduino itself is a good example of how a decent, common abstraction can help users get started.
- jes5199 7y agoyou could probably get a lot more done on arduino by writing a tiny forth in arduino C and then writing your applications in _that_
- eckza 7y agoThis seems to be the preferred methodology, actually. One of my close friends is an embedded systems developer and this is what he does. One of the big advantages of Forth is that it's (apparently) pretty trivial to implement on your own, in whatever environment you choose.
- deleted 7y ago[deleted]
- steveeq1 7y agoThen how can paradigm shifts occur?