16
ruhe
2y

Let's invent a new coding paradigm. Its goal is to make code as it naturally really should be: Ugly af

See the current list of rules in the description

Project Type
Project idea
Summary

Let&#039;s invent a new coding paradigm. Its goal is to make code as it naturally really should be: Ugly af<br /> <br /> See the current list of rules in the description

Description
Feel free to append this list of rules in the comments: - Every line shall have more than 300 chars - Every logical equation must be in CNF and use at least 5 different variables - A function is not really a function without two self-calls and 50 lines minimum length - Naming classes is good, naming them Class1, Class2, Class3, etc. is better - Objects must be called object1, object2, object3, etc. - On every two lines of code, there comes at least one out-commented line of code - Comments are forbidden unless they are used for out-commenting code - Files shall always be stored in the same hierarchy. There should be no extra folders - Indentation should be a random amount of whitespace in each line - To save space, each line should contain two commands, i.e.: i = 5 ; a++; print(a); a = i; - I'm out of ideas, your turn!
Current Team Size
1
URL
Comments
  • 2
    Is it okay if this triggers me? 😂 just a bit
  • 2
    @Clear0Ff that's perfectly fine, just the paradigm doing its job :)
  • 4
    - Design patterns are allowed and encouraged, but only if you reimplement their functionality with GOTO statements.
  • 0
    @AgeOfRanterance sounds great!
  • 8
    - unit testing is good practice. But tests for ClassX must be located in the same file as ClassX
    - passwords should be hardcoded to ensure passwords are hard
  • 3
    Let's infiltrate every big software company and make their code unmaintainable...evil af
  • 3
    - all classes must be instanced with an abstract factory
  • 2
    @Floydian no
  • 0
    @Floydian I'm sorry. If you really want to help out on such topics, why not join a NGO? Such help is always needed
  • 3
    - semicolons are not mandatory

    - spacesarerequiredjusttoseparateexpressionsandifferentinstructions

    - code blocks can either be enclosed in "begin...end", "{...}" or "if...fi"

    - variable names must be at least 10 chars long and must all start with the name of the project/object + "_var1", same goes for methods and functions

    - there's no include/import/using for libraries, they all have to be copies in the same file

    - spaces can also be used to separate parameters instead of commas

    - array will start from 1 and use () parenthesis

    - functions will use [] parenthesis for parameters of just nothing (like assembly)
  • 2
    @MrEvilCooki3 it's beautiful!

    But one change request: instead of mirroring all parenthesis, those should be used as follows:
    ( must be closed with >,
    [ is closed with },
    < with ), and finally
    { with ].
    This would even allow for a fourth type of parenthesis
  • 1
    For version control, only this is allowed: https://devrant.com/rants/1336740/...
  • 1
    Can we add this game or some version of it as a rule?

    https://devrant.com/rants/1598218/...
  • 1
    Is there any existing code following this out there? Would love to read it.
    Also how about a parser converting code to this
Add Comment