Also, there are big differences in the paradigm used. Sure OO is dominant in enterprise software, but there is also functional programming and many others that have a big impact on organization.
Yes and No. Yes in that it is still relatively obscure. I mean there have been plenty of cool Forth systems built, but I'd wager more Python gets built daily than the entirety of Forth code. Does that really matter though? Not really. It isn't a single language or even a family of languages like Lisp (Common Lisp, Racket, Clojure... etc). Rather, Forth is an idea and loose federation of philosophy concerning how to best tie primitives [written in something like Assembly or C (you want a low level language for speed and simplicity), but F#, Common Lisp, Clojure, Python...etc have all been used to write Forths] to code actually written in Forth. There is no traditional compiler and usually not too many data structures outside of the stack which is used for everything. Forth goes for extreme simplicity. There are some commercial vendors and products (SwiftForth, VFXForth, 8th), but the philosophy of Charles Moore was to just write what you need for the project. It was never really meant to be Java.
I really wish there was a modern book on implementing a useful Forth for x86 or Raspberry PI out of C. Not just a pamphlet either, but a thick book covering how to choose between all the different threading options...etc.
I don't know about "modern", but you could go the traditional route and bootstrap it from Assembler (You'll find that you only have to implement a tiny number of primitives until you can start implementing the rest in Forth itself).
> want to know more about implementing in a low level language.
You might check out Jonesforth [0], which is an extensively-documented Forth implemented in x86 assembly language. If you read the single source file top to bottom, you'll get a good understanding of how it is implemented. There are also ports to x86-64, ARM, and other machines.
If you're looking for something in C, you might check out Ficl. [1]
This particular chapter talks about implementation. It probably gets you 80%-90% to an understanding of what you need to do, and the rest should be learnable by examining other implementations, now that you know what to look for.
Forth in general is mainly used in situations where one is in close contact with the hardware (Assembly and C are the usual competitors).
It basically lets you string together a bunch of primitives and user defined functions using a stack. It is probably the only system that is useful where a single person can understand the entire language and implementation. You have to build everything yourself though.
To make a counterpoint, a 401k match is very enticing and important. You're literally matching dollar for dollar up to a certain percentage which really adds up the younger you get into it. Starting a 401k at 22 is EXACTLY the right time to do so and waiting 10 years to start could mean you've lost out on a huge chunk of money that can further propel what you put in later.
Granted, you could be the next Google/Facebook... whatever, but the smart odds are generally on the safe company with the better overall package. I bet that company also doesn't require working weekends (something most employees would rather not).
Yea, but the calories in a kg of vegetables is different than the calories in a kilogram of meat right? Or put another way, a hamburger might be the same weight as a plate of veggies and they're calorically quite different.
I agree and say this all the time. As someone who grew up driving in an ancient 60's Volkswagen with well less than 100 HP, I can tell you that we can make small cars with much lower horsepower that also get far better fuel economy.
People then tell me that they think that is stupid and like having the acceleration when getting on the interstate. In all those years, I never found acceleration to be a problem. We've been pitched cars that have way more power than we need and that use way more fuel than we need. Magazines like Car and Driver will write negative editorials if a car isn't "zippy". What should matter is safety, cost, and fuel economy.
In the US' South region, nearly everyone feels the need for a giant truck. It has been engrained as a lifestyle choice. You get your truck to help you haul your four-wheeler for deer hunting and your boat for fishing. However, 90% of these trucks are used by single individuals as daily drivers to office jobs which is extremely wasteful. They even live in suburbs which have to get bigger garages to compensate. Each man's father, grandfather, and great-grandfather drove one too, so it is deeply tied to one's masculinity. The south also has some of the nation's poorest citizens and Mississippi/Alabama/Louisiana/Arkansas have some of the worst elementary and highschools in the nation. It isn't uncommon for folks to get extremely in debt on a $50k lifted 4x4 deisel pickup truck.
This looks seriously cool and partly resembles how I think computation should be in that it is a series of steps that meat together in a data pipeline.
