Red Programming Language: Plans for 2019
There are a lot of topics here now, which is great, and the opening question about what to make of Red is a good one. The problem in answering it is the same problem we have when pitching it to people: it&#x27;s hard to sum up.<p>Is there a catch? Yes. More than one actually. One is that, because we are building things from the ground up, we don&#x27;t get things for free that other languages do. For example, JVM-based langs get a lot for free, but at a cost. Another catch, and a big one, is that Red is fundamentally different in some design aspects, both superficial (syntax) and deep (all is data, words and bindings, etc.). Those two things deter a lot of people. We get that. If you want to keep doing things mostly the way you always have, Red is not for you. If you just want lots of familiar libs and features, you may have to wait for them, or help build them. This makes us a self-selecting community. We don&#x27;t want to be a cult, but we also won&#x27;t compromise certain things with the hope of it making us more popular. There are few easy choices here.<p>For those who find Red, and give it a shot, not all will like it, and not all who like it will understand it or use it effectively. We also accept that. For those who have the courage to try something new (I mean, really try it), and who take the time to understand it (the process of which brings its own benefits, no matter what language you use), and who reach the moment where it clicks in their head, there is no going back.<p>Whether you support and commend features, or criticize them fairly, they are features. To have meaningful discourse about Red, we need to go deeper. Much deeper. If you only want to compare Red to other tools, on their terms, we&#x27;ll often lose. But if you look at what Red can do, that they can&#x27;t, and Red&#x27;s fundamental goals, it becomes clear that comparisons don&#x27;t mean much. That&#x27;s true for any 2 languages. It can help, provide context, etc., but ultimately you have to evaluate a language or tool on its own merits, just as you have to evaluate yourself and see your own worth and value without comparison to others.<p>If you think the state of software development is just fine, and a few tweaks are all we need, Red probably isn&#x27;t for you. But if you have nagging doubts about why things are so hard, so big, so complex, when it seems like they should be easy, small, and simple...maybe you&#x27;ll be curious and brave enough to take the Red pill. Most, we know, just want the big juicy steak.<p>We can talk more, explain more, if people want. Gitter is our most active channel, but we can try to respond here as well. We&#x27;re glad to hear what people like, and accept fair criticism.