I disagree. You can get up and started in most language stacks fairly quickly. Keep focus, learn to sort advice into helpful and unhelpful buckets, and start building with a goal in mind.
For example - I hadn't touched fennel nor Love2d until about a month ago, and we made something happen.
I recently learned Fennel and cranked out a Love2D game as well. Not only that, but I discovered it’s trivial to run the game on some spare nintendo consoles I have lying around, because Lua is insanely portable.
In contrast, I spent a ton of time trying to build other lisps that are designed to be embeddable on those consoles and got nowhere.
Fennel rocks. Such a pragmatic and well designed mini-language.
You can get started quickly, yeah. You can also build some stuff.
It might be useful, even.
The article is about what it takes to really know a language. That's a bigger task. It takes months, if you work fast. That's how you write high-quality, maintainable software.
Python frustrates me too, but I just throw poetry and nix at it... keeps me not frustrated. :D
It looks like my LOVE game uses about 99M resident... not too bad given it's pulling in a lot of libraries such as SDL2, luajit, audio decoders, etc etc.
I think my concern is more with how do I embed Racket on low memory systems if a simple "racket script" is going to use a large % of the RAM to issue a `(sleep)`?
I disagree. You can get up and started in most language stacks fairly quickly. Keep focus, learn to sort advice into helpful and unhelpful buckets, and start building with a goal in mind.
For example - I hadn't touched fennel nor Love2d until about a month ago, and we made something happen.
You can do this too.