Neko

HOWTO ruin a language

Last modified: 2026.04.01


Programming languages are meant to aid in the very tedious and complicated process of telling computers what to do, also called as programming. The first programming languages were made in the 1950s with stuff like FORTRAN, ALGOL, or ENIAC Short Code and were just rudimentary translators or interpreters. We’ve came a long, long way since then, for good or bad.

Modern programming languages are, according to absolutely every one of themselvers, replacements for the previous failure of languages, although most are new kinds of A/B failures autogenerated by shitty AI agents so the self-proclaimed “developers” don’t have to use other tortures of “multi-paradigm” FLOSS kitchen-sink languages, made by OTHER giant self-proclaimed “indie” open-source capitalist profit-first companies entirely focused on attracting inversors, that also seem to “love” <insert here EVERY cause that may bring them money>, mainly to suck inversors.

I will go on more detail for THIS on this article, and how to make your own shitty programming language!

1. Solve a problem that doesn’t exist

Wait, my elevator isn’t working, this is C’s fault! I shalt replace it [C, of course, that is the culprit]!” — Rust’s lore

For starters, the reason most languages suck is because they are superfluous. The best code is that which does not exist: as it always is the least vulnerable, least buggy, and most mantainable. Most programming languages have a seemingly rational goal, e.g.:

“We want to make programming easier.”

or

“Low level programming, but safe.”

This is, of course, a shameless trap to fool themselves into thinking the language isn’t nonsensical, and for others so they can put “Adopting the future, est. 2025” as their slogan on their vibe-coded Tailwind Vue JS/TS Docker Rust WebPack Vite crypto homepage. Of course, only a couple of languages have achieved their purpose, and those were much clearer than what modern languages introduce. Now you need to introduce:

And you MUST make ALL of these. Great! Now you need to add MORE languages, we already have the statement sublanguage and expression sublanguage, why don’t we add more! The loop language: our overengieneered macro system will allow us to construct a DSL inside the looping keyword, and also an error system template! And why not? We’ll build a DSL for documentation and pragmas based on fucking comments. You need to make it complex! Power requires complexity! Of course!

2. Introduce all paradigms a capitalist company has proven “effective”

You know what is a GREAT way to attract early users? Allow them to use THEIR programming paradigm on your language. And use ALL of them at all. HTTP module procedural, Iterators OO, whatever you think fits best! Most languages are just big clusters of functionality with little-to-no rationale behind anyways. But overall those that can give YOU the highest revenue, and the most “proven” ones, so there is absolutely no risk whatsoever!

3. Expressive syntax

So “expressive” is the new euphemism for “insanely complex” nowdays? (Uriel), I guess so! So we need a heavily expressive languages. One where we can feel the power through our hands!

END

I hope you now have an absolute piece of SHIT of a language. THANKS!