Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That's a plausible use case. Question is, if the engineer goes away, how long would it take to replace him? Languages do not take too long to learn, but Forth programs are often hard for others to read.

I think most people prefer cross-compilation on small systems for professional use.

If you are doing it as a hobby, ignore everything I just daid. I see the fun in it, and applaud it. Enjoy!



Again, depends on how the Forth is done.

Counter question:

Given the obvious savings, why not invest some of that into a second person to retain a clear advantage?

Do what most people prefer and get results that most people get.

There are other ways to success.


> There are other ways to success.

Absolutely. I've played with Forth many times, and enjoyed it. But when it comes to building systems that people pay to develop & maintain, I haven't found any use cases recently. No doubt there are some, but I suspect they're much less justifiable today.


Let me expand a bit. Was tired when I wrote the snarky comment.

In a typical corporate environment, yes. Your thoughts ring true.

It is a big world outside that scene, and many playing there can benefit from Forth. That is the utility. People who grok Forth flat out solve hard problems like no other.

Tool for that toolbox, essentially.


Putting pay under emphasis does not add any value to your earlier comment.

It's a big world out there. Guess I shall reply with same.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: